Just checked the tivoization definition. (Guess I should have done so, when reading the original thread, when I felt unsure from their explanation of the word).
So, it has to be runnable on the same hardware after modification. It makes sense now.
I seems like something that would be good in case the solution is being used for a long period and would make sure the user doesn't have to bear the burden of finding another platform that would run the binary, in case a library update is required. This would be in the interest of even corporate clients.
After each iteration, project managers discuss bottlenecks, identify waste and develop a plan to eliminate it.
1st iteration:
Project Manager A: Requiring approval of multiple Project Managers for the same thing is causing a bottleneck.
So is having to wait for a specific manager for a specific topic.
Resolution: Let all managers approve everything and need only a single manager's approval.
2nd iteration:
Project Manager B: There are too many redundant managers. It's a waste of resources.
Resolution: Get rid of all mangers but one. Actually, let the engineers manage themselves.
... Except when it doesn't.
I use Gnome at work, on an older (supposedly stable) version of RedHat and there are a few ways it breaks, but when it does, it Breaks Bad. I would be fine with said breakages if it were not trying to claim focussing on having lesser bugs and in turn reducing customisability to such low levels that changing stuff like animation speed (which, by default is set to productivity destroying speeds), is not possible from the default repos.
KDE and related applications are much more tolerable and when I find a bug I tend to be happy to report.
Who says you can't have an underground workshop, a gaming setup, a matrix+lemmy+mastodon server, an underground FTTH connection, an escape tunnel with a joyride leading straight to the highway and 100m below all of that, a nuclear power plant.
Ok, maybe someone will say something about the last one, but... You know?
I kinda expected that to happen, since there's already enough to fit all required functions. So yeah, even this is not a good enough criteria for bit rating.
those original 8-bit intructions still exist, and take up a huge part of the encoding space, cutting the number of n-bit instructions to more like 2^(n-7)
err... they are still instructions, right? And they are implemented. I don't see why you would negate that from the number of instructions.
As in, 8 bit 8085 had 28 possible instructions, 32 bit ones had 232 and already had enough possible combinations that we couldn't come up with enough functions to fill the provided space.
Reading this as someone who torrents debian ISOs instead of directly downloading then in the hopes of reducing server load, while at the same time, not torrenting any pirated stuff.
"I can't be racist because, I hate absolutely every one, irrespective of caste/creed/religion/number and shape of genitals/color(also, color of genitals)/age/region/domain/kingdom/phylum/class/order/family/genus/species/base chemical composition/geometrical structure/level of consciousness/lifespan/definition of life, equally."
Yeah, I thought so too.
Guess the V3 has some major, thoughtful changes.