Great, they couldn’t monetize a fucking IDE. I will say without shame, I fucking hate Microsoft.
Sunsetting Atom
861–870 of 880 posts
Re: Sunsetting Atom
#862Ban me or whatever but Bill Gates is coming after your sperm, retards.
Re: Sunsetting Atom
#863Earlier quoted context omitted.
I was able to make VSCode look pretty great with a bit of work by following the ebook Make VSCode Awesome: https://makevscodeawesome.com/ great fonts, minimal visual clutter etc
Watching your "Hide all the crap" gif made me realize you could do this: > View: Toggle Activity Bar Visibility Much nicer, thank you!
I'm not the author of that webpage or e-book, but the e-book has a looooot of other good information like that.
Re: Sunsetting Atom
#864Earlier quoted context omitted.
> Sadly, Sublime is sort of dead. Sublime has ongoing development on https://www.sublimetext.com/dev and the last major release (4) was just about a year ago.
I was under the impression that the "forced" upgrade to Sublime 4 caught quite a few out, and may have been a nail in the coffin. I'm still rocking SLT 3, and it's my go-to for large file handling or just as a simple scratchpad, but development (of SLT) feels like it moves at a snails pace.
I can live with a 'LICENSE UPGRADE REQUIRED' text in the title bar.
Everything works just the same, and I don't get the purchase pop-ups.
Re: Sunsetting Atom
#865Just now I was checking the trending repos in github.com (JavaScript/Today)
and I got atom on no.5 and more than 50K stars
Re: Sunsetting Atom
#866Earlier quoted context omitted.
What an exceptionally unhelpful comment.
It was. I was in a particularly moody state and my filter was gone. It was meant in a way to be sympathetic to the challenges of that situation but is phrased badly. I'd delete it but I can't.
These things happen. Props for acknowledging.
Re: Sunsetting Atom
#867Projects rewritten from the ground up in $POPULAR_LANGUAGE are notorious for being more bug-free, faster, and more stable than mature, well tested and widely used software written in $OTHER_LANGUAGE (which also already has an entire community and ecosystem).
It's legacy the minute we don't feel like adding any more features to it.
I'm being snarky for the sake of clowning on corporations who do this.
I'm sure the choice of Rust was made on the shoulders of many existing issues in atom. However, it bothers me incredibly when a product advertises itself as being built with a specific language. If that's your main selling point (it's in the headline for zed.dev), maybe you're about to build something utterly irrelevant.
Re: Sunsetting Atom
#868Earlier quoted context omitted.
You're deploying via VS Code? If so, that's a weird pattern. I've been using VS Code for years to write JavaScript/TypeScript, Python, Go, Terraform, and CSS. My settings file is 60 lines, 42 of which are "for file extension X use autoformatter Y" configs. When I first switched to VS Code I was frustrated trying to make it conform to random expectations I had. Eventually I learned that it's easier to embrace VS Code'…
> You're deploying via VS Code? If so, that's a weird pattern. I don't think it's a weird pattern, maybe a slightly legacy one but not out of the ordinary. I've seen this pattern used at multiple places (not implement by me). It makes sense if you have special use-cases where you need to use physical hardware and/or a local stack is too heavy or complicated to run.
Sorry, “weird pattern” was a poor choice of words. I just meant that it’s an approach that isn’t common so it’s understandable that VS Code can’t handle it well.
VS Code is best when it’s just an IDE. I even have to drop into the terminal for some Git stuff
Re: Sunsetting Atom
#869Earlier quoted context omitted.
This is why I continued to use sublime text all the way up to capitulating to TypeScript. Code was slower because of all the intellisense. I've had Code freeze on me a few times. Something that I don't have happen in Sublime or Vim. If you have a lot of RAM and work on a current mainstream OS it may seem smooth, but it's still using 400mb of RAM. May as well use Eclipse or WebStorm FWIW. That said I'm using VSCode no…
> "but it's still using 400mb of RAM" Why does this matter? What is the point of saving RAM instead of using it?
Once you exceed it some of the content will go to swap, which is going to slow down the system (and wear an ssd faster). 400MB is not that much though, for me Code usually takes at least 1.5GB RAM.