News for hackers. Stuff that matters.
Re:Atom 1.10 and 1.11 beta by balanceiskey15 on Wednesday August 31, 2016 @11:53AM (#12399208)
Obligatory: Is it fast yet?

Apologies if this comes off as trolling. I really want it to be snappy so I can switch over.

Re:Atom 1.10 and 1.11 beta by Klathmon on Wednesday August 31, 2016 @12:01PM (#12399276)
Nothing "earthshattering" in either of these releases. But progress is definitely being made.

I have nothing to really back this up, but it looks like they are in the "death by 1000 cuts" mode of trying to speed things up. Little improvements here or there, little speedups across the board, refactoring bits of code to skip processes that aren't necessary when possible. Those kinds of things. If you are waiting for a big event like "hey we did X and now it's 5x faster across the board" i don't think you are going to see it any time soon (and if it does happen, you can be sure it'll be in the title!).

That being said, this release does bump the node version up, and the npm version. A lot of the startup slowness is from finding and loading node modules (at least from the bit of profiling I did months ago), and NPM3's flatter structure should allow maximum "reuse" of modules meaning less time reparsing identical modules.

I don't know if this will have any actual visible changes, but again, death by 1000 cuts.

Re:Atom 1.10 and 1.11 beta by swinglock on Wednesday August 31, 2016 @12:02PM (#12399286)
I don't think it is, this is the only thing I'm interested in hearing from Atom. Every time I've tried it has been unusable to me, I need it to be at least close to Sublime performance and resource usage to matter.
Re:Atom 1.10 and 1.11 beta by thatswrong0 on Wednesday August 31, 2016 @12:24PM (#12399456)
There are still little things that I notice are slow. For example, when I search for text within a file, I hit Cmd-f, then paste whatever I'm searching for.. And then my previous search finally loads and overwrites my actual search. In other words, I'm quicker at pasting than the editor is into the search window, so I have to deliberately slow down my paste.

I'm actually trying VisualStudio Code now, mostly because Atom handles indentation terribly. Trying to copy and paste and preserve indentation is a lost cause as of now.

Re:Atom 1.10 and 1.11 beta by acdanger on Wednesday August 31, 2016 @12:01PM (#12399279)
Yes and I would also add - is it stable yet ?

I had numerous instances where Atom would crash at inopportune times on my 2015 16GB MBP.

I Really hope these core issues have been fixed. Seems like a great editor and I’d love to be able to give it another shot.

Re:Atom 1.10 and 1.11 beta by virmundi on Wednesday August 31, 2016 @12:00PM (#12399267)
Similar real line: Does it still eat battery like a mid-westerner at a buffet?

I've thought about using underlying tech for a desktop app. I don't know how easy it will be to sell given that it would drain battery at probably 1.5 the rate of a normal Java or QT app.

Re:Atom 1.10 and 1.11 beta by cwyers on Wednesday August 31, 2016 @12:27PM (#12399488)
As a Midwesterner, I have to ask, what do you coastal folks do at your buffets?
Re:Atom 1.10 and 1.11 beta by twic on Wednesday August 31, 2016 @04:05PM (#12401090)
Well they don't eat batteries, it seems. I know, doesn't make a lot of sense to me either.
Re:Atom 1.10 and 1.11 beta by wyldfire on Wednesday August 31, 2016 @04:13PM (#12401138)
Maybe they meant the mid-west of some other continent?
Re:Atom 1.10 and 1.11 beta by doug1001 on Friday September 02, 2016 @02:37PM (#12415188)
not sure, but i think for buffet restaurants on the coast, "all you can eat" is at the customer's discretion; it's not a legal requirement like it is in the MidWest
Re:Atom 1.10 and 1.11 beta by msbarnett on Wednesday August 31, 2016 @02:18PM (#12400308)
I wouldn't really call buffets a coastal phenomenon.

I mean, there's the odd one here or there, but compared to the last time I was in Kansas, they might as well not exist.

Re:Atom 1.10 and 1.11 beta by bryanlarsen on Wednesday August 31, 2016 @02:34PM (#12400418)
I thought buffets were called smorgasbords in the midwest, or is that just Minnesota?
Re:Atom 1.10 and 1.11 beta by heydenberk on Wednesday August 31, 2016 @01:07PM (#12399809)
Trick question.
Re:Atom 1.10 and 1.11 beta by peterkelly on Wednesday August 31, 2016 @12:23PM (#12399450)
I think it's unlikely the performance issues are related to the underlying tech (that is, Electron), since it's basically a custom build of Chromium that omits the normal web browser controls. Performance-wise, if your app is suitable for running in a browser, it should be fine for bundling with Electron.
Re:Atom 1.10 and 1.11 beta by ralmeida on Wednesday August 31, 2016 @01:33PM (#12400024)
As noted in a sibling thread, other Electron apps such as Spotify and Slack do suffer from performance issues, and the general notion is that Electron apps are "slow by default" - that is, slow unless you take explicit effort to make them fast.
Re:Atom 1.10 and 1.11 beta by coldtea on Wednesday August 31, 2016 @05:26PM (#12401619)
Since when are programming editors handling large files and IDE-like features "suitable for running in a browser"?

I know there have been several (browser based programming editors) over the years, but all have been equally crappy and slow on medium to large files, and not that better at normal workflows either.

Re:Atom 1.10 and 1.11 beta by ralmeida on Wednesday August 31, 2016 @12:11PM (#12399352)
For what's worth (and to the best of my knowledge), Spotify's and Slack's desktop apps are based on Electron, the same "underlying tech" as Atom.
Re:Atom 1.10 and 1.11 beta by PeCaN on Wednesday August 31, 2016 @12:18PM (#12399414)
Yeah, and they're both pretty miserable. I'm thinking of unsubscribing to Spotify just because their desktop client is so bad.

Also, I'm not sure why Slack needs ~250MB of RAM. Seems a bit extreme for a chat app.

Re:Atom 1.10 and 1.11 beta by Klathmon on Wednesday August 31, 2016 @12:29PM (#12399508)
250mb of RAM for a chat app that can display 4k assets, renders every known written language under the sun side-by-side in multiple fonts, supports a stupid number of emoji, has an inline image viewer, realtime sockets kept open for notifications, includes syntax highlighting for a bunch of languages, a wysiwyg-ish editor for posts, one-on-one audio chat, and can work effortlessly with hundreds of people in a single channel (which is about as many as i've seen, but it could do more).

I think that's more than reasonable, and trying to get that number down to anything lower would be such a waste of resources for almost no payoff (what percentage of users do you think will have their lives measurably improved by having slack use 100MB less RAM?)

Oh, and mine is only using 100MB and has been running for a few days at least.

Re:Atom 1.10 and 1.11 beta by coldtea on Wednesday August 31, 2016 @05:31PM (#12401658)
>250mb of RAM for a chat app that can display 4k assets, renders every known written language under the sun side-by-side in multiple fonts, supports a stupid number of emoji, has an inline image viewer, realtime sockets kept open for notifications, includes syntax highlighting for a bunch of languages, a wysiwyg-ish editor for posts, one-on-one audio chat, and can work effortlessly with hundreds of people in a single channel

Not of what you wrote is even remotely difficult to be achieved, even in a 50MB-using native app.

In fact most of those things come for free with the OS and relevant native libs are already loaded into memory:

"renders every known written language under the sun side-by-side in multiple fonts", "supports a stupid number of emoji" (the OS font-renderer can give all that to all apps for nearly free)

"can display 4k assets", "has an inline image viewer" (I can do that in a trivial app that's 1MB or less).

"includes syntax highlighting for a bunch of languages" ...

Really, none of these features, and neither all of them combined, warrant 250mb of RAM.

Re:Atom 1.10 and 1.11 beta by Klathmon on Wednesday August 31, 2016 @06:28PM (#12401949)
But again, would it really make any significant difference in the vast majority of users?

If slack had taken the time to devote another team to developing another application (because they still need to support the web), possibly multiple applications for each platform, would they be where they are today?

Would that time and money pay off in any way? I really believe it wouldn't. To save a few hundred mb of RAM, you are looking at triple or quadruple your development and maintenance costs, not to mention making it that much more costly to add new features. That doesn't seem like a good payoff.

Obviously in places where it did make a difference (mobile platforms) they went completely native, and it shows in both the positive and the negative. Their mobile apps look and feel native, and work quite well, but they lag behind the "web based" clients in features. (most notably the new voice chat options are not in the mobile versions)

In a perfect world every application would be custom developed for each and every platform, and no expense would be paid to ensure that there are 0 wasted resources, but we are far from a perfect world.

Having a slack app that runs on any desktop platform, feels the same between all of them, and allows Slack as a company to exist is a win in my book, even if it uses a few hundred mb more than it should (which again, for me it only uses 100mb of ram, that's 1/320th of my total ram on this machine, and only like 40mb more than the tab that i'm writing this comment on is taking).

Re:Atom 1.10 and 1.11 beta by coldtea on Wednesday August 31, 2016 @06:59PM (#12402103)
>Would that time and money pay off in any way? I really believe it wouldn't. To save a few hundred mb of RAM, you are looking at triple or quadruple your development and maintenance costs, not to mention making it that much more costly to add new features. That doesn't seem like a good payoff.

I don't think writing native apps is so much more difficult that a web app like Slack. If anything, it's probably the opposite.

There are cross-platform (native) apps with custom UIs, like DAWs and NLEs that are an order of magnitude more complex in both their UI and their logic code, and yet are done with teams and by companies that have an order of magnitude less funding than a company like Slack.

Re:Atom 1.10 and 1.11 beta by Klathmon on Wednesday August 31, 2016 @08:25PM (#12402440)
It might not be more difficult, hell it is probably easier for each individual platform, but even if each one is 20% quicker than a web based one, all together you would end up spending 240% as much.

Plus then there is ongoing maintence costs, probably a ton more documentation costs (unless they all look and act the same), more coordination needed with new features to ensure parity, and more bugs and security issue surface area.

That's not a trade-off I'd want to make unless it was required for some other reasons.

Re:Atom 1.10 and 1.11 beta by ralmeida on Wednesday August 31, 2016 @11:33PM (#12402944)
I'm not particularly familiar with the relative costs of native vs Electron, but it should be noted that: a) many DAWs are single-platform; b) DAWs don't have backends, which is at least a significant portion (if not the majority) of what a service like Spotify or Slack spends development time on.
Re:Atom 1.10 and 1.11 beta by bnt on Wednesday August 31, 2016 @01:03PM (#12399779)
Slack is eating up 560MB on my machine. I actually do wonder why it needs this much.
Re:Atom 1.10 and 1.11 beta by ralmeida on Wednesday August 31, 2016 @01:30PM (#12400002)
There's no doubt both of them are not resource-effective at all, especially compared to other apps made in other tech stacks.

However, both are pretty successful services, and since the parent comment expressed concern if an Electron app "would sell", these are examples that such apps are comercially viable (even with all the problems they have).

At the very least, one can use them to go to market faster and/or validate an idea. I do hope that Electron (or other similar techs) apps reach a point where they are viable long-term in terms of performance and battery-efficiency. I also dislike slow, memory-hungry and battery-draining apps as much as pretty much anyone, but one should not dismiss Electron as useless.

Re:Atom 1.10 and 1.11 beta by ishansharma on Wednesday August 31, 2016 @12:24PM (#12399452)
250 MB for slack is good. I am in 4 teams and it is consistently taking 1 GB or more.

Something is wrong when a chat app takes more RAM than my Vagrant VM running an entire OS!

Re:Atom 1.10 and 1.11 beta by Touche on Wednesday August 31, 2016 @01:05PM (#12399797)
I'm not sure why people insist on using the Slack app rather than use it in a browser tab. It's literally the exact same thing.
Re:Atom 1.10 and 1.11 beta by merqumab on Wednesday August 31, 2016 @01:24PM (#12399947)
If you have multiple Slacks, it's not. You can cycle through all your connected Slacks with the app.
Re:Atom 1.10 and 1.11 beta by PeCaN on Wednesday August 31, 2016 @01:52PM (#12400144)
My browser gets messy and I tend to lose the Slack tab. I could just pin it I suppose.
Re:Atom 1.10 and 1.11 beta by asdf1234 on Wednesday August 31, 2016 @12:49PM (#12399670)
I dropped Spotify completely because of the ridiculous energy use.
Re:Atom 1.10 and 1.11 beta by HalfwayToDice on Wednesday August 31, 2016 @12:21PM (#12399434)
Ugh that's maybe why Slack is one of the slowest apps I've encountered on my Mac. Asides from Atom.
Re:Atom 1.10 and 1.11 beta by embwbam on Wednesday August 31, 2016 @12:12PM (#12399361)
They fixed the input lag a few releases ago. I switched from neovim two months ago and it can keep up with my mad keystrokes now.

It still takes a while to launch, but that isn't as important to me as performance once it is running.

Re:Atom 1.10 and 1.11 beta by Dowwie on Wednesday August 31, 2016 @11:59AM (#12399259)
What were you doing with it that gave you performance problems? Basic navigation has millisecond response time. Auto-complete / live syntax checking for Python is instantaneous.

My peeve is with font rendering. The same fonts look better in pycharm. I hope they improve this.

Re:Atom 1.10 and 1.11 beta by jve on Wednesday August 31, 2016 @12:46PM (#12399651)
My use case: Open some html file with thousands of lines. Was unusuable. But that was long ago.
Re:Atom 1.10 and 1.11 beta by madspindel on Wednesday August 31, 2016 @12:00PM (#12399272)
At least moving around tabs is fast now. Other than that I feel Atom is pretty fast on my computer. Still some problems with large files compared to VSCode but I still like Atom more.
Re:Atom 1.10 and 1.11 beta by mrspeaker on Wednesday August 31, 2016 @12:46PM (#12399653)
One thing I just tried: opening a bundle.js file. I accidentally do this at least once a day and it crashed Atom every time. The 1.11 beta handles it fine now. Good job Atom people!
Re:Atom 1.10 and 1.11 beta by haylem on Wednesday August 31, 2016 @01:03PM (#12399780)
Well, that's quite an underwhelming comment...

Yay, we can open a file!

Re:Atom 1.10 and 1.11 beta by jszymborski on Wednesday August 31, 2016 @12:26PM (#12399482)
I use it daily for PHP development, and I don't ever notice performance slow-downs unless I accidently click on a >1mb image and it tries to write the binary to display.
Re:Atom 1.10 and 1.11 beta by ChrisClark on Wednesday August 31, 2016 @12:29PM (#12399499)
Yup, it's perfectly fast. I never notice any slowdown and code on it all day.