Anarchism is not chaos, which is what it seems like you think it means. Anarchism is the opposition to hierarchy and is thus directly opposed to fascism and therefore Trump. No anarchist wants to see Trump win because it means fascism has won.
It’s not necessary. Unlike on Windows, Linux users rarely download random packages off the internet. We just use package managers.
The software itself may or may not be more secure, but acquiring software is absolutely more secure. There’s so much Windows malware people unwittingly download from the internet. Downloading from a distro’s software repository simply doesn’t have that problem.
! 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 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.
Yeah it sounds like you’re trying to mock me but it mostly just comes across as confusing. Maybe it’s just sarcasm? Hard to tell.
Anyway, it’s pretty well-known in the vim community that VSVim is pretty lackluster vim emulation. There are much better examples of vim emulation out there, such as evil for emacs.
It honestly has nothing to do with being a “power user”. It’s simply false to claim that vscode has more features than vim (which is what the parent comment was claiming), and this should be evident to anyone with more than the most basic, surface-level understanding of vim (more than vimtutor, basically). Vim is a lot more than HJKL and ciw.
I’m not annoyed with VsVim really since I honestly don’t really think about it as it’s not all that relevant. I do find it a bit irksome when people make false or misleading claims about vim from a place of ignorance about what it actually is.
It’s a strange phenomenon with vim in particular, where many people are exposed to it at their periphery, read some reductive claim about it online, and parrot said claim all over the place as though it were fact. Perhaps the nature of being a tool that most are exposed to but few actually learn.
Vim is extremely feature-rich, and people that think otherwise don’t really know how to use vim. Saying vim doesn’t have a lot of features is just a meme that isn’t true.
Also, the vim plugin for vscode is kind of a joke compared to what vim can do. It’s very “surface-level” with minor emulation of some of the common keybinds.
A language is not functional just because it supports higher order functions. Technically C even supports them (even though the ergonomics and safety of them are terrible). Would you call C a functional programming language? Obviously not. Rust is also not a functional language, even though it comes closer than most OO/imperative languages.
Kotlin and plenty of other OO languages have borrowed some ideas from functional languages in recent years because those ideas are useful. That doesn’t make them functional languages. If Kotlin were a functional language, then it wouldn’t need libraries like arrow to try to make doing FP in Kotlin even (kind of) possible.
Hallmarks of FP (beyond higher-order functions), in no particular order:
There are some minor exceptions, such as Clojure lacking pattern matching, but on the whole functional languages generally fit these descriptions.
That list also counts Java and C# as “functional languages”. I wouldn’t take it too seriously. Ocaml, Scala, F#, etc. are impure functional languages. Kotlin absolutely is not. Having a couple of features you might find in functional languages does not make a language functional. Kotlin is still very much an OOP-based language. It’s basically a somewhat nicer Java.
Minor nit: Kotlin is decidedly not a functional language.
Design patterns in OOP exist purely to solve the problems created by OOP itself. If you have a language with proper ADTs and higher order functions, the need for traditional design patterns disappear since the problems they solve are first-class features baked into the language.
The first-class replacement for the Strategy pattern (and many other patterns such as the Visitor pattern) is sum types (called enums in Rust).
It’s definitely not great here at all, though I’d say it’s a bit different for professional software developers (who probably make up the bulk of contributors), since that kind of job tends to give you better benefits. In my experience, it’s typical to either have unlimited PTO (that you may or may not be able to take, admittedly, though I’ve never had an issue with that), or at least a couple weeks of vacation a year. I’ve never worked anywhere as a software engineer where I had to really even account for sick time at all. I just tell my team I’m sick and that’s about it.
It sounds funny but it’s not an uncommon phrase.
Briefly glancing through your code there’s a typo on line 37:
outlives_parsed = parse_trail_outlives(bouds.fetch('outlives', nil))
Of course this wouldn’t be an issue had you actually implemented it in Rust since such a thing wouldn’t compile. Not really a good reason to be using ruby for this.
Could you not have a hashmap keyed on matches pointing to vectors of strings for the players in each match? Basically modeling the data how you want rather than relying on indexing.
The similarities are superficial at best. The only thing similar is that it uses braces for attribute sets (objects) and square brackets for lists. And I guess quotes for strings.
But otherwise it’s a full (functional) programming language, with functions, variable bindings, etc.
Flakes aren’t perfect, but they are really good for ensuring that you have completely reproducible builds since the version used for every dependency is pinned.
You only need 1 tab to OOM if that tab is Jira. I’ve literally had tabs take up more than 10GB.