677
vscodium, vscode without spyware (github.com)
submitted 3 years ago by to c/technology@lemmy.ml
109 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 47 points 3 years ago (8 children)

Alternatively you can use and support a true community-driven editing environment dedicated to preserving your freedom, like vim/neovim or emacs.

  • permalink
  • fedilink
  • source
  • hideshow 16 child comments
    •
  • [–] 64 points 3 years ago (8 children)

    But that's something new to learn and configure. I just want to code why should I spend my time learning another text editor when vscodium is fine

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 13 child comments
    •
  • [–] 57 points 3 years ago (3 children)

    Careful. You're in a linux-heavy audience. They're the kinda people who would spend a few weeks setting up systems to use it for a few minutes.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 7 points 3 years ago*

    That's simply outrageous!!! As soon as I finish tinkering with my system, I'll prepare a proper reply...

    On a more serious note though. Don't overlook the role of procrastination in the endless tinkering many put on their boxes. I'm speaking from experience.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 5 points 3 years ago

    I'm a full-time Vim and Linux user when writing code. I agree with the statement that "simply switching" editors is very naive. I'm my personal opinion, you should decide on an editor that makes sense to you and learn to be very good at it. If VS Code is that answer, then great. Not everything points to Vim or Emacs.

  • permalink
  • fedilink
  • source
  • parent
  • [+] 5 points 3 years ago (3 children)
    [deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 1 point 3 years ago

    I'm still using sublime to this day. It keeps getting worse and falling behind VSCode with every new feature that never comes gets to it, but I have so many pet peeves with VSCode that everytime I try it I soon give up. I wish there were more options these days, but as the expected feature sets get more complex the number of options keep going down.

  • permalink
  • fedilink
  • source
  • parent
    • load more comments (3 replies)
  • [–] 19 points 3 years ago* (last edited 3 years ago) (11 children)

    I would love to use emacs, unfortunately coding in TypeScript is much more pleasant to me than coding in elisp or lua.

    Not to say Typescript is a good experience either, I always feel like fighting the language than actually coding. Just saying they are better than elisp or lua.

    Also I find vscode has better mouse interaction, but maybe emacs got better with time.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 11 child comments
    •
    load more comments (11 replies)
  • [–] 13 points 3 years ago (5 children)

    You can also use Debian 1.1 but the makes zero fun as well.

    Why make your own life hard for no reason. VIM is really really outdated when it comes to ease of use.

    There is not a single thing where vim is better in any way. The argument that it is faster is the biggest lie ever.

    Example: I write a few hundred lines of python code and execute it but sadly made formal mistakes. VIM does not help a bit. It might take hours of bugfixing with help of a command line.

    Python addon and some others would have instantly found those mistakes saving myself a lot of headache.

    That’s the same comparison as the senior developer and the normal dev. The dev might type twice as fast but making 5 times the mistakes he still needs a lot more time than the slow index finger typing senior.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 9 child comments
    •
  • [–] 8 points 3 years ago

    The argument that it is faster is the biggest lie ever

    Vscode is written in JavaScript and running in a web browser. Vim is written in C and runs at a console. Of course Vim is faster. Vscode is a hobbled cripple by comparison.

    The rest of your comment suggests you are ignorant of vim with plugins and command line tools. I've tried vscode and while it looks nice, I am far faster when developing with vim and a couple of open terminals.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 4 points 3 years ago

    IDEs like VSCose are only powerful because they integrate coding tools like LSPs and completion enginea. Those tools are also available on neo/vim or Emacs, so you can be as proficient as you were with VSCode. Hell, even GitHub's Copilot is available on vim!

    And frankly, having started coding on Atom before switching to neovim, I find a keyboard centric, mode-based coding much more efficient than a usual mouse-centric workflow.

    It really boils down to personal preference, but I'm eager to find some objective arguments proving that "vim is outdated when it comes to ease of use", because that's not what I experienced.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 3 points 3 years ago

    This is incorrect. Vim and neovim can reach the same level of functionality as VS Code through plugins and extensive configuration. An experienced vim user with plugins is as fast as an experienced VS Code user with plugins.

    Getting vim experience and customizing it has a much steeper initial investment. That’s where the disconnect is.

    There is an argument to be made that completely mouseless development is faster. This also requires a steep initial investment to pan out.

  • permalink
  • fedilink
  • source
  • parent
  • [+] 2 points 3 years ago* (1 child)
    [deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 6 points 3 years ago (1 child)

    What features are available in vim that aren't in vscode? Genuine question, trying to decide if I should make the switch

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 3 years ago

    This is probably going to sound a bit silly, but legitimately the fact that it's installed on most Linux systems by default (and if not full blown vim, then vi - or rather, vim-tiny often). VSCode has the Remote SSH extension, but the last time I checked it automatically installed the VSCode server (?) binary on the remote system. Often times I'm administrating systems that aren't mine, and do not want to leave random bits of VSCode onto it. Even if that weren't the case, its a lot easier for me to just open a file in vim since I'm already at a shell, rather than having to open VSCode, then wait for it to initialize (though it is quick!), activate Remote SSH and connect to the server which triggers the same initialization since it has to start the server-side component.

    Another probably silly sounding reason is that the keybinds are the same ones that you use in a lot of POSIX tools like man, less/more, Firefox even uses / to activate quick-find (while you're not in a text field of course) though admittedly I believe that is the only one, hell even bash itself if you use set -o vi (by default its in Emacs mode - this is actually a feature of the readline library that bash uses as far as I understand).

    Though admittedly, those mostly are Linux/Remote Administration reasons and doesn't apply to everyone - but those were some of my initial motivations.

  • permalink
  • fedilink
  • source
  • parent
    • load more comments (1 reply)
  • [–] 8 points 3 years ago (1 child)

    lapce is a vscode replacement that has all the sugar that people love and it's blazingly fast. It's still in alpha but I'm very hopeful for it's future.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 6 points 3 years ago (2 children)

    Am I going to be judged for admitting I use KDE Kate on here?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [+] 1 point 3 years ago (1 child)
    [deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 3 years ago

    That is incorrect. Both are pretty barebones from the start and have a big pool of extensions to get the functionality that you need. It might be more involved on the vim/nvim side, but that is more of an accessibility VS personalization thing.

    There are even sort of distributions for nvim that bring you all the common functionalities already configured.

  • permalink
  • fedilink
  • source
  • parent