lemmeBe

joined 2 years ago
[–] [email protected] 2 points 57 minutes ago* (last edited 54 minutes ago)

Independently of the Mozilla team, yes.

However, my understanding is that, if Thunderbird were to become hugely profitable, the Mozilla Foundation would benefit financially, though indirectly.

The organizational structure:

  • Mozilla Foundation = parent organization
  • MZLA Technologies Corporation (which owns Thunderbird) is a wholly owned subsidiary of the Mozilla Foundation
  • Mozilla Corporation (which produces Firefox) is also a subsidiary of the Foundation

When Thunderbird moved to MZLA Technologies Corporation in January 2020, this was specifically done to allow Thunderbird to "collect revenue through partnerships and non-charitable donations".

As a wholly owned subsidiary, any profits generated by MZLA would ultimately flow back to its parent organization, the Mozilla Foundation.

In the end, that revenue would probably go to all the smart investments we've seen the Mozilla Foundation make over the previous years. πŸ™„

[–] [email protected] 0 points 14 hours ago

And none of these will stick it to you on multiple fronts if it ever comes down to it.

You want safety, diversify. You want convenience, go all in.

[–] [email protected] 1 points 1 day ago

Yeah, that scenario sounds awfully familiar to me as well. πŸ˜…

[–] [email protected] 3 points 1 day ago

Even with them, it's sometimes guesswork. Without them, it's just stabbing in the dark. πŸ˜„

[–] [email protected] 19 points 1 day ago (2 children)

Spike's a short period set aside to research a problem before committing to how long it'll take to solve it.

[–] [email protected] 36 points 1 day ago (8 children)

My mentor at my first job was a mid-level dev 10 years younger than me. He was an all-around great and knowledgeable guy. When he'd get asked for an estimate on something without proper details in the ticket, he'd reply that a spike was needed before any kind of estimate, and that's how it would usually proceed.

Sometimes, however, the PM would insist on an immediate estimate. My mentor would then, without hesitation, reply: "8 points" (a full sprint in our company).

"But why that long when you don't know the details?"

"Exactly. Give me a spike to find out, and then it could be less."

None of us other devs contradicted him, junior or senior, because we understood where he was coming from. Needless to say, I learned a lot from him including how not to kill myself so someone else could get a tap on the back.

[–] [email protected] 35 points 2 days ago* (last edited 2 days ago)

Exhaustive research was conducted on an impressive sample size of... one single device.

...and the provided details are astounding.

[–] [email protected] 2 points 2 days ago

πŸ₯ πŸ₯ 🎸🎸 🎬

[–] [email protected] 4 points 3 days ago

Enjoy, people! 😊

[–] [email protected] 3 points 4 days ago

I find that Television complements fd nicely.

[–] [email protected] 0 points 5 days ago

Thanks! I'll give it a spin. 🎠

[–] [email protected] 11 points 5 days ago (5 children)

!⬆️!< Same question? πŸ€”

 

First off, I've been loving vanilla-extract for the past 10 months. 😊

The only thing I really missed was the ability to sort CSS properties. Since there wasn't an ESLint plugin for that, I decided to create my own.

@antebudimir/eslint-plugin-vanilla-extract offers CSS property ordering (alphabetical, concentric, and custom), auto-fix capabilities, and supports multiple Vanilla Extract APIs.

If anyone wants to give it a shot, you can find more details in the readme. Looking forward to hearing your feedback.

 

First off, I've been loving vanilla-extract for the past 10 months. 😊

The only thing I really missed was the ability to sort CSS properties. Since there wasn't an ESLint plugin for that, I decided to create my own.

@antebudimir/eslint-plugin-vanilla-extract offers CSS property ordering (alphabetical, concentric, and custom), auto-fix capabilities, and supports multiple Vanilla Extract APIs.

If anyone wants to give it a shot, you can find more details in the readme. Looking forward to hearing your feedback.

 

First off, I've been loving vanilla-extract for the past 10 months. 😊

The only thing I really missed was the ability to sort CSS properties. Since there wasn't an ESLint plugin for that, I decided to create my own.

@antebudimir/eslint-plugin-vanilla-extract offers CSS property ordering (alphabetical, concentric, and custom), auto-fix capabilities, and supports multiple Vanilla Extract APIs.

If anyone wants to give it a shot, you can find more details in the readme. Looking forward to hearing your feedback.

 

First off, I've been loving vanilla-extract for the past 10 months. 😊

The only thing I really missed was the ability to sort CSS properties. Since there wasn't an ESLint plugin for that, I decided to create my own.

@antebudimir/eslint-plugin-vanilla-extract offers CSS property ordering (alphabetical, concentric, and custom), auto-fix capabilities, and supports multiple Vanilla Extract APIs.

If anyone wants to give it a shot, you can find more details in the readme. Looking forward to hearing your feedback.

 

First off, I've been loving vanilla-extract for the past 10 months. 😊

The only thing I really missed was the ability to sort CSS properties. Since there wasn't an ESLint plugin for that, I decided to create my own.

@antebudimir/eslint-plugin-vanilla-extract offers CSS property ordering (alphabetical, concentric, and custom), auto-fix capabilities, and supports multiple Vanilla Extract APIs.

If anyone wants to give it a shot, you can find more details in the readme. Looking forward to hearing your feedback.

view more: next β€Ί