Answer me this: are they or are they not consistently in support of Russia/China? Because I've seen it a lot from them (and blocked the instance soon after joining Lemmy when I noticed the pattern).
Is it just some big joke that went over my head?
Answer me this: are they or are they not consistently in support of Russia/China? Because I've seen it a lot from them (and blocked the instance soon after joining Lemmy when I noticed the pattern).
Is it just some big joke that went over my head?
I dunno, I ended up blocking the instance way before I knew about their reputation (like, when I first joined Lemmy) because all of the users their kept posting the most unhinged shit.
I have definitely seen blatant apologism for China/Russia from them.
FWIW, I'm much further left than your average Democrat (I consider myself a leftist/anarchist). I personally don't consider what I've seen from them to be very "left", just authoritarian.
It's a toss up, for me. Both managed to capture all discussion on major open source projects.
! is supported
Vim's command line, i.e, commands starting with :
. The vanishingly few it does support are, again, only the most basic, surface-level commands (and some commands aren't even related to their vim counterparts, like :cwindow
, which doesn't open the quick fix list since the extension doesn't support that feature).
Your experience is out of date.
The last commit to the supported features doc was 5 years ago, so no, it isn't. Seriously, you can't possibly look at that doc and tell me that encompasses even 20% of vim's features. Where's the quick fix list? The location list? The args list? The change list? The jump list? Buffers? Vim-style window management (including vim's tabs)? Tags? Autocommands (no, what it has does not count)? Ftplugins? ins-completion
? The undo tree? Where's :edit
, :find
, :read [!]
, and :write !
? :cdo
, :argdo
, :bufdo
, :windo
?
Compared to what vim can do, it is absolutely a joke.
I'm a senior software engineer with a pretty uncommon skill set. Recruiters are the primary way that companies hire in my industry outside of networking contacts and I get contacted frequently. The job before my current one was through a recruiter.
I very much dislike Microsoft and LinkedIn in general, but not using it all is a huge handicap that isn't worth taking on.
Nah, it's all hyped up bullshit that has to be babysat and manipulated to a degree that you may as well just write your damn code.
But beyond that, I'd argue that it's actually damaging for engineering organizations, because it means the org is incurring the maintenance cost of code not written by its engineers and that has no real thought put behind it. Maybe you can eventually coax it to produce code that's not completely broken shit, but it's code that your org doesn't actually "own" from a maintenance and knowledge-base perspective. The social aspect of code maintenance with this shit is always massively overlooked.
It's how recruiters find me, so unfortunately I can't. I almost never open it, though.
I use a different tool, visidata. It's especially nice when used as a psql
pager.
A text editor isn't the right tool for editing tabular data, imo.
As for KaTeX, what I would do is have a preview process running outside of vim that watches for changes in source files and re-renders. That's the Unix way of doing things.
There's many very basic features of vim that VsVim does not have (like... almost all command line commands), basic features which regular vim users use all the time.
You seem to think that people using vim emulation is the norm and using vim itself is the exception and unusual... Which is very much not the case. The opposite is true, with VsVim users being a minority. It's relatively novel among vscode users (most just use a mouse and maybe a small handful of built-in shortcuts), whereas vim itself is quite ubiquitous in the Unix world, with many Linux machines even providing it as the default editor. I know many vim and emacs users (including lots that I work with), and maybe 1 VsVim user (honestly not even sure if they do).
And I was expanding on my original comment, which was not replying to you, so there you have it.
It's speed, but it's also flow and a continuous stream of thought. If all your editing is being done with muscle memory and minimal thought, you can continue thinking about the problem at hand rather than interrupting your thoughts process to fumble through some context menu to make a change.
Sure, perhaps it's possible that I saw an unusually high amount of apologists, but I'm saying that it happened enough times and consistently enough that it prompted me to block them before I even knew anything about them, which I think at least says something. I won't claim to know what the majority opinion there is, but I don't think it's a stretch to say that it's an abnormal amount.