21 ms·

Sad to see this go. I was an early adopter of Atom, and I wrote two extensions for it, one of which while it was still in beta. The Atom developers made some t

by p-e-w 4y ago

Sad to see this go. I was an early adopter of Atom, and I wrote two extensions for it, one of which while it was still in beta. The Atom developers made some technology choices that in retrospect were ill-advised, CoffeeScript being the worst of them and splitting everything into dozens of packages a close second. They tried to backpedal on both of these later on, but by that time VSCode, with its far superior engineering built around TypeScript, was rapidly taking over. Of course, the GitHub acquisition was the last straw, but to be fair Atom was already pretty dead by then. While the Atom project ultimately failed, it did give us Electron and Tree-Sitter, two technologies that will certainly outlive it.

Gigachad 4y ago
I started a job in 2018 and someone commented “what are you still on Atom for? Everyone has moved to vs code”. So yeah it’s been kinda dead for a long time now.
- dylan604 4y ago
  whoa, a whole 4 years ago!! ;-) i want to make a "kids today" joke/comment, but it's more of just the pace of trends/fads not the people per se. you show up at a new job and the people make comments, of course you change. i've never used Atom, so maybe it was a better thing to change, but i've been introduced to some very ingrained workflows that just no longer made sense on so many levels. you can come in guns blazing and try to change everything now, or slowly acclimate to the workflow and then start suggesting changes/updates from inside. if you're hired as a 10x dev, then maybe guns blazing works, but if you're not, i'd suggest the latter.
  - satvikpendem 4y ago
    Somewhat unrelated, but why is it that when someone online writes an emoji with a nose, ie ;) vs ;-), I can immediately tell it's an older person? Was that something that was taught back in the day?
    - dylan604 4y ago
      It like when i receive a text when no punctuation, i can tell it is a younger person. anyone using emoticons vs emojis should be the indicator in and of itself regardless if there's a nose or not. how many times did you have to push that number to get to the symbol? "huh?" you ask. shows me your age too.
      - satvikpendem 4y ago
        Hah, bucking the trend there with your lack of capitalization.
        dylan604 4y ago
        that's too many pushes of the same button, so we all learned caps are a waste. also, e e cummings. ;) lol <eyeroll> or is it :eyeroll:
        TeMPOraL 4y ago
        > that's too many pushes of the same button, so we all learned caps are a waste No we didn't, because on a computer it doesn't require any meaningful extra effort (unless you're a lazy kid -> another age indicator), and pre-smartphones... texting actually used to cost money. You'd probably have a plan of some 1000 free text messages / month, or sth., which isn't that much if you're a teenager, given that a text messages was limited to ~140 characters (yes, that's where Twitter's limit came from - SMS compatibility). Caps, instead of being waste, let you skip whitespace. Instead of writing "caps are a waste", you'd write "CapsAreAWaste" (and then possibly shorten it to "CapsRAWaste"). We'd cut the message length by some 20-30% this way, which mattered for longer messages - it would turn a 4 SMS long message into a 3 SMS long one. We'd of course optimize harder when we were close to message length boundary. Being efficient with text messaging was a critical social life skill when I was young.
    - Karellen 4y ago
      Yes. (Damn, it's hard to find a "list of emoticons" (or even "usenet faq") from back in the day now. So much more recent stuff clogging the search results.) Anyway, this list of emoticons from '94 (according to the internet archive) is a pretty good representative of the sort of thing that people passed around then: https://ia802801.us.archive.org/view_archive.php?archive=/23/items/EMOTIC11_ZIP/EMOTIC11.ZIP&file=EMOTICON.TXT https://ia802801.us.archive.org/view_archive.php?archive=/23... As you can see, most have noses. Also, RFC-1855 (Netiquette Guidelines) from October '95 has one example of a smiley in §2.1.1: "Use smileys to indicate tone of voice, but use them sparingly. :-) is an example of a smiley (Look sideways)." I suspect that at least one of the bibliographical references provided would have contained a decent list of them at the time, but so many links are dead now. (And even if some of the ftp ones still exist, most browsers have dropped ftp support now, so most people are kinda SOL there anyway.) http://www.faqs.org/rfcs/rfc1855.html http://www.faqs.org/rfcs/rfc1855.html
  - nindalf 4y ago
    Oh you’ve been programming only for a few decades? I want to make a "kids today" joke/comment, but it's more of just the pace of trends/fads not the people per se. I’m actually a cosmic entity that views time as an artificial construct. When you’ve been around for centuries like I have, you’ll understand that trends/fads are mere points in the time space-continuum. Don’t get bent out of shape when you see one.
- herbst 4y ago
  I haven't worked for someone in years and that totally passed on me. I've tried code several times because of specific platforms it has plugins for but I never seen it as even comparable, at least not more than sublime. No idea what problems people had with Atom, but I really hope some fork let it live on.
  - cbkeller 4y ago
    There's https://github.com/atom-community/atom https://github.com/atom-community/atom, hoping that or similar will gain traction
umvi 4y ago
People hate on electron, but it's a pretty amazing piece of tech if you ask me. I can turn a browser game into a steam game with basically no effort which is nice because browsers change over time and electron helps you get a working offline snapshot of something you created.
- seba_dos1 4y ago
  > I can turn a browser game into a steam game with basically no effort There's actually quite a lot of effort required if you want Steam overlay to work and/or not crash with Electron, or to interact with Steamworks APIs.
  - deleted 4y ago
    [deleted]
- dijit 4y ago
  But what value is that, over the website?
  - drdeca 4y ago
    “ because browsers change over time and electron helps you get a working offline snapshot of something you created.” If the browsers change in a way that makes the website not work, the electron application will still work.
    - csande17 4y ago
      This makes sense from the perspective of the individual developer, but it's also a sad reflection of the sorry state of technology that the only way to be sure a website will work in 5 years is by shipping your own copy of the browser.
  - dmitryminkovsky 4y ago
    > which is nice because browsers change over time and electron helps you get a working offline snapshot of something you created.
esprehn 4y ago
Atom predated the LSP and leaned heavily into customizations with all the plugins running inside the UI thread (more like a traditional web page and 3p scripts). At the time they viewed the extreme customization support as a feature, and there was a thriving ecosystem of folks making plugins. That architecture has a major flaw though. A default install was fast, but a real configuration with all the plugins ended up quite slow. VSCode's architecture worked much better in real world configurations, and it turns out better performance wins in the editor space, even if it meant losing certain customizations (up to a limit). The architecture also allowed seamless remote editing, something Atom never could have done. The interesting thing has always been that both were built on Electron. Atom's developers had built all the tools and primitives needed, they just didn't have the understanding of the long term ecosystem effects of their design.
- brundolf 4y ago
  And VSCode is still pretty customizable/extensible- in most of the ways that people really cared about. It found a really solid balance
- deleted 4y ago
  [deleted]
- augusto-moura 4y ago
  LSP was a HUGE step forward, all editors benefit from it nowadays. Having multiple communities contributing back to the same language server makes maintaining those plugins a lot more comfortable.
  - naikrovek 4y ago
    I still fail to understand the importance of a language server. One could have created a library which conformed to some specification, written the library a single time, then compiled it for different platforms. Editors could then have loaded that shared library and used it just as they wrote in support for a language server. There's no need to get a network server involved. You still have the majority of development effort in the library, instead of individual text editors. You still have the joy of a nearly pure piece of code, without OS-specific paradigms like networking which impede progress. You still have a simple interface with the editor. I see exactly zero benefits of having a language server over a traditional shared library, except with a network server you make a trade off where you gain latency and other networking problems, and you gain absolutely nothing. I don't even know of any central language servers, which were one of the core benefits of the LSP design. "ooh we can all share a language server which is kept up to date independently of our editors! squeeee!" Where's that? Why is that a benefit at all? Presumably you'd still need to shut it down to update it, and someone has to manage it. The experience that people using editors got when aeditor developers started thinking about how to do something better is what the users love, not the LSP itself. LSP triggered this change in thinking, but anything could have, and I'm honestly surprised that nothing else did prior to LSP.
deleted 4y ago
[deleted]
sgtnoodle 4y ago
I tried Atom for a while in Windows, but a file watching bug made it quite inconvenient. Every time I edited and saved a file in another IDE (at the time, I was stuck using it to compile and debug an embedded system), that IDE would rename the original to a temporary file in a temporary directory before writing the new version. Atom would follow the rename rather than re-load the new file at the original path. It would make the open tab useless. I tried making an issue for it, but someone ranted on about moving files around on a Mac and then closed the issue. I tried trying to solve the bug myself, but I got about 4 layers deep into callbacks across at least three different repos, and gave up.
- prox 4y ago
  What editor did you go for after that? I still use Atom (I don’t need an IDE that much)
  - sgtnoodle 4y ago
    I've been using vscode lately. It mostly just works without getting in the way. Although if you work with python, one of the extensions seems prone to glitching out and spinning a CPU core. They're at least responsive to issue tickets. Sublime text seems to be a good paid option.
Existenceblinks 4y ago
Typescript makes VSCode very slow though. I remember the feeling when switched from Atom to VSCode it's wicked fast. And then Typescript happens, my macbook's fan keeps spinning from time to time.
- scambier 4y ago
  Typescript is compiled away. There are certainly issues with VSCode, but TS isn't one of them.
- catfishx 4y ago
  AFAIK Typescript has no runtime impact on performance, the transpiled JS should be equally fast as the handwritten code
  - AgentME 4y ago
    I think they mean the performance of VSCode editing a project with Typescript code in it. There's the runtime cost of VSCode checking the Typescript, providing intellisense, etc. (Not that I've ever had that runtime cost be noticeable to me. Maybe it's a real issue on certain codebases or workflows.)
kaichanvong 4y ago
we had the conversation at University back in 2002; it went, "Atom is a dumb name" (for a beta package for editing, building in). What is this, the year of Marvel Comics taking over the Galaxy or something?
herbst 4y ago
I really missed all of that. Atom is still the editor installed on all my systems. The one single thing I work with every day since many many years.
RektBoy 4y ago
VScode is also crap. It doesn't even support multi screen multi-window, heh no thank you. I can't comprehend, how anybody can use VScode for any real work.
- aembleton 4y ago
  What do you recommend over VSCode for real work?
daemond 4y ago
Yes, the star number of VSCode surpassed Atom in April 2018, 2 months before GitHub was acquired. https://ossinsight.io/analyze/atom/atom?vs=microsoft%2Fvscode#overview https://ossinsight.io/analyze/atom/atom?vs=microsoft%2Fvscod...
vertis 4y ago
I'm not sure it's fair to say it failed. Not everything is forever. It served very important purposes, helped push technology forward and paved the way for editors like VSCode. I'd call that success.
wink 4y ago
I also was an early tester (not adopter) of Atom and I kinda hated it right from the start, but it's been a while and I could never really put my finger on it. I think it always somehow felt sluggish (I'm talking trying out several builds over several months, not just a one-off). But I've also never warmed up to Sublime (which was fast but also felt off). Interestingly the moment I tried out VS Code (many years later) I instantly liked it and have been using it sporadically ever since, and as people always liken the two, I am confused to this day why one felt wrong and one felt right.
- _fat_santa 4y ago
  My journey went Sublime > Atom > VSCode. I started with Sublime in college and then went to Atom when it came out because it was "Free Sublime". Granted I liked it back then but I was still a college student (had I picked it up now I would have different opinions). Almost as quickly VSCode came out and was a "Better Atom" (I thought VSCode was based on Atom for the longest time). I wonder what will eventually replace VSCode. Lex Friedman said on his podcast that he sees VSCode as a modern Emacs which I think is a good way of thinking about VSCode.
martini333 4y ago
Don't be sad it's gone; be glad it happened.
kingboss 4y ago
Electron shouldn't exist. It's an insult to the engineering discipline. :barf:
nigamanth 4y ago
VSCode is owned by Microsoft, ever since Microsoft bought GitHub in 2018 it was bound to happen. The two text-editors had the same audience therefore Atom was bound to get shut.
scarface74 4y ago
> While the Atom project ultimately failed, it did give us Electron That’s not the positive thing that you think it is.
haolez 4y ago
Personally, I prefer CoffeeScript. The code gets more concise, it stimulates a coding style that's more objective and less "enterprisy" than TypeScript with all the excessive OO stuff. A simpler and more concise language attracts more contributors overtime. However, TypeScript has clearly won and static typing can help a lot with autocomplete stuff, so there is no point fighting back.
topherPedersen 4y ago
Are they killing off Atom because Microsoft bought GitHub and they already have VSCode?
codegeek 4y ago
I know people shit on VSCode but in my humble opinion, VSCode single handedly destroyed Atom. Far superior tool, 100% free and adoption growth was crazy.
danjoredd 4y ago
There is a solid alternative, though. Pulsar. Atom was kind of dead, but it still had a small, dedicated fanbase including myself. Hopefully Pulsar will be able to keep the project alive as long as us Atom fans use it
- denysvitali 4y ago
  Reference: https://github.com/pulsar-edit/pulsar https://github.com/pulsar-edit/pulsar
lopkeny12ko 4y ago
I guess I'm old school, but I'm genuinely surprised by how Microsoft drove such widespread adoption of Visual Studio which, as I remember, was an expensive, basically enterprise-only IDE for very Microsoft-specific proprietary technologies like C# and .NET.
- bananapub 4y ago
  eh? VS Code is unrelated to Visual Studio except by the name.

by p-e-w 4y ago

Gigachad 4y ago

I started a job in 2018 and someone commented “what are you still on Atom for? Everyone has moved to vs code”. So yeah it’s been kinda dead for a long time now.

dylan604 4y ago
whoa, a whole 4 years ago!! ;-) i want to make a "kids today" joke/comment, but it's more of just the pace of trends/fads not the people per se. you show up at a new job and the people make comments, of course you change. i've never used Atom, so maybe it was a better thing to change, but i've been introduced to some very ingrained workflows that just no longer made sense on so many levels. you can come in guns blazing and try to change everything now, or slowly acclimate to the workflow and then start suggesting changes/updates from inside. if you're hired as a 10x dev, then maybe guns blazing works, but if you're not, i'd suggest the latter.
- satvikpendem 4y ago
  Somewhat unrelated, but why is it that when someone online writes an emoji with a nose, ie ;) vs ;-), I can immediately tell it's an older person? Was that something that was taught back in the day?
  - dylan604 4y ago
    It like when i receive a text when no punctuation, i can tell it is a younger person. anyone using emoticons vs emojis should be the indicator in and of itself regardless if there's a nose or not. how many times did you have to push that number to get to the symbol? "huh?" you ask. shows me your age too.
    - satvikpendem 4y ago
      Hah, bucking the trend there with your lack of capitalization.
      - dylan604 4y ago
        that's too many pushes of the same button, so we all learned caps are a waste. also, e e cummings. ;) lol <eyeroll> or is it :eyeroll:
        TeMPOraL 4y ago
        > that's too many pushes of the same button, so we all learned caps are a waste No we didn't, because on a computer it doesn't require any meaningful extra effort (unless you're a lazy kid -> another age indicator), and pre-smartphones... texting actually used to cost money. You'd probably have a plan of some 1000 free text messages / month, or sth., which isn't that much if you're a teenager, given that a text messages was limited to ~140 characters (yes, that's where Twitter's limit came from - SMS compatibility). Caps, instead of being waste, let you skip whitespace. Instead of writing "caps are a waste", you'd write "CapsAreAWaste" (and then possibly shorten it to "CapsRAWaste"). We'd cut the message length by some 20-30% this way, which mattered for longer messages - it would turn a 4 SMS long message into a 3 SMS long one. We'd of course optimize harder when we were close to message length boundary. Being efficient with text messaging was a critical social life skill when I was young.
  - Karellen 4y ago
    Yes. (Damn, it's hard to find a "list of emoticons" (or even "usenet faq") from back in the day now. So much more recent stuff clogging the search results.) Anyway, this list of emoticons from '94 (according to the internet archive) is a pretty good representative of the sort of thing that people passed around then: https://ia802801.us.archive.org/view_archive.php?archive=/23/items/EMOTIC11_ZIP/EMOTIC11.ZIP&file=EMOTICON.TXT https://ia802801.us.archive.org/view_archive.php?archive=/23... As you can see, most have noses. Also, RFC-1855 (Netiquette Guidelines) from October '95 has one example of a smiley in §2.1.1: "Use smileys to indicate tone of voice, but use them sparingly. :-) is an example of a smiley (Look sideways)." I suspect that at least one of the bibliographical references provided would have contained a decent list of them at the time, but so many links are dead now. (And even if some of the ftp ones still exist, most browsers have dropped ftp support now, so most people are kinda SOL there anyway.) http://www.faqs.org/rfcs/rfc1855.html http://www.faqs.org/rfcs/rfc1855.html
- nindalf 4y ago
  Oh you’ve been programming only for a few decades? I want to make a "kids today" joke/comment, but it's more of just the pace of trends/fads not the people per se. I’m actually a cosmic entity that views time as an artificial construct. When you’ve been around for centuries like I have, you’ll understand that trends/fads are mere points in the time space-continuum. Don’t get bent out of shape when you see one.
herbst 4y ago
I haven't worked for someone in years and that totally passed on me. I've tried code several times because of specific platforms it has plugins for but I never seen it as even comparable, at least not more than sublime. No idea what problems people had with Atom, but I really hope some fork let it live on.
- cbkeller 4y ago
  There's https://github.com/atom-community/atom https://github.com/atom-community/atom, hoping that or similar will gain traction

umvi 4y ago

People hate on electron, but it's a pretty amazing piece of tech if you ask me. I can turn a browser game into a steam game with basically no effort which is nice because browsers change over time and electron helps you get a working offline snapshot of something you created.

seba_dos1 4y ago
> I can turn a browser game into a steam game with basically no effort There's actually quite a lot of effort required if you want Steam overlay to work and/or not crash with Electron, or to interact with Steamworks APIs.
- deleted 4y ago
  [deleted]
dijit 4y ago
But what value is that, over the website?
- drdeca 4y ago
  “ because browsers change over time and electron helps you get a working offline snapshot of something you created.” If the browsers change in a way that makes the website not work, the electron application will still work.
  - csande17 4y ago
    This makes sense from the perspective of the individual developer, but it's also a sad reflection of the sorry state of technology that the only way to be sure a website will work in 5 years is by shipping your own copy of the browser.
- dmitryminkovsky 4y ago
  > which is nice because browsers change over time and electron helps you get a working offline snapshot of something you created.

esprehn 4y ago

Atom predated the LSP and leaned heavily into customizations with all the plugins running inside the UI thread (more like a traditional web page and 3p scripts). At the time they viewed the extreme customization support as a feature, and there was a thriving ecosystem of folks making plugins. That architecture has a major flaw though. A default install was fast, but a real configuration with all the plugins ended up quite slow. VSCode's architecture worked much better in real world configurations, and it turns out better performance wins in the editor space, even if it meant losing certain customizations (up to a limit). The architecture also allowed seamless remote editing, something Atom never could have done. The interesting thing has always been that both were built on Electron. Atom's developers had built all the tools and primitives needed, they just didn't have the understanding of the long term ecosystem effects of their design.

brundolf 4y ago
And VSCode is still pretty customizable/extensible- in most of the ways that people really cared about. It found a really solid balance
deleted 4y ago
[deleted]
augusto-moura 4y ago
LSP was a HUGE step forward, all editors benefit from it nowadays. Having multiple communities contributing back to the same language server makes maintaining those plugins a lot more comfortable.
- naikrovek 4y ago
  I still fail to understand the importance of a language server. One could have created a library which conformed to some specification, written the library a single time, then compiled it for different platforms. Editors could then have loaded that shared library and used it just as they wrote in support for a language server. There's no need to get a network server involved. You still have the majority of development effort in the library, instead of individual text editors. You still have the joy of a nearly pure piece of code, without OS-specific paradigms like networking which impede progress. You still have a simple interface with the editor. I see exactly zero benefits of having a language server over a traditional shared library, except with a network server you make a trade off where you gain latency and other networking problems, and you gain absolutely nothing. I don't even know of any central language servers, which were one of the core benefits of the LSP design. "ooh we can all share a language server which is kept up to date independently of our editors! squeeee!" Where's that? Why is that a benefit at all? Presumably you'd still need to shut it down to update it, and someone has to manage it. The experience that people using editors got when aeditor developers started thinking about how to do something better is what the users love, not the LSP itself. LSP triggered this change in thinking, but anything could have, and I'm honestly surprised that nothing else did prior to LSP.

deleted 4y ago

[deleted]

sgtnoodle 4y ago

I tried Atom for a while in Windows, but a file watching bug made it quite inconvenient. Every time I edited and saved a file in another IDE (at the time, I was stuck using it to compile and debug an embedded system), that IDE would rename the original to a temporary file in a temporary directory before writing the new version. Atom would follow the rename rather than re-load the new file at the original path. It would make the open tab useless. I tried making an issue for it, but someone ranted on about moving files around on a Mac and then closed the issue. I tried trying to solve the bug myself, but I got about 4 layers deep into callbacks across at least three different repos, and gave up.

prox 4y ago
What editor did you go for after that? I still use Atom (I don’t need an IDE that much)
- sgtnoodle 4y ago
  I've been using vscode lately. It mostly just works without getting in the way. Although if you work with python, one of the extensions seems prone to glitching out and spinning a CPU core. They're at least responsive to issue tickets. Sublime text seems to be a good paid option.

Existenceblinks 4y ago

Typescript makes VSCode very slow though. I remember the feeling when switched from Atom to VSCode it's wicked fast. And then Typescript happens, my macbook's fan keeps spinning from time to time.

scambier 4y ago
Typescript is compiled away. There are certainly issues with VSCode, but TS isn't one of them.
catfishx 4y ago
AFAIK Typescript has no runtime impact on performance, the transpiled JS should be equally fast as the handwritten code
- AgentME 4y ago
  I think they mean the performance of VSCode editing a project with Typescript code in it. There's the runtime cost of VSCode checking the Typescript, providing intellisense, etc. (Not that I've ever had that runtime cost be noticeable to me. Maybe it's a real issue on certain codebases or workflows.)

kaichanvong 4y ago

we had the conversation at University back in 2002; it went, "Atom is a dumb name" (for a beta package for editing, building in). What is this, the year of Marvel Comics taking over the Galaxy or something?

herbst 4y ago

I really missed all of that. Atom is still the editor installed on all my systems. The one single thing I work with every day since many many years.

RektBoy 4y ago

VScode is also crap. It doesn't even support multi screen multi-window, heh no thank you. I can't comprehend, how anybody can use VScode for any real work.

aembleton 4y ago
What do you recommend over VSCode for real work?

daemond 4y ago

Yes, the star number of VSCode surpassed Atom in April 2018, 2 months before GitHub was acquired. https://ossinsight.io/analyze/atom/atom?vs=microsoft%2Fvscode#overview https://ossinsight.io/analyze/atom/atom?vs=microsoft%2Fvscod...

vertis 4y ago

I'm not sure it's fair to say it failed. Not everything is forever. It served very important purposes, helped push technology forward and paved the way for editors like VSCode. I'd call that success.

wink 4y ago

I also was an early tester (not adopter) of Atom and I kinda hated it right from the start, but it's been a while and I could never really put my finger on it. I think it always somehow felt sluggish (I'm talking trying out several builds over several months, not just a one-off). But I've also never warmed up to Sublime (which was fast but also felt off). Interestingly the moment I tried out VS Code (many years later) I instantly liked it and have been using it sporadically ever since, and as people always liken the two, I am confused to this day why one felt wrong and one felt right.

_fat_santa 4y ago
My journey went Sublime > Atom > VSCode. I started with Sublime in college and then went to Atom when it came out because it was "Free Sublime". Granted I liked it back then but I was still a college student (had I picked it up now I would have different opinions). Almost as quickly VSCode came out and was a "Better Atom" (I thought VSCode was based on Atom for the longest time). I wonder what will eventually replace VSCode. Lex Friedman said on his podcast that he sees VSCode as a modern Emacs which I think is a good way of thinking about VSCode.

martini333 4y ago

Don't be sad it's gone; be glad it happened.

kingboss 4y ago

Electron shouldn't exist. It's an insult to the engineering discipline. :barf:

nigamanth 4y ago

VSCode is owned by Microsoft, ever since Microsoft bought GitHub in 2018 it was bound to happen. The two text-editors had the same audience therefore Atom was bound to get shut.

scarface74 4y ago

> While the Atom project ultimately failed, it did give us Electron That’s not the positive thing that you think it is.

haolez 4y ago

Personally, I prefer CoffeeScript. The code gets more concise, it stimulates a coding style that's more objective and less "enterprisy" than TypeScript with all the excessive OO stuff. A simpler and more concise language attracts more contributors overtime. However, TypeScript has clearly won and static typing can help a lot with autocomplete stuff, so there is no point fighting back.

topherPedersen 4y ago

Are they killing off Atom because Microsoft bought GitHub and they already have VSCode?

codegeek 4y ago

I know people shit on VSCode but in my humble opinion, VSCode single handedly destroyed Atom. Far superior tool, 100% free and adoption growth was crazy.

danjoredd 4y ago

There is a solid alternative, though. Pulsar. Atom was kind of dead, but it still had a small, dedicated fanbase including myself. Hopefully Pulsar will be able to keep the project alive as long as us Atom fans use it

denysvitali 4y ago
Reference: https://github.com/pulsar-edit/pulsar https://github.com/pulsar-edit/pulsar

lopkeny12ko 4y ago

I guess I'm old school, but I'm genuinely surprised by how Microsoft drove such widespread adoption of Visual Studio which, as I remember, was an expensive, basically enterprise-only IDE for very Microsoft-specific proprietary technologies like C# and .NET.

bananapub 4y ago
eh? VS Code is unrelated to Visual Studio except by the name.