Speaking of Ragnarök, the whole premise of CatastropheOS was that there would always at least be plenty of old and salavagble Z80's waiting around to reboot civilization the day after. I think they supported 6502's as well, but they bet big on at least Z80's surviving. Personally, I favor the land of the lost 6809, and what might-have-been in an OS/9 derived world.
Posts by tychosoft
7 publicly visible posts • joined 1 Mar 2018
The eight-bit Z80 is dead. Long live the 16-bit Z80!
NetBSD 10 proves old tech can still kick apps and take names three decades later
In a sense I always felt NetBSD remains most true to the original heart and soul of the original Berkeley Software Distributions of Unix, and so in that sense it is also much older, too. But BSD has always been about what is new and possible, too. FreeBSD is initially somewhat friendlier to use as a desktop, especially with desktop focused variants like GhostBSD, but it is also more focused on chasing Linux distros and what Apple wants than simply being a BSD, and I do think this is okay, too. As for OpenBSD, well, the fish tribe is kinda "special" ;).
Open source versus Microsoft: The new rebellion begins
Perhaps one difference for why now is that there is a "home team" to help prop up again. Both past times Suse was on some weird journey in strange hands, so essentially mia. Curiously enough it is returned as much a cloud vendor as an open source one. But what may be important it is a German one again! Canonical? Hardly European even before BR-Exit, let alone German. Red Hat? Exchanging one kind of US landlord for another. This may also be about the rise of a new protectionism, the "new" nationalism, etc.
How GitHub Copilot could steer Microsoft into a copyright storm
Re: No Solidarity with A.I.'s run for profit!
Actually, many proprietary software companies were already prohibiting their developers from using resources like stackoverflow toward the end of last decade precisely because they feared snippets of code from there might cross-contaminate and taint the licensing of their own products. Hence, I don't see why these same companies would not similarly fear co-pilot, which does so with even greater ease.
Liability has already been defined
There is already case law establishing that an AI cannot be an "inventor", in respect to patents, and that the "operator" / provider of the AI's training and output is. This presumes then that the liabilities also follow the same path, and this leads to Microsoft. Furthermore, the damaged party, which is the originator of the training data, may not even be a party to any agreements with github or microsoft.
What's all the C Plus Fuss? Bjarne Stroustrup warns of dangerous future plans for his C++
Boring. The phone business has lost the plot and Google is making it worse
Re: Form factors
Indeed, even a just somewhat thicker/heavier phone with the extra space used for a better battery life seems a win-win to me, too. Of course I also do remember a period when lead slugs were put into telephone handsets because they felt much "cheaper"/"flimsier" to people once the old carbon mike and classic speaker was replaced.