Do you guys know what javascript frameworks might be useful for?

If you think Javascript frameworks are an example of the Unix philosophy, you need to reevaluate your life.

His definition of the Unix philosophy is so fucking broad that he regularly cites Microsoft Windows and bloated web browsers as good examples of Unix. Most of his examples of Unix being shit are from ancient commercial implementations, gigantic webshit, or screeching about kernel sizes when most of that code is drivers.

I've never seen him say this, but why would you even want to use something following the UNIX weenie philosophy anyways?

JavaScript frameworks are a perfect example of the UNIX philosophy. Web browsers need millions of lines of code just to implement a language that sucks and still need more megabytes of "framework" code to be halfway usable.

My definition of the UNIX philosophy is whatever UNIX does, just like the definition of C was whatever the PDP-11 compiler did. Windows does not follow the UNIX philosophy, but it's written in C, so C brain damage infected Windows (literally, due to viruses, spyware, and ransomware spread by exploiting bugs in C code). UNIX weenies always bring up hypothetical bullshit they "could" do with 15,600 people if they were able to throw everything away and start over again or pretend that "good parts" that only apply to 0.1% of the OS are a "philosophy" of UNIX. On the other hand, people who like Multics, Lisp machines, Ada, PL/I, and so on, are always talking about specific things that actually exist. Lisp machine users talk about actual facts like how all the code can be modified and the condition system and object system. UNIX weenies say things like "Rule of Economy: Programmer time is expensive; conserve it in preference to machine time" which is another way of saying their code is slow even though they don't check any errors.

In this case, the problem is that JavaScript sucks, so it needs another couple million lines of code (a framework) to actually do something useful. Even Eric S. Raymond says this is "What Unix Gets Wrong."
catb.org/esr/writings/taoup/html/ch01s04.html
Browsers are bloated because a browser "should be" just an empty shell for bookmarks, tabs, and GUI features like fonts, images, buttons and textboxes that other software on your computer already does. It needs 50 million lines of code just to turn HTML, CSS, and JavaScript into something your computer can already do. Eric S. Raymond is agreeing that "If society ran the same way UNIX does, everyone who owned a car would be forced to refine their own gasoline from barrels of crude..." but he says it's a good thing. I agree with "mechanism, not policy" in libraries because that increases code reuse, but for applications like browsers, it just means everyone has to repeat the same code and reinvent wheels over and over again.

This is like another planet where people believe that bad is good and broken code is better than working code. Solving the wrong problem the right way just means a different group of users will appreciate it. Lisp was made for AI, but became used for GUIs, 3D graphics, and all kinds of other applications. Solving the right problem the wrong way is how you end up with UNIX, C, C++, JavaScript, asm.js, WebAssembly, Linux, UEFI, GRUB, sendmail, awk, bash, 50 million line web browsers, and so on.

I'm having this nightmare in which a chorus of unix weeniepod-people chants: "sendmail is what the internet communty accepts as standard" "sendmail is what the internet communty accepts as standard" "sendmail is what the internet communty accepts as standard"over and over again, as they shuffle relentlessly towardsme, clutching hideous kludges that they claim are "InternetStandards", that I must accept in order to be "compatable".In vain, I throw copies of the actual Internet protocoldocuments back at them in a futile attempt to demonstratethe difference between the Internet and Unix. Copies ofRFC821 and RFC822 are simply trampled under their feet asthey close in around me. As I lose consciousness, I thinksome of them have switched to chanting: "you are number six" "you are number six" "you are number six"

Existed*, briefly and miserably in PL/I's case someday I'd like to write a PL/I compiler for shits and giggles but don't expect anything to come from it. If Unixfags want something bad enough, they write it themselves. Sometimes the results are good, sometimes not. Unix Haters, on the other hand, sit around and twiddle their thumbs while moaning about the good old days and how no one writes software for them.
As someone interested in non-Unix OSdev, parrots like you are the worst. You've basically killed Zig Forums's Ada and Lisp discussions because no one wants to be associated with your boomer rants, usenet quotespam, and constant appeals to Windows/webshit/X11/shit everyone already hates when good Unix software already exists.
The Unix family is not incapable of producing good software and has some interesting ideas, even if some design quirks, language choices, and historical baggage like X11 make it more difficult than it should be.

Fuck off, faggot.

do you people still read the unix haters' textwalls? I pretty much just scroll past them at this point. Thankfully they're very easy to identify visually.

Because The truth sets you free.

They don't. Sometimes I write a block of text full of nothing in particular, sign it with a fake usenet quote for shits and giggles, and anons assume it's the Unix Haters fag through the formatting alone.

Attached: 1457293772860.png (1280x720, 707.72K)

...

nobody uses vanilla JS ever

That's a poor attempt at FUD. PL/I is still a main language for mainframes (along with Cobol), Multics was used until 2000, and IBM made PL/I for Windows and OS/2.

I brought those discussions back.

Maybe, but I haven't seen any. The good software is a ripoff or port from another OS. The interesting ideas came from Multics and other operating systems and were better in the original OSes. There were some OSes that improved things, but with UNIX, it's always worse, like they can't even understand what the other OS did and what they're trying to accomplish.

people.fas.harvard.edu/~lib113/reference/unix/unix2.html
The next time UNIX weenies mention simplicity, keep in mind that this is the kind of thing they mean. This explains the UNIX weenie's aversion to libraries. Even the shitty form of static linking using "ar" was a bolted on hack. The name of that file, by the way, was "a.out".

Pipes weren't an original UNIX idea either, they just took the existing IPC method of streams or channels and limited them to sequences of bytes, just like UNIX limited files to sequences of bytes.

A high quality garbage collector is a couple thousand lines of code, which is nowhere near the size of all this C and UNIX bullshit.

If a vendor decides to do something about the crassinadequacies of UNIX we should give them three cheers, notstart a flame war about how the DIRECTORY command *must*forever and ever be called ls because that is what the greattin pot Gods who wrote UNIX thought was a nice, clear namefor it.The most threatening thing I see in computing today is the"we have found the answer, all heretics will perish"attitude. I have an awful lot of experience in computing, Ihave used six or seven operating systems and I have evenwritten one. UNIX in my view is an abomination, it hasserious difficulties, these could have been fixed quiteeasily, but I now realize nobody ever will.At the moment I use a VMS box, I do so because I find that Ido not spend my time having to think in the "UNIX" mentalitythat centers around kludges. I do not have to tolerate ahelp system that begins its insults of the user by beinginvoked with "man".

you people need to stop engage/encouraging him. Don't feed the trolls.

Not remotely. For a couple years after the 2014 GG migration we had a lot of Lisp and Ada discussion, discussion which died after you showed up and one of the bigger /g/ migrations happened. Fucking no one discusses Ada here anymore outside brief namedrops in Rust threads and Lisp is relegated to a single thread of salty fags who can't even write a text editor.
...Which is still the fastest way to read files on most non-solid state storage mediums. The exceptions I've heard people bring up only apply to fucking massive files where jumping ahead is faster than reading sequentially, in which case you're doing something horribly wrong. Just because pipes aren't that great doesn't mean we should cripple overall file reading performance to satisfy someone's anti-Unix salt.

for putting in ur ass

Times of old, am I right?

Is this what mental illness looks like?

Their good if your a low effort person who wants things to just werk without using your brain.