1,228 karma · joined December 24, 2012
I get the impression this is a very common sentiment in the engineering community, actually - I was raised this way. In my family, step one of "digesting" a feeling was always understanding why you felt it. Someone told me recently that "your feelings do not have to make sense to be valid and action-worthy", and I was stunned — all these years no-one had told me. It is immensely true.
If you insist on understanding your feelings before taking them into account, I think it's easy to fall into the trap of disregarding ones you think you shouldn't have, or choosing not to act because rational beings rise above their feelings. There are also some feelings you may never understand, and you could spend years sitting around trying to grok them.
It is perfectly valid (at least to me) to say "I made this decision because I felt this way at this time." No further explanation required.
To be honest, people using Electron are doing it because of huge business / process wins and worse performance is a generally acceptable downside. Performance is improving as Chromium improves, but it isn’t a huge focus in the Electron community.
I'd pay $69/year without even thinking about it, maybe they should jump on the subscription train!
(I know there’s a way to do autoupdate with Flatpak, but it is not tested and maintained as part of Flatpak itself, and when I looked it seemed to be a proof of concept with no production use!)
[Disclaimer: not a VIS guy]
- It's a fork of Nylas Mail with the entire mailsync codebase (~40k lines of JavaScript) replaced with a new C++ core based on Mailcore2. It uses roughly half the RAM and CPU of Nylas Mail and idles with almost zero "CPU Wakes" thanks to new C++11 features, which translates to great battery life. You might not even notice it's an Electron app.
- It still has the same great pro features, like snoozing and send later, but doesn't send your email credentials to Mailspring servers. All of these features have been re-implemented to run locally on your computer.
- The pro features still cost money ($8/mo). The goal is to use revenue from subscriptions to pay maintainers (myself, possibly other folks!) to maintain Mailspring indefinitely and/or put bounties on popular feature requests.
- The roadmap and website are still being assembled, but there's some really cool stuff in the works. Launching it and polishing the new C++ sync codebase is just step 1.
A lot of the features in the app, like read receipts and link tracking, are targeted at sales and business folks that send a lot of email and care about it being read. You can use the app without using them though! Unlike Nylas Mail, Mailspring implements all mail sync on your computer - your email credentials are not sent to the cloud and things like "unsnoozing" happen on your machine, not on a server. (Note that for many people, this is actually a /bad/ thing - if enough folks complain we might add the cloud sync stuff as an opt-in!)
That's actually mentioned a few sentences before the quote above in that GitHub issue ;-) The Mailspring ID stores metadata for things like read receipts and link tracking, but that's pretty much it!
Feel free to grab the version from the link above, just come back and switch to the auto-updating snap when it's ready!
1. Company invests heavily in engineering and builds a sync engine. Progress is visible on GitHub and rapid.
2. Company launches and repeatedly adjusts pricing and business models. Drives everybody crazy BUT:
3. Company finds it's value prop and customer base and the changes stop. Entire company shifts to building a sales team and keeping the wheels on the bus while they make their first customers happy.
4. Engineers switch from working on the core sync codebase to surrounding services, infrastructure, and scale.*
* Last week's developer dashboard announcement: https://www.nylas.com/blog/announcing-the-nylas-dashboard-2....
And somewhere along the road: Company realizes customers that are willing to go through the hassle of provisioning, deploying, and maintaining their own version of the open source sync engine are not the customers to focus on. ;-)
It's definitely sad to see this post, but Nylas has remained committed to open source and I think they've done this right. Relicensing everything under MIT ensures the product will have a bright future, even though Nylas has better opportunities it needs to pursue for it's employees and investors.
Would love for you to check out Mailspring (http://getmailspring.com) when it launches this month. We always struggled to implement performant, battery-friendly mail sync in JavaScript, and Mailspring essentially "rebases" the entire JavaScript UI on top of a new C++ sync engine built on mailcore2. You get the flexibility of JavaScript + plugins + themes with a much lighter profile.