Yes, they are predatory organizations by nature - in fact a closer operational model would be mafias. This was developed further by Murray Rothbard in his book "Anatomy of the State": https://cdn.mises.org/anatomy-of-the-state.pdf
1,563 karma · joined May 25, 2021
Yes, they are predatory organizations by nature - in fact a closer operational model would be mafias. This was developed further by Murray Rothbard in his book "Anatomy of the State": https://cdn.mises.org/anatomy-of-the-state.pdf
> Putting EAS and utilisation clamping together, we took a 15" M2 MacBook Air from about 6 hours of useable battery life just sitting at the desktop to about 8-10 hours of 1080p30 YouTube, 12-15 hours of desktop use, and an enormous 25-28 hours of screen-off idle time. We still have many more tricks up our sleeves to eke out more battery life, and a deep dive on EAS utilisation clamping is in the works. Watch this space!
https://www.notebookcheck.net/Asahi-Linux-improves-battery-l...
pkgsrc is by far the most KISS package manager for macOS, I like it.
It mostly feels like a single-user version of TOPS-10, which Kildall initially used to write CP/M. OS-8 and RT-11 also borrow heavily from it, making it basically the common ancestor of anything that feels "DOS".
You'll even find some code samples from 1948 on the website.
Have a look at the Wikipedia article. For some reason the French one appears to be the most complete, it even describes every unit of the machine and features some comparison with the EDSAC, SSEM, EDVAC, Zuse and Colossus.
https://fr-m-wikipedia-org.translate.goog/wiki/ENIAC?_x_tr_s...
Unfortunately I know no simulator of the stored program ENIAC.
On Windows, Wordpad was plenty enough for most needs, came preinstalled for free and barely consumed any resources, but I understand it's no longer shipping with Windows. Office 365 is now where the money is, even for basic needs.
Nowadays it's just a clunky mess of direct rendering interfaces bolted on top of legacy cruft from a long gone era. It's complex and inefficient.
You might also want to consider Void and Chimera. Void has a unique combination of technical simplicity, functionality, rolling updates and low maintenance along with some beefy repos. It's close to being the perfect desktop Linux to me.
Chimera uses dinit, which is closer to systemd's features, whereas Void uses runit, with is more of a minimal viable init + rc.
https://chimera-linux.org/docs/configuration/services
Then if a Linux kernel isn't a strict requirement, there's obviously NetBSD, from which Void takes inspiration. At last it's "the real thing" and not some adaptation, and a very underappreciated and overlooked Unix.
Quite a feat considering how horrifyingly difficult programming the 2600 was. Even the SDK was fairly barebones, basically a VT100 connected to a PDP-11 running RT8 and a 6502 assembler
Better yet, simulator at the schematic or microcode level. The KA11 was the first PDP11 CPU accurately simulated but the KD11 also seems to be working.
Then Linux started transitioning from a patchwork of loosely coupled replaceable components to integrated stacks in the mid-2000s, becoming ironically more and more of a corporate commodity rather than a playground for software freedom. You would need to define "the dark ages", as I understand casual users may prefer this trend, but for me, NetBSD is where the spirit remains. This is an entirely dependable, simple, hackable, grokable system and that's the way I want it to stay.
That's a bit of an understatement. NetBSD is primarily about preserving the original Unix spirit with broad compatibility across both hardware and software. This is the antithesis of, say, Fedora. NetBSD spans a vast amount of history, supporting everything from VAX and early Sun workstations to aarch64 and amd64, and from the V7 filesystem (1979) to ZFS. It will run both early SunOS binaries and bleeding edge software.
That being said, what I appreciate most about NetBSD is the dogfooding. Many core developers use vintage hardware or ARM boards, and routinely try the releases on antiquated hardware. Since software behaves like a gas, this helps keep bloat to a minimum. So there you have it: a deliberately old-school Unix that will run modern software yet still work like in the 80s / early 90s on basically anything with a CPU and MMU.
This is a commercial anyway, the low quality articles on their blog are just trying to give some credibility.
I wish there were an ARM-compatible version of DOS, if possible stateless. It would often be more suitable for an ARM board than a full-fledged Linux, given its almost non-existent attack surface, low resource consumption, and simplicity. Heck, I'd even like to see DOS microservices on stateless nano-VMs.