News for hackers. Stuff that matters.
Re:Building Your First Atom Plugin by asd on Monday August 22, 2016 @10:04AM (#12336381)
I really want to love Atom, mainly due to the plethora of cool plugins being created lately. However, its inability to handle large files and the slow launch times are unfortunate.
Re:Building Your First Atom Plugin by cloverich on Monday August 22, 2016 @10:45AM (#12336654)
I know this gets viewed as overly negative, but to provide a bit more context: I still use my purchased Sublime text instance for: 1) Quickly opening single files, and 2) Opening large e.g. JSON files. I prefer everything else about Atom / VSCode, but in my experience they have not yet matched the performance of Sublime Text.
Re:Building Your First Atom Plugin by thom on Monday August 22, 2016 @10:43AM (#12336639)
It seems like some people have created VLF-like packages for Atom that employ similar workarounds to emacs for large files. This tickles me, but I assume long term this'll be solved more fundamentally.

I personally never cared much about emacs' similarly slow loading times, and don't see much of an issue with a modern editor taking time to start up. I'm happy just never quitting emacs on any of my machines, but it does mean you need something that interacts with sudo (i.e. tramp in emacs) to make quick edits to config files etc.

Re:Building Your First Atom Plugin by tombert on Monday August 22, 2016 @10:53AM (#12336712)
In Emacs' case, it bothered me until I discovered you can compile everything (including your `.emacs` file) and have it boot a lot faster.

AFAIK, there's no equivalent in Atom yet.

Re:Building Your First Atom Plugin by jnevelson on Monday August 22, 2016 @02:38PM (#12338389)
For me it's not so much the slow start-up time - that I can deal with since it happens so infrequently - it's the intermittent lag when typing or selecting text, and the high memory and CPU usage. A text editor should not be consuming 100% of a CPU core for almost any length of time and making my laptop sound like an aircraft carrier.

I love the concept of Atom (OSS text editor is awesome!), but it's bordering on unusable for me at the moment.

Re:Building Your First Atom Plugin by shriek on Monday August 22, 2016 @10:11AM (#12336429)
I haven't tried atom for a while now but it's startup time was also something that put me off from using it on a daily basis.
Re:Building Your First Atom Plugin by qudat on Monday August 22, 2016 @10:25AM (#12336522)
I guess I don't get the concern. Bootup happens once for me. I used to use vim but atom is much more Web friendly.
Re:Building Your First Atom Plugin by sotojuan on Monday August 22, 2016 @10:27AM (#12336537)
New software law: Every thread about Atom must contain a few people complaining about the start up time.

It's also fine for me, and I love plugins like the merge conflicts one[1].

[1] https://atom.io/packages/merge-conflicts

Re:Building Your First Atom Plugin by biocomputation on Monday August 22, 2016 @10:47AM (#12336671)
Atom is ~30 years newer than the original version of Windows Notepad, and Atom runs on hardware that is orders of magnitude faster than the 286 on which early versions of Windows ran.

Yet Atom is still slower and laggier than Notepad running on Windows in 1986.

How did GitHub manage to pull off that feat? Given the fact that faster programs were made 30 years ago on vastly inferior hardware, Atom's performance absolutely deserves to be criticized.

I can start Visual Studio right now and make a simple Windows desktop app in an hour with a text editor whose performance ( startup/ file load / editing ) will blow Atom away.

Re:Building Your First Atom Plugin by niftich on Monday August 22, 2016 @11:25AM (#12336966)
This point gets brought up a lot, and the criticism is fair, but only to a point. Atom's primary innovation is being built with HTML, JS, and CSS, and running on top of Electron that's running on top of Chromium. This design makes its internals approachable for a large audience. For lack of a better term, it's a first-party tech demo for Electron.

At this layer, you're pretty far from bare metal, and it's nice that it works as well as it does. In the future, I believe the need for so many layers will be lessened, when native script hosts and renderers can be leveraged, API calls shimmed between platforms, when packaging full Chromium is no longer necessary. Therefore I fully expect Atom to get better, both on the below-Electron side as native platforms evolve [1], and above, through optimizations.

For me, it's about expectation management. I expect Atom to be a proper text editor, but not necessarily a performant one yet, because I know how it's built.

[1] https://msdn.microsoft.com/en-us/windows/uwp/get-started/cre...

Re:Building Your First Atom Plugin by biocomputation on Monday August 22, 2016 @01:13PM (#12337799)
>> Atom's primary innovation

They couldn't make it fast on modern hardware?

It's a significant indictment of the technology, and of GitHub's engineering that a product like Atom is slow on th high-end Dell hardware that my employer buys for me.

Atom's problem, which includes the astoundingly enormous amount of CPU and memory that it guzzles, is that the people who built it demonstrably didn't care about performance, didn't know better, or both.

Atom is a textbook example of how not to write software. I guess it's not only 'hackable to the core', but 'inefficient to the core'.

It's just bad software.

Re:Building Your First Atom Plugin by niftich on Monday August 22, 2016 @01:24PM (#12337877)
> It's a significant indictment of the technology

Yes, it is; much more so an indictment of the stack than Atom itself.

> didn't care about performance

Perhaps; I can see why they would prioritize features over performance.

> Atom is just a textbook example of how not to write software.

I disagree. I very much feel that Atom is about demonstrating an archetypal 'desktop application', like a text editor, in Electron. And Electron is about coding in HTML/JS/CSS, albeit currently it's backed by a entire shrinkwrapped Chromium, which means you're essentially stuck inside a particular browser and inherit all of its performance characteristics.

It's the Electron stack that must prove that it's viable in the long-term, but it's possible that Atom will catch a lot of the flak instead.

Re:Building Your First Atom Plugin by lghh on Monday August 22, 2016 @10:58AM (#12336754)
> Yet Atom is still slower and laggier than Notepad running on Windows in 1986.

I would love to see something beyond just a void claim of this. Numbers, a video, literally anything. Even though Atom has a completely different use case than Notepad, one is for a quick edit of a file and one is for managing a project including file indexing, project search, and plugins, I still don't believe this is true. And I don't even like Atom!

Re:Building Your First Atom Plugin by SCdF on Monday August 22, 2016 @11:25AM (#12336956)
Not against notepad exactly, but there are good numbers comparing it to other text editors on the same computer.

https://pavelfatin.com/typing-with-pleasure/

You can download the software he wrote and try it for yourself, on your different text editors with plugins etc.

Re:Building Your First Atom Plugin by biocomputation on Monday August 22, 2016 @11:04AM (#12336804)
It would be great to post a video or some actual performance numbers, but I don't know where I'd get my hands on a 286 running the original version of Windows.
Re:Building Your First Atom Plugin by lghh on Monday August 22, 2016 @11:11AM (#12336856)
I'd wager, if you somehow could find it, your nostalgic view of the speed of a computer from the 80s would quickly diminish. Especially when you had to deal with more than one file with Notepad.
Re:Building Your First Atom Plugin by biocomputation on Monday August 22, 2016 @11:35AM (#12337045)
I was actually just a kid, so I don't really have nostalgic views of computer performance from the 1980s.

I do remember typing reports in Notepad. We had a PC because my parents couldn't afford a Mac.

Re:Building Your First Atom Plugin by krisdol on Monday August 22, 2016 @12:12PM (#12337309)
I guess that's part of the disconnect between happy users and folks who find it too slow. Atom is an effective IDE for me. I have smart auto-completion, version-control integration, task runners, linting, and, for many of the languages I work with, definition lookup, a debugger, a repl, and inline reporting of compilation errors. It makes for a great markdown writer as well. As a daily one-off text editor I can understand the complaints. But compared to a proper IDE, the startup time is pretty competitive.
Re:Building Your First Atom Plugin by striking on Monday August 22, 2016 @10:31AM (#12336563)
Eh, vim has that too: http://vimcasts.org/episodes/fugitive-vim-resolving-merge-co...

(edit: holy downvotes, Batman! I thought I'd provide a helpful point about vim, since not everyone knows it has plugin capability. My bad!)

Re:Building Your First Atom Plugin by fizzbatter on Monday August 22, 2016 @11:45AM (#12337137)
On the note of Vim, i wonder what could make Plugin development as active as Atom?

To me, that is a large part of what makes Atom attractive is the development community. I don't feel like Vim or Emacs has that, despite having so many plugins/etc. There just isn't as much Zeal for it.

I wonder if something about Vim could simplify this. Make it easier to support, develop, extend and use plugins?

Re:Building Your First Atom Plugin by sotojuan on Tuesday August 23, 2016 @08:23AM (#12343092)
Don't use Vimscript? You can't beat the react and ease of use of JavaScript. Also, a lot of people like their editors minimal. Vim users especially delegate a lot of work to Unix tools.
Re:Building Your First Atom Plugin by rgreasons on Monday August 22, 2016 @11:30AM (#12337002)
I love Atom as well and didn't understand why there were so many complaints about its performance, but once I ran into one of these issues myself I was unable to use it for the time being.

This specific issue opened on github[0] seemingly would affect a large number of atom's userbase - "Windows users with git repos" - and yet the best course of action is to modify atom from a community workaround. I love the editor and can't wait to go back to it, but I do really wish they would make a push to fix the smattering of performance issues and transition to v2.0. I think the editor is going to continue to have a bad PR problem as long as each discussion thread is half-full of potential users complaining about performance.

[0]: https://github.com/atom/atom/issues/9544