As a kid, my dad (a mechanical engineer) explained this to me in a really memorable way. He was planning a model bridge building contest for my friends and me, and I complained that he was making too many rules. Allowed building materials, maximum qty of various things, etc. He pointed out that without these rules, it’d be perfectly acceptable to just fill the simulated valley with concrete—there’s no way that would lose the load bearing test. But it’s also not fun and defeats the purpose of the contest. _The constraints were important._ It’s the constraints that make it engineering. So you could use a beautiful piece of solid wood on the back of your dresser. But most likely that breaks the constraint of cost. Knowing where to save money on material without it getting noticed is where the engineering is.
This was a one off first-gen product that was sold almost 9 years ago. How long do you expect them to keep maintaining it? At least no one is attempting to build infrastructure on top of an Apple Watch—that can’t be said about google’s services.
Apple’s executives committed themselves to the lunacy of selling effectively disposable electronics housed inside an actual gold case. They knew exactly what they were doing and that decision is exemplar of their overall practice of building hardware that is impractical to maintain in the long run.
In a vacuum, maybe. But in any atmosphere, removing the thrust means negative acceleration due to drag. Thus the propellant could start to drift up/forward.
It depends if that structure ever burns or rots since this would release much of the same carbon back into the atmosphere
There is actually some research on growing fast crops to be immediately buried after harvest as a CCS solution but it’s a Herculean effort for what you get in terms of tonnes of CO2
I don’t think that’s true for devtools. I use FF devtools ever day, and it frequently crashes. Even the view source page has horrible performance issues when using cmd+f.
But also when Chrome first came out, it was legitimately better than the competitors. FF at the time was horribly slow. Teams was never better than Slack.
Chrome was faster and optimized for google services indeed.
However, Google was smart enough to know that being superior doesn't count. Firefox was not horribly slow, the leap from firefox over IE was massive. Chrome over firefox wasn't quite the same leap.
The average user has been pushed aggressively, they weren't going to do research on web browsers when they even didn't know what a web browser is. Google knew that.
When a tab crashed or got heavy usage on Firefox, the whole browser locked up.
Chrome didn’t. It was noticeably faster and more reliable.
Switching browsers isn’t something that people generally do lightly. You lose them, you lose them for a decade+.
That and Mozilla behaviour hasn’t been great over the past several years; like, forced advertising extensions, crypto, more advertising to turn off on a fresh install than _google_…
Manifest v3 will probably be the straw that forces me to switch back again, but reluctantly.
Your pink glasses are showing. For the longest time before quantum firefox was generally very slow and straight up locking ui thread when it feels like it.
Exactly. It's been a while and so a lot people either don't remember or were too young to really remember.
I was a Firefox user at the time (was using it when it was Firebird). People were already starting to shift away from IE towards Firefox at the time. A sequence of events where a person's computer was infect with malware, they asked a computer savvy friend for help, the friend "fixed" it, installed Firefox and told them to stop using IE is how most people switched browsers in those days. But Firefox was a slog and Chrome was a breath of fresh air when it was first released. So the sequence was tweaked to "install Chrome and tell you to stop using IE".
Chrome became what it is because Microsoft had tried to neuter the internet because they saw the web app potential and understood that it could undermine Windows market share. And when they realized that there was no stopping the internet, they spent several years incompetently trying to improve IE (and eventually Edge) before eventually going the "can't beat em, join em" route.
