I'm glad to see Electron / Atom-Shell moving forwards, but I wish they'd publish a roadmap. There are things (like copy/paste) that are lacking and I'd like to know what the plans are. As it stands it's mostly a wait-and-see kind of deal, which is a bit disconcerting on big projects.
What does Electron do differently from NW? I get that one is Chromium and the other is just webkit, but what concrete, practical differences are there?
This would interest me more if there was a good automatic build process for it (in the style of node-grunt-webkit-builder).<p>As it is you still have to do a bunch of the packaging manually (or design your own shell script for it), and for whatever inane reason, `npm install electron-prebuilt` only downloads the binary for your current platform, so you can't even make a replicable build process by using it as a base and using scripts that copy the different binaries.
Is it suitable for WYSIWYG or a plain text & source code editor? Does it originate initially from Mozilla's Ace text editor? <a href="https://github.com/ajaxorg/ace" rel="nofollow">https://github.com/ajaxorg/ace</a> The name changes are a bit confusing (Mozilla Bespin -> Skywriter -> Ace ->(?) Atom -> Electron).
Electron's / Atom Shell's homepage isn't doing a good job of explaining what it is (as someone who's unfamiliar with it). Is it a site-specific-browser implementation? It's certainly not a "shell" in the normal sense of the term.
Is it me, or does it sound a bit bloated:<p>> It now includes automatic app updates, Windows installers, crash reporting, notifications, and other useful native app features<p>* automatic app updates : We have distribution repositories for this.
* windows installers: Doesn't window have it's own like app store now (market something?)
* notifications: which we already had on all major OSs for years.
The thing that turned me away from Atom and its' development is CoffeeScript. As someone who loves idiomatic JS, I still can't get why you'd pick a language that makes tooling and debugging a nightmare. It's also a kick in the gut to efforts to fix the shortcomings of ECMAScript like ES6 [1].<p>[1] <a href="https://github.com/lukehoban/es6features" rel="nofollow">https://github.com/lukehoban/es6features</a>
That's a seriously confusing name. I thought this was a physics story of some kind.<p>Additionally it's also a bad name because it's impossible to google.