It is not a fork of VS Code and it is a truly open source project. If you want an editor that looks like VS Code and is compatible with with it's extensions then use Theia. Check their github repo, they still have open issues related to telemetry. VS Codium is playing catch up with Microsoft to disable telemetry on every new version. The worst part of VS Code is that it is infested with telemetry. 4 years from now they might decide to sunset VS Code in favor of a new proprietary editor or a cloud editor and you will have to switch editors again. New github CEO said, 4 years ago, that he understands that the code editor is a personal choice, difficult to switch, etc and that they will keep developing atom. It is better to move to Neovim, Vim, Emacs or any other open source editor developed by a community and not a corporation that might decide to sunset their editor at any time. VS Code is not as hackable as Atom and that is their biggest difference. automatically attaching the project folder conda env R based on the file in focus in the editor, but can't see to figure that out how right now, though at least the framework is there because on the python side it just works.Īnd because of this in Linux I just launch VSCodium from the GNOME desktop, not like I had to do with Atom where I opened a terminal, activated a conda env, launched Atom and then was stuck with that conda env and not automatic env switching based on the file in People that like Atom more than VS Code don't care if VS Code is better or faster. I'm still trying to figure out how to do the the analogous with R in VSCode, i.e. It automatically switches depending on the file in focus in the editor. Honestly it's just a tool for me to get my job done effectively (scientific software dev and comp analysis in python and R) and I don't care that much am not a cultist, and guess what it actually works well and has features I've always wanted that Atom never had.Ī feature VSCode has that Atom didn't and it's a huge plus for me is that each your project folders can be associated with their respective mamba/conda environments - so each with their own python and libraries specific to that project. VSCode has a ton of settings and takes some time to get adjusted to, but in only a few days I feel pretty comfortable. I just moved to VSCodium because I need to get my job done TODAY, can't wait for pre-alpha or beta madness right now. But have to get my job done and not waiting until last minute until more Atom breaks. Loved every minute of it, best IDE I've ever used. I have been very pro Atom since I started using it in 2017 until last week. (Just about no chance Atom packages would be compatible.) It will be a bit different from Atom, to be sure.) But (other than tree-sitter) it is a total re-write from scratch in a different programming language. Otherwise, the only thing shared is people (some really significant core contributors from Atom), and some shared design philosophy. Shared code with Atom is basically tree-sitter for code syntax highlighting. The package ecosystem would not be compatible. (I will say this: I can see that it will not be a 1-to-1 replacement for Atom, especially if Atom package ecosystem is the thing that matters most to you. If you want an update on Zed, this talk is pretty much the only major update recently: Best not to speculate, or assert things that aren't set in stone yet. Even if it is a very important reason to the creators motivating them to build this app.) Nathan Sobo said in a talk that in the long-term they want the core editor to be " free and probably open-source." (Sounds like/I guess implies the collaboration feature would be monetized and potentially closed-source, while clarifying that the collaboration feature would probably be an optional part of using the editor. It is still pre-alpha (or private alpha some time this month). The code for Zed has not been shared, yet.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |