all 8 comments

sorted by: hot top controversial new old
[–] 2 points 3 years ago

Come to neovim and spend countless hours tweaking your configs when you should be working 🙃

  • source
  • [–] 1 point 3 years ago (1 child)

    Is there even a difference, asside from the telemetry?

  • source
  • hideshow 2 child comments
  • [–] [S] 0 points 3 years ago (1 child)

    VSCodium has limited plugins, but most known ones were available.. Weird logo, some kind of a seaplant?? But I soon dig it..

    VSCode has all the plugins, but with Microsoft's Telemetry as expected.. Cool logo..

    Truth: I'm using VSCodium, the absence of Telemetry tends to improve it's overall performance.. I'm beginning to like the logo.. Plugins support has improved, all the plugins I used in VSCode, are now available.. All of it..

  • source
  • parent
  • hideshow 2 child comments
  • [–] 0 points 3 years ago* (last edited 3 years ago) (1 child)

    Vim, nano, micro, emacs... ffs. Your text editor should not be a shell, a file manager, a compiler, a build system or a dependency manager. Do one thing and do it well, a editor that tries to be everything ultimately becomes an inflexible mess. An integrated system often becomes an interdependent system, where you are stuck with a single build system, version control, compiler, or file manager. When these are separate tools, they are interchangeable, one person can use vim, the other nano, a third gedit. One project can use make, a second ninja or meson.

    If a project uses VScode, it basically forces everyone else to use it or forces you to maintain two separate build systems. Another option is to only use external tools, but then VScode just becomes an extremely bloated text editor. On my computer, both vim and emacs, start before I can lift my finger from the enter key. The same can't be said about VScode.

  • source
  • hideshow 2 child comments
  • [–] 0 points 3 years ago (1 child)