1,228 karma · joined December 24, 2012
Also if you power on any old devices to look for the email, put them in airplane mode ASAP!
Originally Nylas Mail was OSS, but tied to the Nylas Cloud APIs (which did the actual mail processing.)
The cloud strategy was too expensive, and in version 2.0 the entire mail-sync system was moved into the client and open sourced. (https://github.com/nylas/nylas-mail/tree/master/packages/cli...). It's now much more like Thunderbird. There's a bit of cloud processing for snoozing / send later, etc., but it no longer syncs all your email through the cloud.
If you're a sysadmin and you test everything in an ancient version of Firefox that doesn't display SSL errors, you're not getting an accurate picture of what the product's users will see. The latest browsers might entirely block people from visiting your site, display a huge warning, etc. and you wouldn't know. Maybe being a sysadmin requires getting the fixes, refreshes, rebranding as they come down the pipe? I'm also not a fan of the recent changes, just take a more defeatist attitude I guess!
For most of the last three years I've worked on Nylas Mail (https://github.com/Nylas/Nylas-mail), and it hit 2.0 yesterday with Mac/Win/Linux support. It's entirely open source (GPL), written in JavaScript, syncs mail locally, etc. It essentially -is- what the author of the post is looking to build, except it doesn't look like Thunderbird. Nylas put at least $2M+ worth of engineering time into it, and I imagine ThunderbirdJS would take at least a similar commitment of time and effort. Heck, maybe they could just skin Nylas Mail and call it Thunderbird ;-)
This change evens the playing field for new users, allowing them to use the platform the same way og users like @alex and @ow do (having meaningful threads with 3+ people.)
If you have infinite time and need infinitely great performance, writing your own GUI framework on top of each platform's native libraries is probably the way to go. But a huge team of people already built and bulletproofed one called Chromium. It's icky in some ways and abstracted far from the native layer, and it'll probably eat an extra 50ms when someone clicks a button, but you can build and ship a cross-platform app in less than three years. The docs are written, the bugs are known ones, and it's easy to hire people who can help you. Just saying :-)
(full disclosure: I worked on an Electron-based mail client—definitely biased :-) )
Color scheme is very strange though. I live in SF, and I imagine if you surveyed folks on the street, everyone would tell you blue is a "safer" color than orange.
Maybe it could follow the Google Maps standard—green, yellow, red (traffic)? They may be depicting a different metric more important to cyclists (safety), but the problem-solving approach is the same: try to take green / yellow routes and avoid red ones.
(disclosure: I was the Nylas N1 team lead from 2014-Dec 2016.)
Curious if the author has made any optimizations around the observable queries to prevent small changes to the database from re-running everything? We had to do a bunch of optimizations so that changes would only cause queries to re-execute when absolutely necessary. Our case might be extreme though - the mail client has several GBs of mail data in SQLite and 50+ observable queries for different parts of the UI.
On iOS, the message has always been clear: "Use MVC, delegates & data sources, storyboards, etc. /We use them internally/ and you should too. Don't go re-invent UIViewController!"
1. Electron is not necessarily the best choice if all you want to do is "put your website in the Dock." In Electron, JavaScript on the page can do anything native code could do, like write to the filesystem unless you explicitly disable node integration. Just loading up your website inside an Electron window could be a disastrous security hole.
2. Electron apps run at least 50MB, and take at least 100MB of RAM. (Equivalent to one tab in Chromium)
3. JavaScript is single threaded. Node's event-driven / async design makes is a good fit for most things, but considers all work equal. You have to bend over backwards to do things that a nice threading abstraction would make easy (like Regexp find/replace in a huge directory tree. Atom actually spawns a separate process to do it so it doesn't consume the JavaScript process.)
Coming from native Mac OS X development, Electron is an breath of fresh air. There's an incredible amount of energy and momentum in the web development community these days, and things like Flexbox, ES2016, React, and ESLint make it possible to ship fast and iterate quickly. Who would have thought JavaScript would be achieving what Java/Swing set out to do in the 90's?
I've had a chance to work with the core team on a handful of bug fixes and new features, and they've been incredibly kind and welcoming. I think Electron will go far as an open source project, and I'm excited that GitHub is growing it beyond Atom.
If you're in the SF Bay Area and interested in learning more about Electron, there's a meet-up coming up later this month! http://www.meetup.com/Bay-Area-Electron-User-Group/
Really sad to see that Apple is using embedded web views without these sort of basic protections. I bet worse exploits than this are possible, given that they probably expose parts of the ObjectiveC layer through the JavaScriptCore bridge.
Of course, you could leave out the images, but you could also just keep using DOS if RAM is a concern :-)
It's beautiful, it speeds up my work day to day, and it's been worth every cent. Open source is great and I spend my days building an open-source mail client, but I have no problem paying for great tools.
This really highlights the need to create some sort of shared library from Electron's core, though. I've probably got a half dozen copies of Chromium bundled into various apps now!
For folks just learning about Electron / web-based desktop UI — we gave a talk about UI considerations at the Bay Area ElectronJS meetup last month: https://www.youtube.com/watch?v=JIRXVGVPzn8