You never get too much latin in your product updates!!
I wrote for a general audience. Yes, it's a bit fluffy, but I had to try to explain certain things to people who don't know the first thing about computers (if you don't believe me, take a look at the eudora listmoms listserv). The responses I received were overwhelmingly "don't change a thing but the Unicode handling and the SSL!"
This crowd-funding itself was an exercise in poor risk management. I mean, you don't need a detailed feasibility study to tell you that starting from a couple ancient codebases based on (1) M$ MFC and (2) Apple Carbon, and ending up with a high-performing, multi-platform application that people would actually want to use today is going to be very hard and probably entirely unrealistic. A cursory look at the code should suffice.
The high mobile data cost was because said developer lives in the arse end of the middle of nowhere, and he refuses to use Mercurial properly (does a full hg clone instead of hg pull every time he contributes, drives me bonkers to be honest but the man writes good code!)
Said developer also admitted, publicly, to using an unlicenced copy of VS Enterprise after a disk crash. That was an indefensible state of affairs to me, and so the only thing I could do without wasting scads of time was to buy him a licence.
Please don't conflate HERMES Mail with Mail/X. They have similar user interfaces and are mail clients formerly written by different developers at the same company, but they are in different languages, different devs as stated before, and target different platforms.
I hope you're not saying that Eudora should be written using Electron...
If the primary threat to the project was "not finishing", then I'd absolutely use Electron. Development with web technologies is fast.
But if performance _is_ critical, and the biggest risk to the project is "lack of community interest", then I'd go with React Native†.
† I'm prepared for the possibility that some newer or more exciting technology exists by now.
> The only issue left is that of preventable costs arising from error, oversight, or incompetence
> [notably,] the indiscriminate destruction of data […] under the mistaken impression that it was otiose, by a programmer whose experience was insufficient for the task at hand.
> Although he might have been the 'cause of more harm than good' (in the opinion of another of our programmers), […] and while correction of the mistake took some time and effort, it did not result in schedule slippage.
His assertion that "the only phone suitable for the task (of talking to 3 people)" is a crowdfunded phone that doesn't exist yet, shows (at best) poor risk-management.
I don't understand how one developer could need $170/month of mobile data to fulfil their commitments to this project.
I don't understand why the Enterprise edition of Visual Studio would be necessary… nor why Visual Studio would be the right choice for macOS development.
I don't understand why he's being so open with such indefensible spending.
The project seems out-of-touch. One of his roles is to inspire collaboration, so he would have more luck using technologies that excite people today.
[0] https://www.kickstarter.com/projects/1313324524/hermes-eudor...