Have a colleague who went from over $300k/year to like a $50k/year job. Basically something to vaguely keep the lights on while his savings took care of itself. Way too young to retire, but he figures he can be ok with his savings and bonuses he had over his high paying career.
jj4211
Never wanted to climb the ladder, but it was the only way I could really get better pay.
The higher I go, the more I can't stand the conversations. Being straightforward is a career killer. Competing with folks that talk big without knowledge, knowing I need to carefully balance working with them while making sure my ass is documented and covered for any blame when they screw up and want to throw someone under the bus.
I have generally still loved talking to the "grunts" and customers. People who have real problems and doing real stuff without so much office politic crap going on. Not people trying to write blog posts to try to sound smart without actually doing anything or actually knowing the material.
Ironically, Microsoft platform as of yet still is pretty much a given that Linux may also run, with the exception of some of the Surface systems, but the ones no one wanted anyway. Apart from SecureBoot, Microsoft is picky enough about firmware specifications that are open, Linux can more easily be customized than random embedded things. Some things were rough, like ACPI implementations that didn't comply strictly with the spec but microsoft happened to tolerate it, but fundamentally the Microsoft approach of outsourced everything makes for better chance for third party OSes.
Motorola has been under Lenovo for over a decade now, and still is, as a clarification.
The new thing is that for whatever reason, Motorola themselves has explicitly declared that some as-yet specified 2027 flagship model will officially support Graphene (though you have to load it yourself). This goes beyond just letting the community figure it out if it happens to be workable.
Now as to whether they follow through on that, hard to say. Lenovo broadly sometimes makes announcements and then backs out without explanation.
They are compatible with some existing and future phones. Google's in-house processor decided to skip on an extension that the broader ARM ecosystem seems to continue to value. Graphene didn't invent this extension. I presume that their compatibility with upcoming motorola devices indicates other mobile device processor designs implement the extension just fine.
Actually, Motorola has more market share than Pixel.
Though Google mainly cares about the software ecosystem, so they explicitly don't care about Graphene since it's not an outcome they want in the industry anyway.
One near me does it. They just happened to have a special where a month cost less than a single wash and my spouse went for it.
Nightmare to cancel the damn thing.
It's pretty much codified. 9 mph over means pretty much nothing. If you are a little over that? Everyone knows the courts will probably knock it down to 9 over just by asking.
As another comment points out, it's works for being selectively enforced. Almost every car on the road can be pulled over. Even if you are going the speed limit, you might get pulled over for impeding traffic.
You are right about American freeways. City roads tend to have a lower speed limit that is probably appropriate and it would be unsafe to go faster.
Rural America will have little roads with deer and intersections at blind curves and say 55 mph seems about right.
Note that Debian has had a purist approach to intellectual property, and the common sense practical view that 'obviously' it has to be ok or else the entire industry would be hopelessly screwed by now, I could see them trying to stick to their guns.
There are still court cases flying about and so far the focus has been by rights holders versus the AI platforms. Those have thus far been pretty favorable for the platform holders, but there's a catch.
The platform defense has been that "sure, we trained on copyrighted works and sure, the model can produce copyright violations, but when a violation happens, it is the fault of the operator and they should be on the hook for violations". So it remains possible that someone comes after an AI user for making a knockoff, and given the context, the AI user might be making a violation without even knowing they are.
So accepting a contribution under GPL might get them in hot water because some company decides that the submission looks too much like their proprietary code, and they can draw a line from their codebase being open to AI ingest to it landing in a codebase.
Sadly, this is a bigger risk for open source than closed source, as the closed source is harder to detect such things.
Not him, but I almost never boot windows, but the other day I had to change a part of a a stupid powerpoint presentation that only could be done using Powerpoint desktop app. Wine has not done so well with it, Libreoffice wouldn't do the thing right, and browser based office can't touch 'master slide' content.
I'll second the volunteering, though I never really feel comfortable socializing among the volunteers, it still feels good actually doing something I think matters, but at the same time know I'm utterly replacable and no one would specifically need me to do any of it.