HOW THE FUCK DID PEOPLE LET THINGS GET THIS BAD.
how can we actually make things better?
HOW THE FUCK DID PEOPLE LET THINGS GET THIS BAD
John Hall
Other urls found in this thread:
youtube.com
en.wikipedia.org
themoviedb.org
en.wikipedia.org
github.com
en.wikipedia.org
stackoverflow.com
en.wikipedia.org
news.ycombinator.com
liberapay.com
twitter.com
Ryan Martinez
- Abandon Loonix/iOS/OSX/Windows/BSD/Android.
- Popularize Smalltalk, Oberon, Lisp machines, and Plan 9.
- Extirpate the Web, keep Gopher.
- Stop DRM and the IOTS.
- Destroy the x86/ARM architectures, let POWER/PPC/MIPS/(RISC in general) survive.
- Have a firing squad for executing programmers who use shitty kiddie languages.
- Jail the pajeets that want to make "MMO apps using blockchain technology" (sic).
That would just be the start.
Juan Murphy
1. Free Software
Use GNU/Linux or another Freedom and privacy-respecting operating system and use libre programs, as much as possible.
Encourage others to do the same, at least partially.
2. Free Hardware
Buy, support, or at the very least shill libre hardware, preferably non-x86 hardware.
I mean, purism is doing great things to mitigate, but the (((courtesy letter))) and their subsequent removal of their FSP repo and pointing instead to Intel's one shows that we really gotta get off this train. There is no hope for it.
Explain to brainlet friends and acquaintances the dangers of Amazon Alexa and Google Home (((smart home))) stuff. Bryan Lunduke recently showed just how insidious it's getting, and nobody seems to be scared yet...
3. Kittens
Always love kitten bois forever OwO
Luke Gray
Change social relations to the means of production.
Windows/mac can't be installed if we own all the factories instead of the oems that install Windows.
Mason Lee
Deleting this board would be a good start
Brandon Johnson
You mean (((Bryan Lunduke)))
youtube.com
Joseph Anderson
- Have kids
- Raise them to be Hitler
- Cross your fingers
Nathaniel Ross
>but the (((courtesy letter))) and their subsequent removal of their FSP repo and pointing instead to Intel's
nuking isreal would be a great start to solving this problem
Charles Fisher
Why do you want to beat your kids user?
Logan Hughes
If you really want to make things better, abandon everything written in C, which includes all of those.
These should be popularized, and so should Multics, VMS, and all the other OSes that have solved problems the shills don't want you to think are problems.
Plan 9 sucks even more than 1991 UNIX. 1990s UNIX-Haters rants that people here thought were made up are still valid in Plan 9 in 2018. If you want something resembling UNIX if it was redone 50 years later by more intelligent people, take a look at Multics.
RISC sucks because it's made specifically for C and UNIX. x86 is a badly designed CISC that's full of obsolete bullshit, but it still has advantages over RISC.
Date: Tue, 19 Nov 91 08:27:49 EST From: DH Yesterday Rob Pike from Bell Labs gave a talk on the latest and greatest successor to unix, called Plan 9. Basically he described ITS's mechanism for using file channels to control resources as if it were the greatest new idea since the wheel.Amazing, wasn't it? They've even reinvented the JOB device.In another couple of years I expect they will discover theneed for PCLSRing (there were already hints of this in histalk yesterday).I suppose we could try explaining this to them now, butthey'll only look at us cross-eyed and sputter somethingabout how complex and inelegant that would be. And thenwe'd really lose it when they come back and tell us how theyinvented this really simple and elegant new thing...
Multics was written in a high-level language first. ITS ranon the PDP-6 and PDP-10.Sure they came up with an implementation. You just make amachine that looks just like a PDP-11 and you can port unixto it. No problem!The latest idea is to build machines (RISC machines withregister windows) which are designed specifically for Cprograms and unix (just check out the original Berkeley RISCpapers if you don't believe me: it was a specific designgoal). Now, people tell me that the advantage of a Sun overa Lisp machine is that it's a general-purpose machine ("Ofcourse it's general purpose." they say. "Why it even runsunix.").Hmm, well this example shows that at least the weenix uniesknow how to USE recursion!
I'm just getting around to responding to this, with an historical note which I cannot resist. Paul's paper is a good, thorough, and competently done analysis, but the conclusion takes me back about 14 years. Are we always destined to reinvent the same stuff every N years?There is a well known effect in the computer architecturecommunity, which in summary states that all majorarchitectural mistakes must be and have been made at leastthree times: once in the design of mainframes, once in thedesign of minicomputers, and once in the design ofmicrocomputers. Perhaps a similar rule applies to operatingsystems.The same mistakes are made once in mainframe OS's, twice inmicrocomputer OS's, and N times in Unix (tm) operatingsystems. What seems surprising and different is that theydon't get fixed in Unix. Mostly people don't even realizethey ARE mistakes.