101–110 of 163 posts
I bought this when it came out, but thought it was horrible. The only good bit was the preface by one of the Unix authors (Ritchie?). The rest just seemed like whining by people that didn't really get the Unix philosophy.
Both your statement and my statement don't really mean anything.
Earlier quoted context omitted.
> I suspect most CS students these days start around web technologies using VS Code in stock Ubuntu More likely, Visual Studio Code on macOS.
haven't the google chromebook kids hit the college market yet? wonder if they'd go for macOS at all
For computer science, the only people who buy Chromebooks are the people who install Linux on them or have another machine to SSH into.
Earlier quoted context omitted.
> This is a tongue in cheek but also piece of shit MIT propaganda piece mostly written by the clowns who created the abortions that were Multics and LISPMs. Sure--the people who wrote systems with opposing philosophies to the "unix philosophy" are going to be the ones who write this book. And that they failed-in-the-market ("abortions") is already evident by the fact that HN is probably majority unix (mac) or unix-li…
LISPms, Multics, Symbolics machines all run instances of software that depended upon custom instructions, tailored precisely for the languages which they executed, and could not be ported to any other machine.
https://github.com/ynniv/opengenera
you first have to get the opengenera sources, though. But they aren't hard to find.
Earlier quoted context omitted.
If your time is worthless, Windows can - and always could - be free. But if your time is worth something, it's better to shell out that $$$, and also be legally and morally on the safe side.
Pretty sure installing Kmspico is faster than buying a serial key.
Find a proper key for your edition here: https://docs.microsoft.com/en-us/windows-server/get-started/...
slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
slmgr /skms kms.digiboy.ir # just an example of many KMS servers that exist
slmgr /ato
Earlier quoted context omitted.
Eh, what? At the time (1994) the handbook was written reasonably priced alternatives were MacOS and Windows, both of which froze all the time and had horrible programming environments. AIX, non-free, was notoriously horrible, too. And the Wirth systems that you promote here were actually free. So what exactly is the great stable commercial alternative in the 90s?
Digital Research produced some nice usable systems in the early 80s. MP/M was a multitasking version of CP/M available by 1981. In the mainframe world, TOPS-10/20 and VMS were both exemplary. From the user POV, the former was one of the best command-line systems ever created, with none of the insane user-hostility built into UNIX command naming. Dave "VMS -> NT" Cutler absolutely hated Unix, and it shows. But we're r…
Earlier quoted context omitted.
Rereading the section on NFS again, I suddenly realize that I was foolish to have skipped it as out of date. Since my last read I have encountered some incarnation (heh) of every single one of the problems listed in that chapter. I'm betting v4 isn't much better either. Is there a good network file system solution!?
What's wrong with nfs v4? It was quite a bit faster than the alternatives last I checked.
> There’s only one problem with a connectionless, stateless (file) system: it doesn’t work.
> Example #1: NFS is stateless, but many programs designed for Unix systems require record locking
> Example #3: If you delete a file in Unix that is still open, the file’s name is removed from its directory, but the disk blocks associated with the file are not deleted until the file is closed.
(Example #2 is a non-issue)
The security is still lacking, and the system still can't handle failures.
Yet, yes, it's faster, easier to set-up, and more widely supported than the alternatives.
Earlier quoted context omitted.
counterpoint: launchd works.
What doesn't work about systemd?
After years of dealing with systemd, I've finally given up on it, and I'm back on openrc.
(Yes, I know I'm not answering your question, but I'm not up to the task... ;P)
Try unixux. Really.
Earlier quoted context omitted.
Yes, using standard POSIX tools wasn't the best experience of the world. What helped Unix succeed was that originally Bell Labs wasn't allowed to sell it, so they gave it to universities for what was a symbolic price in comparisasion what a standard OS used to cost, alongside its source code. So naturally many stundents from those universities went out and started businesses based on UNIX, like Sun for example. One o…
Eh, what? At the time (1994) the handbook was written reasonably priced alternatives were MacOS and Windows, both of which froze all the time and had horrible programming environments. AIX, non-free, was notoriously horrible, too. And the Wirth systems that you promote here were actually free. So what exactly is the great stable commercial alternative in the 90s?