Feyter

I considered deleting this slop, but you guys having way to much fun in the comments :D

Forking is easy. Maintaining the fork is the hard part.

If the question is really about “can”, than the answer is definitely yes.

If it’s about if you should, than it’s a clear no. Because storing data in a GitHub Project is not the use case. Nothing in the protocols or the platform itself is optimized for that. Also GitHub could just pull the plug of your project if they ever feel that it is against their terms.

I try to add something to the understand.

Especially in old games, the program code (what happens if you press a button, what happen if your health bar goes to zero…) is often handled in the same memory structure as the game data (sprites, your entered player name, you inventory…) If you glitch a function that should edit a memory block of game data (e.g. reduce the players money or rename a Pokémon) to do it’s operation on a program code block instead, you can reprogram the game while you are playing it and even make it a different game.

A different famous example is Super Mario Land. If you glitch trough the level borders the game is displaying all kind of data (game data and program code) as level blocks that you can walk on. Some of those level blocks are distructable, which is setting this memory block to a different value. By carefully destructing the correct blocks, you can change things like how many life’s you have. But if you hit a wrong block, the game will potentially crash because you changed the program code to something that doesn’t make sense.

Apparently, there is even a movie about this joke… https://en.wikipedia.org/wiki/404_(film)

Oh boy… now I discovered that Sarah Connor once fall in love with a Kilrathi. The 80s/90s where a interesting time.

Wouldn’t be so sure about that Heisenberg principle. This Schrödinger’s Cat thing must come from somewhere…

Exactly my stand is, that cat’s don’t differentiate much between play and hunt.

It’s a joyful experience for them (most times), not a stress situation.

Don’t worry she probably not thought about killing you, but was just happy you signalized to play “kill this thing” with her.

I have to ruin the joke but this is not really accurate.

Cat’s are not thinking about “killing” when they have this look. It’s the “play & snack mode” a very positive feeling for the cat. They don’t have the idea that they might hurt or kill another living being in the process.

The real “kill mode” is when having a dispute with other cats (or cat like animals) that they identity not as a snack but as a cat like thing. And this look is much closer to the left picture.

I wouldn’t count it as desktop Linux as well. But I think it’s much more likely for chrome to take over Windows than it is for macOS.

Apple business strategy is to sell overpriced premium hardware. They don’t want to sell 300$ notebooks.

I think you underestimating ChromeOS

deleted by creator

To use this side you have at least be as pale as #FFDAB9… But nobody is enforcing it.

there are problems with the old driver? Man you think at some point a tecnology is just complete, but apparently no.

No one can exit vim. It’s simply not possible.

There are even legends that the devil himself was onced tricked into opening vim and is stuck there since.

I think there is a lot that the author is right about.

However, removing X11 season was a decision of the Gnome Team not the Ubuntu team and I completely respect this.

Yes you can keep shipping it with the X11 optio, but someone has to maintain it. The gnome project has only limited resource so it’s either removed or an unstable mess… removing in this case is always the better option IMHO.

I think the core takeaways from all this is, we (as a community) should definitely no longer recommend Ubuntu as the default distro for newcomer to the Linux world.

We all have been idiot savants at some point of our lifes :)

I’m pretty sure those machines still run WinXP at best ;)

And yes that’s exactly what I said. You still can run Linux on a 486 for this special edge cases, it’s just that the Linux Kernel team will no longer provide the service for maintaining it. If it is such an important thing for crucial industry machines, they can definitely pay someone patching it back in.

For the overwhelmingly majority of Linux use cases it’s not a concern anymore. So why should they do the extra work, instead of spending the time elsewhere?

Exactly! Just because there is support for a stone age CPU in the Linux Kernel, doesn’t mean every single modern Linux compatible software is running smoothly on this.

Of course, from the Mac/Windows point of view it was the correct thing to ditch such old stuff. Because they are concerned about having a stable product that is running on modern hardware. Keeping this old stuff in, makes it more complicated to maintain their system and therefore more suspectable to errors.

Linux could only keep this support up for so long, because somewhere there where people that though it would be worth care about for 28 years. And even now it’s not over. You can modify the kernel and patch 486 support back in again on your own. So “incompatibility” doesn’t really exist with a open system. It’s just that nobody at the core kernel team will do this service for you anymore.