That's basically how you could describe what happened. Those competent people are using Mozilla's infrastructure and trademarks, but otherwise running on donations.
calling it garbage seems kinda harsh, but I think they are moving more to using a javascript rendering method instead of xul. I remember reading about it a while back. I don't really like it either and one of the first updates from back then broke a lot of UI that had been working ok. I am not really sure what the problems are with working with xul though, but I think firefox moved off it a long time ago too. I feel like thunderbird's user base is more the type to want to use thunderbird because it runs like a local first desktop style app as an alternative to using a web interface to their email. At least that's what I like about it.
> they are moving more to using a javascript rendering method instead of xul
Yeah, that's what I said: garbage.
> I am not really sure what the problems are with working with xul though
I'm sure they'll yell "for teh securitah!" in a bunch of vague fearmongering, just like they did with firefox. But the #1 and #2 problems are that it's not shiny and new and the CADT brigade[1] only knows javascript.
> I think firefox moved off it a long time ago too
I wouldn't call it "a long time ago", but I guess that depends on your perspective.
And that's the moment when firefox became garbage - just another chrome-alike, except slower and more resource-hungry. It had been getting worse for a decade prior to that, but dropping xul and breaking a ton of my extensions and customisability was the (large) straw that broke the camel's back. Sound familiar yet?
> I feel like thunderbird's user base is more the type to want to use thunderbird because it runs like a local first desktop style app as an alternative to using a web interface to their email. At least that's what I like about it.
Exactly. Which is why moving their UI to a worse, javascript-powered, uncustomisable, web-alike trash UI is a bad thing. And a big part of why everything they've done in the last ~10 years has been garbage. And why I'll almost certainly be switching to something that isn't thunderbird next time I'm forced to upgrade it.
(forgive my tone, nothing against you, I just get emotional when morons take an excellent piece of software I've been using for decades and turn it into broken, unusable trash)
One thing that's important to note (which holds for the Mozilla Corporation too) is that the for-profit thing is a legal status, but the Foundation (an official non-profit) is the only shareholder, i.e. the only entity that "profit" can flow to. So you're not lining some billionaire's pockets.
(Though of course, employees of either entity can be paid whatever, which also holds for every other non-profit.)
Yeah it's all a bit complex (just like the US tax code, I suppose). MZLA (which makes Thunderbird) is a subsidiary of the Mozilla Foundation. The Mozilla Corporation (which makes Firefox) is also a subsidiary of the Mozilla Foundation. In practice, this means that the people running Firefox day-to-day aren't the people running Thunderbird day-to-day, although of course they do talk, and technology choices made in Firefox can and do effect Thunderbird, just like they effect e.g. Zen Browser or Tor Browser.
(Also, someone help a non-native speaker: I think the "effect"s above should be "affect", but for some reason that looked wrong here. Why is that?)
For their more common meanings, like in your paragraph, as a verb you want affect, and as a noun, effect. So, when in doubt, use that as a rule of thumb.
However, both have alternative meanings as the other part of speech.
Affect as a noun means emotion or disposition, and is mostly used in psychology. Your psychologist may say you have a depressed affect.
Effect as a verb means to bring about. You might say that a successful protest effected change in society.
As a verb, in addition to “have an impact on,” affect can also mean “to pretend to have,” like “she affected an air of mystery,” although this is less common.
"Effect" and "affect" are hilariously messed-up. They have subtly overlapping definitions sometimes but other times mean totally different things. They look almost the same in writing. They can sound almost the same. In spoken English, for some senses of each word we denote what we mean by changing the sound ("affect" may be pronounced almost like "effect", or, for one of its noun definitions and a related verb definition, very differently) or stress (for "effect", in some cases we hit the second syllable a little harder than other times).
The way you used "effect" here, its verb sense of "to bring about or cause" is the one that suggests itself, which isn't what you meant.
The simple way to keep the words' overlapping meanings straight, is that it's "effect" when it's a noun, "affect" when it's a verb. "Effect" can also be a verb, and "affect" can be a noun, but those definitions don't overlap.
Your post did indeed call for "affect", as you suspected.
Companies will often state a subsidiary is wholly owned by the ultimate parent regardless of which tier the subsidiary is at. The Thunderbird subsidiary could be under the Firefox subsidiary and the statement would still be true.
I agree that it should be "affect". Affect doesn't look wrong to me:
and technology choices made in Firefox can and do affect Thunderbird, just like they effect e.g. Zen Browser or Tor Browser.
I'm no expert on the rules of english, but I think maybe it would be slightly more gramatically correct to say that "choices made in Firefox can and do have an effect on Thunderbird". I would probably have phrased it like that. Maybe that's why it looks wrong to you?
English is a bit of a bastard language IIUC, and so we accept the way you've phrased it too, but in that case it should be "affect".
I hope this helps rather than making things more confusing! ;)
As a Dutch person, I experience exactly this dilemma: ringing the bell feels like telling people to get out of the way, when often there is plenty of space for me to pass through, but I know that there's a significant chance that they're going to veer into my way if they don't know I'm coming.
Of course, ringing my bell will often cause people to veer into the way, too. But then if you ring at a sufficient distance, you risk them not hearing it. Except there's no way to tell if they're not hearing it, or just consciously not veering into the way, and in the latter case, you don't want to ring again, because that will sound even more impatient.
Etiquette is hard.
(And yes, I want cars to have a bicycle bell too, so they can greet people without jump-scaring me.)
I used to slightly pull & quickly release a brake lever that made a less-annoying and less-loud "clack" noise when I wanted to be noticed but not to be annoying, generally when I knew I had no right of way but wanted to politely ask for a way around a group of people who hadn't noticed me yet.
Heh, you were walking right up to my viewpoint and then turned away. A parliamentary democracy with proportional representation has way more influence IMO, and you'll find another couple of relatively well-run countries that work like that.
Often it's very likely that previous ones won't need to change significantly, in which case disposing of having the full context while waiting for that review ends up slowing you down a lot. In those cases, often the main cause of extra busywork is Git administration, having to manually rebase sub-branches, and then losing in-progress reviews on those PRs as well.
Jujutsu is interesting in that it appeals both to Git enthusiasts, and people who strongly dislike Git's UX. It's great to see it spurring more innovation in the ecosystem around it.
Though if it can just make stacked PRs widespread, I'd already be very happy.
reply