

Even if you fine tune the setup, the auto-detect is great for getting you going.Į-mail clients really don't have much to add. You can't stop them I've tried.ģ) Seems really slow to sync hotmail and gmail.Ĥ) I found the PGP plugin harder to set up than Enigmail in TB.ĥ) The accounts setup does not have the cool auto-detect you get in TB. There are a few negatives with Claws Mail:ġ) No HTML support beyond a hokey plugin. There are some huge, commanding wins for Claws Mail over and above the RAM win clincher:ġ) Threaded view, easily/quickly toggled on/off.Ģ) View shows headers in line I happen to prefer that to a second scrolling pane.ģ) I found the accounts setup to be more rational and well organized than it is in TB. I have seen Claws Mail grow to around 0.4 GB no more - even if left open and exercised INDEFINITELY. For a while I thought I could run with no swap (I have 16 GB RAM), but behavior is even more pathological and irrecoverable when you run into the memory wall with no paging.
Mozilla thunderbird alternatives Pc#
Watch your PC get driven into thrashing the page file and I guarantee you will know what rage is. That is unacceptable, inexcusable, and an incompetent and moronic design. There does not appear to be any way to set an upper bound. If I leave my Thunderbird open and exercise it for several days it grows to 6 GB RAM use and beyond. Second the recommendation for Claws Mail. But I *really* don't think the solution is to allow *anyone* to make changes without *any* oversight. Maybe widening the pool of active participants and decentralizing power could be useful in many projects. And, from what I hear, there can be a lot of dysfunction in the open-source community at times. Maintainers with too much power can definitely be a problem. If people like what you're doing better, they'll go with you. Those people can be a problem, and they can hold things back.īut if that's so much of a problem as to significantly degrade the quality, then you shouldn't be the only one complaining - so team up and fork. I'll be the first one to admit that there are plenty of projects where I've heard of overbearing or wacko maintainers who have weird ideas about what the project should or shouldn't do. You got a problem with that? You don't think the direction of the project is going in the right way? That's fine - FORK. I, and most others, can't commit directly to the Thunderbird source repo That would drive Firefox's share of the market up, as existing users would not leave, and new users would use it to get access to the new changes that they want to use. Firefox should include lots of wanted changes, and few to no unwanted changes. That's what drives users away, sending Firefox's share of the market from the mid-30% range down to single-digits.

Firefox typically includes lots of unwanted changes, with very few wanted changes. They rarely make changes that the Firefox users actually want!įirefox's approach to change is upside down.


This is another area where Firefox devs fuck up. They want support for new features and functionality that they desire. Those are the kinds of changes that are unwanted, because they cause problems for users. Far too many of the changes to Firefox are dumb, dumb, dumb! We aren't talking about one or two bad ones now and then. The problem with Firefox is that the changes are fucking idiotic. The problem with Firefox isn't that there's change.
