This is how Firefox fell behind Chrome and bled their entire market share. The strategy of letting Chrome out innovate them and then copy what they think is good is not a strategy that works.
It works pretty well for Apple
Readit Newsamethyst commented on Firefox will have an option to disable all AI features mastodon.social/@firefoxw... · Posted by u/twapi
amethyst commented on Two guys hated using Comcast, so they built their own fiber ISP arstechnica.com/tech-poli... · Posted by u/LorenDB
If you haven't already, check to see if either Google Fiber or Monkeybrains is available in your area. Last I checked, the regs are still in place that prevent landlords from denying you access to an ISP of your choice.
Google Fiber isn't rolled out to most of the bay area. Monkeybrains is wireless with speeds significantly slower than what Comcast offers me. I've checked just about every wired ISP possible, and Comcast is the only option that services my neighborhood.
And FWIW, I own my house in the east bay — I am the landlady ;)
amethyst commented on Two guys hated using Comcast, so they built their own fiber ISP arstechnica.com/tech-poli... · Posted by u/LorenDB
amethyst commented on Two guys hated using Comcast, so they built their own fiber ISP arstechnica.com/tech-poli... · Posted by u/LorenDB
I’m sorry I still don’t get it. Could you explain that in different phrasing ?
A comcast customer always had the option to pay for unlimited data. I get that part. What is the 2nd part? “Started offering it as standard” means what?
In markets where Comcast has actual real competition, they "include" the unlimited data (aka no cap) with no extra charge when you sign up for their gigabit plans.
amethyst commented on Upgrading an M4 Pro Mac mini's storage for half the price jeffgeerling.com/blog/202... · Posted by u/speckx
amethyst commented on Sapling: Source control that's user-friendly and scalable (2022) engineering.fb.com/2022/1... · Posted by u/lordleft
Test coverage at Meta is pretty far off from this
And yet, as someone working on core language infra, we apply exactly that sort of ideal when making changes. If a diff doesn't break any tests, then it's "safe" to land, and if something does indeed break afterwards, then it's the broken team's responsibility to fix forward or otherwise provide proof that it's a big enough problem to roll back. If we end up in SEV review for a change, and there were no broken tests on the diff, then there are going to be some hard questions for the team that didn't write tests.
Ie, tests aren't mandatory, but if you aren't writing tests, it's your responsibility when someone else's change breaks your project.
amethyst commented on Ball: A ball that lives in your dock github.com/nate-parrott/b... · Posted by u/Bluestein
It looks like this repo is is a rewrite of an earlier "scmpoo.exe" that roamed the internet in the mid-1990s. That was fun to set up on school computers to automatically launch at random times.
That's the one I had. I got it from my friend in sixth grade, and who knows where he got it from!
amethyst commented on Ball: A ball that lives in your dock github.com/nate-parrott/b... · Posted by u/Bluestein
I still miss my desktop sheep every once in a while: https://github.com/Adrianotiger/desktopPet?tab=readme-ov-fil...
Edit: the best part was running it a couple dozen times to get an entire flock walking, falling, and rolling all over your desktop, and watching everything grind to halt under CPU strain!
And this didn't get them in trouble with the fire marshal?