What went wrong?

Your mind on BSD.

all of academia is filled with jews, it's part of their propaganda and control system just like MSM.

Lmao BSD is officially cucked garbage.

Universities have been turned into UNIX shill cults. It's not just Lisp machines they don't talk about. This PDF reads like an AT&T advertisement for UNIX.

cosm.sfasu.edu/gharber/353/notes/Unix_philosophy.pdf
Selfishness explains a lot about UNIX.


That's the opposite of the truth. These OSes are more reliable, faster, more productive, have better interfaces, and support more users than UNIX. UNIX weenies don't want you to be more productive because it would make you better than them.

For reasons I'm ashamed to admit, I am taking an "Introto Un*x" course. (Partly to give me a reason to get back onthis list...) Last night the instructor stated "BeforeUn*x, no file system had a tree structure." I almostscreamed out "Bullshit!" but stopped myself just in time. I knew beforehand this guy definitely wasn't playingwith a full deck, but can any of the old-timers on this listplease tell me which OS was the first with a tree-structuredfile system? My guess is Multics, in the late '60s.

Yes, and they've succeeded. Hordes of grumpy C hackers are complaining about C++ because it's too close to the right thing. Sometimes the world can be a frightening place. I've been wondering about this. I fantasize sometimesabout building better programming environments. It seemspretty clear that to be commercially viable at this pointyou'd have to start with C or C++. A painful idea, but.What really worries me is the impression that C hackersmight actively avoid anything that would raise theirproductivity. I don't quite understand this. My best guess is thatit's sort of another manifestation of the ``simpleimplementation over all other considerations'' philosophy.Namely, u-weenies have a fixed idea about how much theyshould have to know in order to program: the amount theyknow about C and unix. Any additional power would come atthe cost of having to learn something new. And they aren'twilling to make that investment in order to get greaterproductivity later. This certainly seems to be a lot of the resistance tolisp machines. ``But it's got *all* *those* *manuals*!''Yeah, but once you know that stuff you can program ten timesas fast. (Literally, I should think. I wish people woulddo studies to quantify these things.) If you think of aprogramming system as a long-term investment, it's worthspending 30% of your time for a couple years learning newstuff if it's going to give you an n-fold speed up later.

From the metroidvania-haters mailing list, 24 May 1991:
There already existed much better-designed games several years prior to both Metroid and Castlevania. But when the subject is brought up, discussions fall silent. Nobody wants to admit that game systems and home computers prior to the NES were capable of anything beyond Donkey Kong and Manic Miner. Doing so would be an admission that Nintendo is not in fact the saviour of video games, but rather a shrewd business that suckered many fools into its walled garden. And nobody likes to admit being a fool.

Attached: bruce_lee.png (320x200, 1.58K)

That's an example of a game way better than Metroid or Castlevania? The NES titles are far from perfect (as basically everything NES except SMB3 which is 9.5/10), but pls

Weren't *BSDs plagued by all those licensing issues which were settled only in the late 90s after the window of opportunity had been taken advantage of by Linux?

I think it's nothing malicious, just a matter of familiarity. Most kids didn't have home computers back then, so they never played those pioneers. But they had the NES, so they know Metroid. And there's no reason not to cherish that memory, it stands on its own very well. In fact, I dare say this: action-adventure games before Metroid were like fighting games before Street Fighter II, or FPS before Doom. Yes, the genre existed; yes, some of those games were pretty enjoyable; but when that one game came out, it got everything so right that it established a new standard and redefined everyone's expectations.

Still, I hate the "metroidvania" term, not just because the genre was done before, but because I prefer Castlevania as a strictly linear, arcade-style game.

It was more because of the superstition and apprehension that came after the BSD lawsuits. To their credit, ultimately, that issue was resolved. That's why it's called GNU/Linux, because GNU's Not Unix; the name's a testament to why it ever became relevant. What that didn't resolve was the fact that so-called copycenter licenses are still copyleft just as copyleft is a technique within copyright, making them just as hypocritical by their own logic as the freetards whom they're so disdainful of. The irony is that the utilitarian appeal of the simplicity of copycenter licenses is precisely why said licenses are so technically flawed and thus so legally dangerous. This is conveniently ignored because such advocates rely on the fact that big corporations don't have the financial incentive to abuse copycenter projects even if the power structure is such that they're in a position to do so.

Copycenter is that place where you go and pay a few cents to make a copy of paper or print a photo.