It might be wordsmithing to skirt around "robot" as a fully autonomous entity. Much like their FSD, I expect they aren't going to deliver full autonomy anytime soon.
So much of it is a problem of execution. If people could use Linux without ever having to know what a terminal is (much like the average Windows user doesn't know what PowerShell is), then it would actually be quite successful. It has gotten better over the past decade, but it still suffers from endless paper cuts and the odd issue that requires a shell session to fix. I will say that Valve's SteamOS has come the closest to avoiding this trap. You can use a deck without ever having to touch a CLI.
It's been an unfortunate re-occurring issue for me as well. Recent hardware is much better about this, and I too have seen the performance bumps at the cost of software compatibility. I feel like if Adobe brought their CC suite to Linux I'd have no reason to ever use Windows outside the random game that _needs_ it.
At least on the latest Sequoia, there has been no hard requirement for an online account. They nudge you towards it, but you can decline and continue. As far as I can remember, macOS has never required an online account to set up a Mac.
You might need it for the App Store if anything, but even then... You don't need the app store for installing software. Mac is at its peak currently, though the new glass UI stuff is a little over the top for me. I miss the old simpler UI. I'm sure I'll get used to it eventually.
The geometry means it's not so bad. The 'plane is going horizontally, but your initial acceleration is effectively vertical. Thinking of the triangle of forces, the 'plane is going in the sin(θ) direction (therefore with speed) whereas you are going in the cos(θ) direction ... therefore not travelling much.
So the geometry works in your favour, and the forces on you aren't that bad.
Atlas being created is kinda the shot across the bow. You can integrate with us willingly, or we'll hook into your web apps anyways. One retains at least some control. Same outcome as Disney's deal with Sora.
A core SRE principle is that "machines/servers are cattle, not pets". They shouldn't be special or bespoke in a way that makes replacement painful or difficult.
I've heard the term used for servers before but not version control repositories. I just don't understand what it would mean for a git repo to be a cattle vs a pet. Like what is an example of a cattle repo vs a pet repo. The metaphore just sounds like gibberish to me idk.
Unless all it means is that that you can have more than a few like the other commenter said but I didn't think that was what the metaphore meant with respect to servers so again I have no idea lol
To me it would mean that a git repo should not have scripts, runners, etc. configured that we don't have the means to easily and readily replace. It should all be documented and understood well enough that we could kill the repo and init another at will.
reply