41–50 of 69 posts
Every update I hope there won't be lag, but sure enough there always is. Leave it open for a whole day and text input + browsing a project tree will freeze periodically. I'm on a maxed out Mac too...
As others above have said, me included, never experienced what you describe.
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.
1) Old Linux laptop with 4GB of RAM which I leave open for days on end without issues
2) Linux VM on virtualbox on my 8GB Ram desktop. I went for months leaving Atom open in the VM (saving it day to day) without issues
I'm not even using an up to date version of Atom? I know Atom is not great with very large files (it warns you before you open them) but for me this is only things like logs which I read from the command line with tail and grep. I have no need to open large files in my coding editor.
Earlier quoted context omitted.
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 lik…
SQL.
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.
I wonder why you get type lag, maybe you're working with really large files?
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?
The easy example being a datastructure growing over time and getting slower to manipulate and query. This is a problem where being cavalier with the amount of memory you allocate and use will hurt you, even if you've got lots of memory to spare.
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.
Thus you clearly have not learned F#, nor any other (superior) Standard ML descendant (e.g. OCaml or Rust).
(Why is F# inferior, you ask? CLR interoperation requires using types and datastructures defined in C# code, which overall mean that you will use an unidiomatic style. Hence, F# is basically "a usually-less-annoying C#", unlike other SML-likes. Except Scala, whose best description is "F# on the JVM".)
How about reducing the memory footprint?
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 like VSCode, but the Clojure integration in Atom is top notch. When that catches up I might take another look.
Another co-worker is the one who put together proto-repl for Atom so you'll see a lot of similar functionality in the two. I still use Atom and proto-repl just because I've been too lazy to get familiar with VSCode. But when James has demoed the debugger functionality in his VSCode plugin it looks great.