Atom 1.21 features support for the language server protocol
Wow, that's a big one! I'm eager to try Atom out again after being burned by speed issues years ago.
Atom 1.20
11–20 of 69 posts
Re: Atom 1.20
#12How about reducing the memory footprint?
You were downvoted to oblivion, but honestly this is a huge issue that somehow feels like people are just OK with. Honestly, work with Atom open for a day or two on the same project, that's not uncommon right? Prepare yourself for some serious type lag. Full disclosure, I run a Linux desktop with 32GB of RAM. I'm not accustomed to type lag. Judging by your downvotes it's an acquired taste.
Yes, Electron apps consume a bunch of RAM. Yes, Rust needs you to deal with data lifetimes. Yes, Go still doesn't have generics. Yes, Haskell has a steep learning curve if you learned imperative languages first.
No, restating those facts on HN at every opportunity is not constructive.
Re: Atom 1.20
#13I was a fan of Atom until I tried VSCode. Call me a shill, if you will, but it is an all around better experience and I haven't looked back.
Re: Atom 1.20
#14Earlier quoted context omitted.
You were downvoted to oblivion, but honestly this is a huge issue that somehow feels like people are just OK with. Honestly, work with Atom open for a day or two on the same project, that's not uncommon right? Prepare yourself for some serious type lag. Full disclosure, I run a Linux desktop with 32GB of RAM. I'm not accustomed to type lag. Judging by your downvotes it's an acquired taste.
I downvoted paule89's comment because it felt like a cheap shot at an established product with well-known pros and cons. Yes, Electron apps consume a bunch of RAM. Yes, Rust needs you to deal with data lifetimes. Yes, Go still doesn't have generics. Yes, Haskell has a steep learning curve if you learned imperative languages first. No, restating those facts on HN at every opportunity is not constructive.
It's input directly from their user base about what they want in their work environment.
Re: Atom 1.20
#15I was a fan of Atom until I tried VSCode. Call me a shill, if you will, but it is an all around better experience and I haven't looked back.
Why shill. It's just great tool. I love lots of what MS does. I still consider C# best language I ever learned.
Re: Atom 1.20
#16Earlier quoted context omitted.
You were downvoted to oblivion, but honestly this is a huge issue that somehow feels like people are just OK with. Honestly, work with Atom open for a day or two on the same project, that's not uncommon right? Prepare yourself for some serious type lag. Full disclosure, I run a Linux desktop with 32GB of RAM. I'm not accustomed to type lag. Judging by your downvotes it's an acquired taste.
I downvoted paule89's comment because it felt like a cheap shot at an established product with well-known pros and cons. Yes, Electron apps consume a bunch of RAM. Yes, Rust needs you to deal with data lifetimes. Yes, Go still doesn't have generics. Yes, Haskell has a steep learning curve if you learned imperative languages first. No, restating those facts on HN at every opportunity is not constructive.
Re: Atom 1.20
#17I was a fan of Atom until I tried VSCode. Call me a shill, if you will, but it is an all around better experience and I haven't looked back.
Re: Atom 1.20
#18Re: Atom 1.20
#19I was a fan of Atom until I tried VSCode. Call me a shill, if you will, but it is an all around better experience and I haven't looked back.
+1, my coworkers always teased me for sticking with Atom and tried to get me to Sublime Text but VSCode was the first thing post-atom that stuck. Atom just could not handle big files well, and years of waiting sadly didn't yield big enough results.
Re: Atom 1.20
#20Earlier quoted context omitted.
I downvoted paule89's comment because it felt like a cheap shot at an established product with well-known pros and cons. Yes, Electron apps consume a bunch of RAM. Yes, Rust needs you to deal with data lifetimes. Yes, Go still doesn't have generics. Yes, Haskell has a steep learning curve if you learned imperative languages first. No, restating those facts on HN at every opportunity is not constructive.
It's a hugely beneficial visual when they are deciding what to prioritize on the roadmap going forward. It's input directly from their user base about what they want in their work environment.
For the record, I disagree with both of those statements.