Bryan Lunduke's Substack covers computing history, Linux, open source politics, and retro operating systems.
HN links it for retro computing and open source stories, though one commenter disputes a claim that it copied material from Slashdot.
Ardi Executor. There's a recent fork at GitHub. You can run m68k binaries seamlessly. You don't need propietary MacOS parts, just the software.
But if you are some software preserver, having a libre option to run legacy media it's always good for historical reasons. I am a daily libre software user but I emulate ancient machines with propietary stuff just for curiosity. As it not a personal computing device I find it fine. It's just an historical toy and not my computing device. And, well, if you want to create libre engines for old Mac games (ScummVM, SDL ports...), for sure you need to at least emulate the old OSes and run the propietary game in order to compare the output and correctness.
Also, it already exists "Mac" for x86. It was Rhapsody DR2 and it could run Classic Mac software and NeXT one too. It was like a blend of these two. OSX it's like NeXT Step concept 2.0, with few traces of Mac Classic. Qemu will run it fine.
https://lunduke.substack.com/p/hands-on-with-1998s-rhapsody-dr2
I think you got this one wrong.
The original posted URL was:
https://lunduke.substack.com/p/richard-stallman-the-state-of-the
The grandparent comment says that Lunduke ripped off Slashdot. I don't see that. There is one quote that's the same and several that I see that are different. You claim you changed it to the original source... the original source would be the Libreplanet link here:
https://media.libreplanet.org/u/libreplanet/m/the-state-of-the-free-software-movement/
So both Lunduke and Slashdot are posting news about LibrePlanet and it's not clear one ripped off the other, other than having one quote that's the same.
It seems like you went with the above commenters without investigating.
I have no affiliation with Lunduke. I'm not a paid subscriber to his journal, I just get it by email sometimes.
Project time/resource constraints not withstanding, wonder how this compares to other c-64 os alternatives.[0]
?? future options ?? : Unix bootable from a cassette tape drive? :-)
?? c-64 unix server with ports to hook up one or more c-64's via CaTer (Cartridge Terminal) -- perhaps best done via tcp-ip 'ports'.
?? fuse[1] for c-64 to be able to 'read' other floppies / c-64 unix swap space over tcp-ip.??
?? "modern" 5.25" for c-64 via c-64 variant of greaseweazle[2] ??
-----
[0] "The Many Operating Systems of the Commodore 64" : https://lunduke.substack.com/p/the-many-operating-systems-of-the
[1] c64-fuse (perhaps over c-64 tcp-ip) : https://en.wikipedia.org/wiki/Filesystem_in_Userspace
[2] greaseweazle : https://github.com/keirf/greaseweazle
Prior instance of principal-agent problem in open-source, https://lunduke.substack.com/p/linux-foundation-spends-just-34-of
> The Linux Foundation — the organization that effectively controls Linux and employs the creator of Linux — only spends 3.4% [of $177M] on… Linux.
Is the proposed SFC copyright assignment intended to be temporary, e.g. could it be returned to the creator after a legal case is won? Why is it not sufficient for SFC to represent the copyright owner? Would joint/minority ownership be an option?
Leaving aside legal concerns, could code maintainers possibly lose the ability to steward their OSS community and set governance policy, after they surrender copyright?
Respectfully, that's a bit of a stretch. Impaired human memory and increased risk taking are coefficients that would impact far more industries than software. I think the notion is that software, in particular, seems buggier. IF these side effects of repeated COVID infection have anything to do with software bugs, I would think it's contribution would be dramatically smaller than say LLM assisted coding, rapid merging of code, lack of human review.
Just a couple of examples:
- Linux kernel ai commits (https://lunduke.substack.com/p/ai-submissions-to-linux-hits-new)
- Omarchy 4 30k lines of ai generated code (https://x.com/dhh/status/2057907663967543618)
My main worry is that someone might register a trademark for that name and cause all sorts of issues for me. Worst case scenario I could just rename the project, but my mind goes to the time when Firefox browser, at the time Phoenix Browser and firebird browser, kept bullying other open source projects and it was only their copyrights that kept them from needing to change their branding.
https://lunduke.substack.com/p/why-is-firefox-called-firefox
Thing is, idk how often this stuff happens and if it is something I need to reasonably be worried about especially since another non-trademarked piece of software has that name already