Acronym use here to single being part of an in-group. It is one of the most annoying shift in tech language over the past decade. I partly blame it on all the certification testing that has popped up over that time frame.
It isn't like there hasn't always been tech acronyms but they are so causally communicated these days without regard for audience.
Would rather a more robust and distributed app store system that figures out how to police these edge cases of fraud rather than one vendor (Apple or Google) whose monopolies push developers into subscriptionware across the board. Something more akin to how internic moved from one domain name registrar to what we have today, chock full of competition and new top level domains.
It feels like independent development on devices has slowed in recent years. More stores appealing to different developer models/tools and monetization strategies please.
I have been trying to trouble shoot a Time Machine issue since upgrading to Tahoe. It is usb backup. So far none of the most recent stated fixes work.
An initial backup on newly formatted disk will run but very slowly. Perhaps reaching 100% but it never finishes. At some point the percentage will change and the backup will stay stuck at somewhere near 10%. Cancel backup and run it again. Gets to ~10% and stays stuck. Multiple drives. Re-fs'ed. Boot into safe mode. Networking off. Etc, etc. etc. The TimeMachineMechanic app doesn't have any revealing feedback. I can run a full tar backup to the same disks.
No idea.
I haven't tried backing up to a network share but really, it shouldn't be this difficult.
Clearly someone didn't test a bunch of edge cases when pushing this one out.
Your post reflects another online observation. With the rise of online sports books, this sort of predictive doomerism has flooded almost every team's online comment section. It no longer feel like fandom or community in the same way. Just lots of voices that will be glad to say, "I told you so," in the loss and crickets with the W. Wish there was some accountability mechanism for all the negative noise broadcasted into the channel.
When I was part of a team developing a highly durable texting protocol, those of us in NYC would regularly test messaging while riding the subway. Between stations, you didn't have network access but different devices upon entering the next station would handle and recover from the interruptions in various ways.
The subway produced so many repeatable network connection edge case problems. It was fantastic.
A shorter and consistent iteration cycle by meaningful working groups on the legislation until a long term workable legal framework is enacted from the lessons gathered.
Something like, every four months, X working group will present updates to legal recommendations and they will be voted on at that time. Allow for public input throughout the process. Mistakes will be made but can be short lived with the correction cycle.
They are trying to tightrope walk complex legislation for tech. Might as well take on a tech release cycle to get out of beta and into release version 1.0 of these laws.
They aren't directly linked. I just like the idea of cataloging all of the time bounded limits in CS. Reading the wiki entry and having forgotten the exact date for when Unix time comes to end, although knowing it is close, i figured others might enjoy seeing the 2038 date too. Based upon voting, I was wrong.