4 ms·
Between Sublime and VS Code I just don't see Atom's value proposition. I'd like to be proven wrong though.
by stuxnet79 8y ago
Between Sublime and VS Code I just don't see Atom's value proposition. I'd like to be proven wrong though.
- exelius 8y agoPretty sure Atom will just go away soon. VS Code is better at the same thing and now that they’re under the same roof it makes no sense to keep Atom around.
- jrs95 8y ago“Apache Atom”
- chiefalchemist 8y agoMaybe it makes sense for MS to use one to keep the other honest. Maybe the negative PR from shutting down Atom isn't worth it. Etc.
- BinaryIdiot 8y agoIt won't be going away. Microsoft and GitHub have both independently said they see a place for Atom and they're not getting rid of it. Let's also not forget that the deal isn't done yet. They still have 5-ish months to go before it's done. It'll probably still go through but until then they're separate companies (and even after then GitHub is becoming a subsidiary).
- wool_gather 8y agoPlus, it's open source, MIT licensed, so it would be difficult at best to make it just ¡poof! disappear.
- nijaru 8y agoI haven’t looked into it in about a month, but there are people on the atom team working on an experimental text editor engine written in rust rather than electron.
- ilikehurdles 8y agoIt has awesome packages and looks pretty good. I’m sure this comment is repeated in every post that has mentioned atom in the last year or two, so there may be some more in depth analysis if you do a search. VSCode and Atom have nearly the same value prop. Atom’s ecosystem works better for me for the languages I develop in.
- mephitix 8y agoI see IDE competition kinda like browser wars. I was just thinking the other day that VSCode was slower than it used to be. What if VSCode becomes slower? What if MS adds a bunch of bloat to it and it becomes like VS proper? Similar to when Chrome was the shiny new entrant, while FF was suffering with memory leak issues. Today, the roles are a bit reversed. If Atom can pull a Firefox I could see it taking market share away... anyway, competition is healthy, even if the value prop isn’t so clear right now.
- hungerstrike 8y agoVS proper isn’t that slow. It opens just as fast as Code does on my machine. I think you see performance penalties in VS when you add things like Resharper.
- jakear 8y agoI think editors tend to do best in the language they're made in, as thats the prime use case the developers have in mind. VS is great for C++ and C#..., but actually kinda terrible for JavaScript and TypeScript. On the other hand, VSCode is great at web, but debugging C++ in it is miserable. No support for STL containers, constant digging around in fields to get what should be at your fingertips from the start. As for performance, I took a clean install of VS Enterprise just last night, opened the VSCode source code in it, and files would take up to 10 seconds to just syntax highlight. Compare that to opening the VSCode source in VSCode, where everything is instant. And you say VS opens as fast as VSCode? I find that hard to believe. VS has an entire loading box it shows before it even renders the main window, because of how slow the startup is. Is this a cold open or maybe restoring from an in-memory instance?
- flukus 8y ago> VS has an entire loading box it shows before it even renders the main window, because of how slow the startup is And even when it's loaded it's not done. You can look forward to some more loading when you open a code file, when you try to open the main menu and a dozen other things. They went full eclipse.
- SquareWheel 8y agoCan VSCode edit itself yet? Atom was great for adjusting CSS of the editor on the fly.
- ehavener 8y agoyes you can theme it live, although changing syntax colors is only possible through a (limited) json flavor of textmate.
- jakear 8y agoYou can customize theme colors and syntax colors live, in the settings.json file. Syntax looks like: "workbench.colorCustomizations": { "[Monokai]": { "sideBar.background": "#347890" } } or "editor.tokenColorCustomizations": { "[Monokai]": { "comments": "#229977" } },