Whilst this is a sound and logical approach, I much prefer the visual models in the Team of Leaders book by Stewart Liff and Paul Gustavson which show the leader just outside the team but still connected but importantly the team members all having strong connections between themselves rather than the diagram in this article implying every decision is still going through the lead.
You should look into Azure Local, formerly Azure Stack HCI, but it has limitations like no blob equivalent, but I see another commenter has already mentioned Azurite, as it is the solution that can work on some desktops. Azure Stack Hub is more complete but it requires enterprise hw, eg DELL blades etc, to run with mandatory redundancy requirements so not cheap.
This is just Mariner now allowed to exist outside AKS and rebranded. Used mainly if you are running c++ or .net components as unlike a more lightweight distribution like Alpine that ships with musl, it ships with glibc.
Company that outsourced a part of its business for operational and cost efficiencies upset when outsource company looks for operational and cost efficiencies.
This takes me back. I worked for a software company a long time ago that used these types of physical dongles and they would serve two purposes. One to prevent the software from running, and also to store data in one or more registers with more detailed license entitlements beyond just will it run. Like how many client connections are allowed, license expiry, etc. There was a switch to USB based dongles at some point and then software licenses often tied to physical attributes of the server that the software was running on.
Physical dongles remained popular with customers for longer than you would expect mostly in my often air gapped previous industry where the ability to rapidly deploy new hardware in the case of a failed server, transferring a dongle based license was a simple matter of plugging the existing dongle into the new server and you were up and running again. Many soft licenses required internet connectivity or required you to revoke the license from the old server and reassign on the new computer taking into account the new hardware identifiers for locking the license down to the specific server.
I can still hear them rattling about in my top work drawer as I opened and closed them.
I can’t be the only one that also sees either a mini Godzilla riding a normal sized cat into battle or a full size Godzilla riding a giant cat into battle.
On the web UI they sneakily slide in the Gemini icon exactly where the settings icon is after about 2 seconds of loading the page which caught me out for the first account I was updating. Really annoying.
Microsoft announced a while back that the end of EWS is coming for exchange online which means M365 accounts. They will start blocking EWS requests from October next year and only support access via Graph API. I understand the Thunderbird team are also working on Graph API support.
“When we meet as a team, we discuss these paint points and others in detail, because we want developers to choose Windows.”
Putting aside the “paint points” vs pain points, unless there is some MS Paint aspect I have missed, what about the broader user base who are not developers and simply want a robust OS to run their games and applications without all the AI and telemetry “features”?
Whilst this is a sound and logical approach, I much prefer the visual models in the Team of Leaders book by Stewart Liff and Paul Gustavson which show the leader just outside the team but still connected but importantly the team members all having strong connections between themselves rather than the diagram in this article implying every decision is still going through the lead.