4 ms·
> But there's also a problem: I now have Thunderbird exactly how I wanted it, but it took a few hours to set it up and it required some technical knowledge: cal
by cxr 6y ago
> But there's also a problem: I now have Thunderbird exactly how I wanted it, but it took a few hours to set it up and it required some technical knowledge: calendar, tasks, Gmail like smart search, multi language corrections. For a normal user, that might be off-putting. However, I think Thunderbird is gaining momentum again
Thunderbird's problem is and always has been a lack of resources. Mozilla infamously bungled, underfunded, and then abandoned it (as a result of narrowing their focus from "the Internet" from their original charter and trying to redefine "Internet" to mean "the Web"). But even after the spin-off and independence, Thunderbird's lack of resources isn't helped by Thunderbird development being more difficult than it needs to be (read: seemingly unapproachable for many potential contributors).
"How to keep contributors when they are not even contributors yet" by Soledad Penades is incredibly relevant (moreso for its title than the actual specifics of the post content, but there are good lessons there, too):
https://soledadpenades.com/posts/2015/how-to-keep-contributors-when-they-are-not-even-contributors-yet/ https://soledadpenades.com/posts/2015/how-to-keep-contributo...
Ten years ago, you could get folks who were willing to get dirty with XPCOM/XBL/XUL because they already existed in the wider Mozilla community, and the biggest problem was Thunderbird's build process and compile times. Nowadays, you have the same barrier wrt annoying build processes, but the pool of knowledgeable people is smaller since the XUL add-ons ecosystem has been decimated. Ultimately, Thunderbird will need to address its legacy use of XUL, but they already know that and seem to be working on it.
More importantly, though, the problem Thunderbird needs work on is the same old problem from before: the headache of setting up a development environment that can actually perform a successful build, and how long it takes for that build to complete. The way that Zotero is built is currently pretty hacky, but nonetheless an example of how easy it should be to get a development environment set up. (In fact, it can and should be made easier than that, but just getting Thunderbird's build process to where Zotero is right now would be a huge boon to making Thunderbird something that potential contributors actually start considering as "approachable".)
https://github.com/zotero/zotero-standalone-build/blob/master/fetch_xulrunner.sh https://github.com/zotero/zotero-standalone-build/blob/maste...
- jcranmer 6y agoWhat hurts Thunderbird extremely hard is Mozilla's inability to keep any embedding story live for more than a year or so. Originally, Thunderbird and Firefox lived in the same CVS codebase, and the only difference to build Thunderbird was changing one line in your config file. When Mozilla moved to Mercurial, the Thunderbird code was left out of the repository on purpose, and so gained the annoying split-repository. Then Mozilla removed the ability to build the C++ code in anything other than a link-everything-into-libxul configuration. (Well, you could choose to have binary components live elsewhere, but the string APIs turn out to be completely different for pretty much no good reason--and mail code is obviously very string-heavy) There was a plan to build Thunderbird on top of a vanilla XULRunner. Then XULRunner was killed off. Webrunner was next (I think), and that was then killed off again. Now I believe there's yet another thing, but of course Firefox has also shut off access to binary (C/C++) extensions, so if Thunderbird wanted to use it, it would have to rewrite ~1M lines of code.
- cxr 6y ago> Then XULRunner was killed off [...] Webrunner [...] killed off Yeah, and just to point out: in a profoundly stupid move. I mean, it was stupid then, too, it's just that now we have the evidence for it. The constant refrain was that niche being a dead end. But the rise and proliferation of Electron (to the point that people bring it up to complain about it in places where it's not even on topic) and the success of Chromebooks (compared the failure of FirefoxOS for mobile; which itself was a leadership/execution error) both mean exactly one thing: those calling the shots on that decision and their supporters were flat out wrong. And so where is that crowd now? Mostly with their legacy and influence still being felt in every decision—and where those decisions contribute to Firefox being more marginal every passing year. Even if you forgive the original mistake, how is this not outright embarrassing for Mozilla Corp leadership?