/unixhate/ #1

I mentioned a specific HARDWARE feature of Lisp machines, nothing more.

Ah yeah, forgot about that

And that's why I said OBJECTIVELY.
and EVEN if you IGNORE that, you guys have been shitting up this board with your lisp machine shilling and your failure to come up with a design of a better system than unix, which has already been done roughly 20-30 years ago by bell labs.

And I have seen you fags over IRC. You guys know jack shit about programming aside from, maybe fizzbuzz.
This will be the last (you) I'll give you.

Top kek, who's the midget behind this post? var-g?

Hang yourself.

Trips of truth

𝙵𝚘𝚞𝚗𝚍 𝚝𝚑𝚎 𝚄𝙽𝙸𝚇 𝚞𝚜𝚎𝚛𝚜. 𝚆𝚑𝚎𝚗 𝚊𝚛𝚎 𝚢𝚘𝚞 𝚐𝚘𝚒𝚗𝚐 𝚝𝚘 𝚜𝚝𝚊𝚛𝚝 𝚞𝚜𝚒𝚗𝚐 𝚊𝚗 𝚊𝚌𝚝𝚞𝚊𝚕 𝚐𝚘𝚘𝚍 𝚙𝚛𝚘𝚐𝚛𝚊𝚖𝚖𝚒𝚗𝚐 𝚕𝚊𝚗𝚐𝚞𝚊𝚐𝚎, 𝚕𝚒𝚔𝚎 𝙲++?

a-am I allowed to come back? uwu

Umm, so since one of you said to "start using an actual good programming language", that got me thinking. Is there any other language out there that has the same level of performance as C/C++? That seems to be the most common argument in favor of those languages: writing low level stuff that needs to be fast.
Is the Rust meme capable of that? I know people make fun of it a lot here, but people have already been trying to write an OS in it, and the shills say it's safer or something, so wouldn't that be a possible C-replacement? of course the community sounds like a bunch of controlling meanies, but is it as good as they say on a technical level?

Do any of you have any other possibilities? ^.^ I think it would be nice to see, as it seems whether we want to replace C/C++ or not, we can't do it without finding something that's as fast.

Attached: boy.jpg (736x1021, 87.52K)

Bullshit. UNIX weenies believe that all Multics innovations came from their "eunuch" OS because they don't know anything about Multics. The hierarchical file system and other parts of VMS, VME, Xerox workstations, and Lisp machines are based on Multics, not UNIX.

en.wikipedia.org/wiki/ICL_VME

They're an amazing lack of quality control.

Accomplishments don't disappear just because you don't know about them.

Modern hardware does have bounds checking. x86 has segment limits and a BOUND instruction that can be used for bounds checking since the 80s. RISCs don't have it because the PDP-11 is not modern.

What I find disgusting about UNIX is that it has *never*grown any operating system extensions of its own, all thecreative work is derived from VMS, Multics and theoperating systems it killed.

If you want to remember the actual last time you edited those files, then keep your own damn database of dates and times, and stop bothering us Unix Wizards.I thought this is what RCS is for.I'm TA'ing an OS course this semester. The last lecture wasan intro to Unix since all other operating systems were onlyimperfect and premature attempts to create Unix anyway.Some lecture highlights...An aside during a discussion of uid's and many a unixweenie's obsession with them: "A lot of people in the Unixworld are weird."When asked if Ritchie et al regretted some otherinconsistency in Unix metaphysics, "These guys probablydon't care."Have another twinkie.

Some Andrew weenie, writing of Unix buffer-length bugs, says:> The big ones are grep(1) and sort(1). Their "silent> truncation" have introduced the most heinous of subtle bugs> in shell script database programs. Bugs that don't show up> until the system has been working perfectly for a long time,> and when they do show up, their only clue might be that some> inverted index doesn't have as many matches as were expected.Unix encourages, by egregious example, the mostirresponsible programming style imaginable. No errorchecking. No error messages. No conscience. If a studenthere turned in code like that, I'd flunk his ass.Unix software comes as close to real software as TeenageMutant Ninja Turtles comes to the classic Three Musketeers:a childish, vulgar, totally unsatisfying imitation.

how old is this book, mister lisp meanie? did they not have postgres back then?

Attached: postgresql_logo-555px.png (555x617, 45.99K)

>>９３８８０５
Ｆｉｒｓｔ ｏｆ ａｌｌ， ｒｅｐｏｒｔｅｄ ｆｏｒ ｔｒｉｐｆａｇｇｉｎｇ， ａｖａｔａｒｆａｇｇｉｎｇ， ｓｈｉｔｐｏｓｔｉｎｇ， ａｎｄ ｒｅｄｄｉｔ ｓｐａｃｉｎｇ．

Ｓｅｃｏｎｄ ｏｆ ａｌｌ， Ｃ／Ｃ＋＋ ｉｓｎ＇ｔ ｒｅａｌｌｙ ａｓ ｆａｓｔ ａｓ ｙｏｕ ｔｈｉｎｋ． Ｉｆ ｙｏｕ ｎｅｅｄ ｌｏｗ ｌｅｖｅｌ ｓｔｕｆｆ， ｙｏｕ ｎｅｅｄ ｔｏ ｕｓｅ ａｓｓｅｍｂｌｙ． Ｃ ｉｓ ａｌｍｏｓｔ ｎｅｖｅｒ ｕｓｅｄ ｉｎ ｅｍｂｅｄｄｅｄ， ｙｏｕ ｅｉｔｈｅｒ ｕｓｅ Ｆｏｒｔｈ ｏｎ ａ ｄｅｄｉｃａｔｅｄ ｓｔａｃｋ－ｂａｓｅｄ ｐｒｏｃｅｓｓｏｒ， ｗｒｉｔｅ ａｓｓｅｍｂｌｙ ｆｏｒ ｓｏｍｅ ｏｂｓｃｕｒｅ ｐｒｏｃｅｓｓｏｒ， ｏｒ ｕｓｅ ａ ＰＬＣ．

Ｒｕｓｔ ｉｓ ａ ｆａｓｔ ａｓ Ｃ， ｍｏｒｅ ｓｅｃｕｒｅ ａｎｄ ａｃｔｕａｌｌｙ ｆｕｎ ｔｏ ｐｒｏｇｒａｍ ｉｎ． Ｏｂｖｉｏｕｓｌｙ ｉｔ＇ｓ ａ ｇｏｏｄ ｒｅｐｌａｃｅｍｅｎｔ， ｉｔ＇ｓ ｊｕｓｔ ｎｏｔ ｔｒｕｅ ａｎｄ ｔｒｉｅｄ ｙｅｔ．

Ａ ｇｏｏｄ ｐｏｓｓｉｂｌｉｔｙ ｉｓ ａｌｓｏ Ｊａｖａ． Ｉｔ＇ｓ ｐｌｅｎｔｙ ｆａｓｔ， ｅａｓｙ ｔｏ ｐｒｏｇｒａｍ ｉｎ， ｒｕｎｓ ｅｖｅｒｙｗｈｅｒｅ， ａｎｄ ｔｈｅｒｅ＇ｓ ａ ｆｕｃｋｔｏｎ ｏｆ ｊｏｂｓ ｆｏｒ ｉｔ． Ｄｏｎ＇ｔ ｌｉｓｔｅｎ ｔｏ ｔｈｅ «ｈａｈａ ｌｅ ｐａｊｅｅｔ ｊａｖａ ｕｓｅｒ？？ ｌｅｔ ｍｅ ｗｒｉｔｅ ｆｉｚｚｂｕｚｚ ｉｎ ｃ ｔｏ ｓｈｏｗ ｕ ｈｏｗ ＳＭＡＲＴ ｉ ａｍ»， ｔｈｅｙ＇ｒｅ ｃｏｍｐｅｌｔｅｌｙ ｄｅｌｕｓｉｏｎａｌ ａｎｄ ｍｏｓｔ ｌｉｋｅｌｙ １２ ｙｅａｒｓ ｏｌｄ．

Attached: 800px-James_Joyce,_Ulysses,_1ed_2pr,_p240.jpg (800x1035, 178.39K)