> mac window management is borderline unusable and I'm tired of installing 5 tools to fix it.
There's exactly two you need to get macOS eye-on-eye with Windows: Hyperswitch for an alt-tab that actually works and SizeUp to get a "window arrangement like Windows with Win+arrow keys".
Further migration pains can be eased with a Windows keyboard layout bringing special characters to where they belong in muscle memory (that however can and will bring pains with anything Adobe, their apps absolutely do not like non-Apple keyboard layouts and will refuse to load keyboard command presets) and Karabiner to map Ctrl+C/V to reduce hand strain.
Are you installing those tools regularly? I have a couple of invisible helper apps but Time Machine backups and Mac-to-Mac Migration Assistant has made those apps transparent. They're always there.
But you know what, I think I know where you are mentally. I was there 2 years after I first bought a Mac. I wanted a clean Mac. Nothing untoward, nothing that wasn't Apple. I got rid of that feeling and learned to love the Mac as a platform, to love the Mac because of its vibrant third-party developers. That's why I use a Mac even though Apple is often a bad steward of this wonderful bicycle for the mind.
I've just gotten the email and downgraded to the Essential plan for online Xbox gaming...which I'm not 100% sure I still need. Seems silly and short-sighted on Microsoft's part.
free users get the same value as paying customers...JetBrains can do as they please to get some value out of these users. Don't like it, pay up...I'm a long time JetBrains customer (since 2005). I've never asked my employer to pay for my licenses because their tools make me a better developer than any other options on the market.
Are you willing to pay for the true cost of maintaining these devices for ~50 years? The original price might have been 600 USD. I think the answer is regulation. Another idea: Sell the IP to a separate company who will support the legacy product for a fee. The original product will tell you how many years support is included (not lifetime). Later, there may be monthly charges. I doubt you will like that idea, but it is more honest. Germany has similar rules about car parts. Car manufs are required to make replacement parts available for X years after a car is manuf'd.
> Are you willing to pay for the true cost of maintaining these devices for ~50 years?
Sounds like Nest/Google didn’t think about that when they priced their products. That’s not the consumer’s fault. I’ve been de-Google-ing myself over the past couple of years and this is the final nail in the coffin. They could have given a partial refund, instead they insult customers with a “discount”.
How much do you think a server for config files costs? The true cost is very little here. You can make a server host a million thermostat connections for less than a thousand dollars per year. But let's 10x that to be safe, and have a sysadmin dedicate an overkill 1 day per week to keeping the servers happy. And we'll say the sysadmin makes well over median salary and costs $200k to employ.
For 2 million devices, that's $20k a year in server costs and $40k a year in sysadmin. For 50 years, that's 3 million dollars. So it would take a whole... dollar and a half per purchase to fund 50 years of servers.
Making this subscription-based would be fine, as long as I have my choice of providers. Because then I can run it myself on a raspberry pi or pay a big host a few dollars a year to handle my entire household of devices.
Google have the gaul to "offer" their newer devices at a discount - yes I want to pay you again for something I've already paid for...trusting that you don't this again in 10 years. I have 3 of these devices.
On the flip side, some companies have gone to extremes. I now have to MFA and provide a pin-code to authenticate. I have to do this several times a day. It's fucking mind-boggling how I can get anything done in a day when I spend so much time verifying who I am. I'm waiting for the next innovation...require a drop of my blood to log in.
Why is that extreme? I have to provide a pin code using MFA to my bank to authenticate, and their sessions are a lot shorter than your average developer or operator session.
And their actions impact far more than just my own account. Is it inconvenient? Yes. Does it work? Yes. Is it perfect? No, absolutely not but it is a useful layer in the cake.
Requiring a user to MFA once per day per device is normal for a work account - but that's already a lot compared to services like gmail.
After all, workers are mostly working in an access-controlled office or their private home; and your endpoint protection will be ensuring they're connecting from a company-issued laptop and that they have screen lock on a timer and a strong password.
I'm already validating something-they-know (FDE password) and something-they-know (OS password) and something-they-know (SSO system password) and something-they-have (company laptop). And once a day I'm validating another something-they-have (TOTP code/Yubikey).
Asking people to provide the second something-they-have several times a day seems like security theatre to me.
I don't know what it was about the writing style, but I couldn't make it through than a few paragraphs before giving up. One thing that LLMs seem reasonably good at is summarizing things. So here's your 200 word summary:
Two high‑school quarterbacks, decades apart, met the same fate. Jay Kutner, 18, Holy Trinity (NY), suffered a broken neck during a scrimmage in 1972 on a routine play. He became paralyzed, eventually passing away months later. His teammates dedicated their season to him and won a game he’d always meant to play in. His memory endured through field dedications and the stories of classmates and family.
Caden Tellier, 16, Morgan Academy (AL), collapsed during a game in August 2024 after being tackled. He fell ill, was hospitalized, declared brain‑dead, and donated his organs per his wishes. His school and community held a revival and memorials. Coaches, teammates, and townspeople gathered in grief and reflection .
The article draws parallels across time and place: both boys were promising athletes, kind leaders, beloved in their schools. Each death sent ripples through their communities, triggering reflections on football’s dangers and the weight of memory. Their stories affirm that some lives, however brief, outlast time itself ([espn.com][2]).
Add in my cousin, who told his coach he was ready to go back in after a first-quarter neck injury. One play later he was on a stretcher, and dead by morning.
The opposing team bought the biggest damn floral display you ever saw for his funeral. I can't imagine what it felt like.
It wasn't the primary reason I have a visceral revulsion from American football, but it strengthened it.
I love long form articles but this is way too difficult to follow, which is unfortunate because it’s both topical and eerie (great mix), but you just can’t have that many simultaneous strands as you jump repeatedly across narrative time. Unreadable.
reply