• 0 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle
  • And that has to be just about one of the pettiest to distinctions known to man.

    If it’s a petty distinction, why not acknowledge what I’m saying and move on? What is the point of this conversation for you?

    It’s still built to write code. Yes text is code, but vim is not a text editor in general,

    It’s built to edit text, not just code. Yes, text is code, but Vim is a text editor in general.

    The features are in the editor.

    Once you put them there, yeah.

    They are integrated with the editor.

    Once you put them there, yeah.

    Yes, it’s through plugins,

    .

    but they’re still part of the editor



  • Vim is designed to edit code

    To edit text files. It doesn’t matter if it’s code, configuration files, or plaintext. There are no interpreters, no compilers, no debuggers, nothing designed to support any particular framework or language or workflow. All of that is possible to add through the extensibility features.

    Vim is a highly configurable text editor built to make creating and changing any kind of text very efficient.

    Vim is an advanced text editor that seeks to provide the power of the de-facto Unix editor ‘Vi’, with a more complete feature set.

    Vim is a highly configurable text editor built to enable efficient text editing.

    https://vim.org/

    Vim is a text editor which includes almost all the commands from the Unix program “Vi” and a lot of new ones. It is very useful for editing programs and other plain text.

    https://vimhelp.org/intro.txt.html#intro.txt

    It has scripts for the sake of those scripts enabling integrated developer features.

    Those features aren’t enabled nor integrated. They’re added to Vim at its extensibility points. Baseline vim doesn’t have them.











  • Fluent polymorphism via duck typing. It’s useful when you’re treating objects as a collection of properties, and therefore it’s not their type that matters but which properties they have. Types can still be used to label common collections of properties but it’s less painful to talk about objects that are “like an X but with/without certain properties,” or where some properties themselves have a different shape, etc. This is applicable to web APIs, not just because of JSON, but because it allows to define both very rigid and very flexible schemas without much overhead or repetition. See the OpenAPI specification.




  • I don’t care what you prefer. But:

    Dark mode just doesn’t make sense for professionals.

    Come on.

    I use a dark, low contrast theme and work in a nearly unlit room with my monitors on nearly minimum brightness. It’s comfortable and totally efficient. I understand wanting to switch to bright mode and use higher contrast when reading unfamiliar material, but code is not that. It is highly structured, repetitive (syntactically) and organized. So you can usually have a clear idea of what you’re looking at without relying much on visual details.

    you risk blinding yourself with the sudden flash to light

    Only if your monitors are way, way too bright for your environment.