Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Atom 1.20

blog.atom.io

Post reply on HN
Print view View original

21–30 of 69 posts

Re: Atom 1.20

#21

Post by _eht »

dmit wrote: post #20
_eht wrote: post #14

Earlier quoted context omitted.

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.

Do you think this thread is the best place for that input? Or that the input is valuable enough to post at any opportunity? For the record, I disagree with both of those statements.

Yes, I do think this is the best place for that input. People post things on HN, and there is a comment section where we talk about the thing. What else would be in a thread about a thing?

Noted.

Re: Atom 1.20

#22

Post by dmit »

methodin wrote: post #16
dmit wrote: post #12

Earlier 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.

Perhaps not but not all of us follow such things as closely as you might so the assumption that it's common knowledge is not necessarily accurate.

You're absolutely right that not everyone seeing this comment tree knows the details of Electron's memory usage. But I don't think that GGP's original comment was aimed to educate those people about the issue. To me it just sounded like a quip aimed at getting some cheap points from the choir.

Re: Atom 1.20

#23

Post by disease »

czechdeveloper wrote: post #13
_eht wrote: post #5

I 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.

I loved c# 10 years ago but have a few issues with it these days:

* functions not really being first-class citizens * great collection methods with LINQ, but why did they give them such weird names? (map = select, filter = where, reduce = aggregate?) * took them a while to come up with a great async model (async/await), so legacy c# asynchronous code can be hard to figure out at first

Just my opinion but it seems like more recent languages like Swift have done a better job implementing ideas from functional programming. It's still light years ahead of Java to me though.

Re: Atom 1.20

#24

Post by subie »

_eht wrote: post #5

I 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.

Tried VSCode. Thought Atom was still a cleaner experience.

Package system doesn't get much better than Atom. I think my code looks better on Atom (still not better than Sublime). I also ran into setup problems with VSCode git support on Linux.

Re: Atom 1.20

#25

Post by krainboltgreene »

_eht wrote: post #6
paule89 wrote: post #3

How 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.

If you have 32gb of RAM and you're getting type lag after 2 days, it's probably not a RAM issue, right?

Re: Atom 1.20

#26

Post by wjoe »

_eht wrote: post #6
paule89 wrote: post #3

How 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.

>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.

I dunno, I have the same Atom instance open on Linux for weeks with 20+ files open, I haven't experienced any noticeable lag. Maybe I'm just not as sensitive to the sort of lag you're experiencing.

Re: Atom 1.20

#27

Post by cyberferret »

_eht wrote: post #6
paule89 wrote: post #3

How 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.

> 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.

iMac with 32GB RAM here, and I routinely work with 10+ tabs open with files of 1000-2000 lines of code, and never really noticed and lag or crashing in Atom?

I leave Atom open and running 24/7 for days at a time. In fact, this morning was the first time I remember restarting Atom in over a fortnight because I installed 1.2.

Re: Atom 1.20

#29

Post by yjftsjthsd-h »

krainboltgreene wrote: post #25
_eht wrote: post #6

Earlier 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.

If you have 32gb of RAM and you're getting type lag after 2 days, it's probably not a RAM issue, right?

We'd need to know how much memory Atom itself is using after that time. Perhaps GP has found a memory leak, perhaps he's on an Atom processor; we don't know unless he tells us about resource use by Atom itself.

Re: Atom 1.20

#30

Post by SwellJoe »

_eht wrote: post #5

I 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.

I tried it, liked that it was faster than Atom at the time (though the gap has shrunk, as I understand it), but couldn't deal with it having an "only one open project" model. That was a deal-breaker for me. All of my stuff is broken out into many small projects, and I'm trying to go further in that direction rather than toward more monolithic codebases.

That one factor was a deal-breaker and I went back to Atom (though I still use vim just as often as Atom, since I don't have every project open in Atom at any given time, and sometimes I just need to edit one file really quick and check it in).

VSCode is very good. But, as long as it's got a one-project model, I can't do anything with it.

Post reply on HN