You mean Microsoft will recoup the cost of unbundling by charging more per product compared to the previous bundle, given that it’s now different products?
'cause at work the powers that be has gone all-in on MS and this decision won’t change a bit their “strategy”.
That’s a lot of words for “I’m too lazy to master the most essential tool of my professional life and keep it updated to my requirements”.
If you don’t want to do it, feel free to pay an Ubuntu support subscription, open a ticket, and get back to work. As you said: you should be working on your problem instead of whining. Or maybe you earn more whining?
There’s a saying that goes like that: “To a bad workman, there’s always bad tools.”
Modular’s Mojo might interest you - it just popped up in my news feed, it’s entirely a coincidence.
Others has answered the specific cases where TTM is paramount.
When time is less of an issue, in my experience it’s in no particular order a mix of:
All in all, instead of short term profit, it’s a lack of not-so-long term vision and engagement from everyone involved. They just don’t care.
Yeah, I’m the one in charge of fixing the mess, why you ask?
Your question is a bit vague but it looks to me that what you want is some sort of expert system of inference engine.
There might be some open source solutions, and there’s always the GNU Prolog language that might suit your needs.
I suspect that you won’t get a graphviz structure out of it though.
You can add support contract requirements for some pieces of software coming from vendors with so little confidence in their product that they’re rather have it run on an outdated dependencies environnement. A side effect of the logic you talked about, applied to software vendors.
Yet again an example of (for some, not-so) old, control-freak farts that just don’t understand the world they live in. The law proposal is entitled “Regulation of digital space”. As if a country could regulate an international network.
Sometimes I’m really ashamed of our politicians.
Unplug your mouse. Seriously. Do it. It might sound like the “kicking and screaming” method but you’ll learn to rely on your keyboard even for GUI tools and you’ll vastly improve how fast you navigate your computer. You should find yourself more and more in the terminal, obviously, but you may learn also some nice tricks with everything else.
Simple: because it goes against the KISS principle. The GNU tools that constitute the user interface to the system comes from a philosophy that started with Unix: simple tools, doing one thing well, communicating through “pipes” - i.e. the output of one tool is supposed to be used as the input of the next one.
Such philosophy allows to assemble complex logic and workflows with a few commands, automating a lot of mundane tasks, but also allowing to work at a large scale the same way you would work on a few files or tasks.
Graphical tools don’t have such advantages:
Beware though: as time passes, Unix founding principles seems to get forgotten, and some CLI tools manifest a lack of user experience design, diverging from the usual philosophy and making the life of system administrators difficult. I’ve often observed this on tools coming from recent languages - python, go, rust - where the “interface” of the tools is closer to the language it’s written with than the CLI uniform interface.
Given this trend, GPT 5 or 6 will be trained on a majority of content from its previous versions, modeling them instead of the expect full range of language. Researchers have already tested the outcome of a model-in-loop with pictures, it was not pretty.