Post list of mistakes ITT

Post list of mistakes ITT
>x86
>unix
>C
>javascript

Other urls found in this thread:

wiki.sei.cmu.edu/confluence/display/c/SEI CERT C Coding Standard
man7.org/linux/man-pages/man3/strcpy.3.html
twitter.com/AnonBabble

(You)

http

Technology was a mistake

>x86
>UNIX
>C
>Mistakes

>likes UNIX
>likes x86
I can tell someone wasn't around for UNIX risc workstations.

/thread

At least JS wasn't planned as a mistake.

also: GNU
Linux
X11
cpp

Switching from analog to digital

Was js planned?

synchronous processors

>X11
>cpp
this
>gnu
>linux
replications of and extensions to an already flawed OS with even more legacy bullshit than windows

Windows

FTP
JavaScript
Adobe
Microsoft
Google

C
>strcpy
>buffer overflow
>segmentation fault
>strings are literally char arrays
x86
>spectre
>meltdown
>Intel Management engine
>AMD PSP
JS
>you already know
unix
>read the good,bad ugly about unix

idiots.

>plan9 never replaced unix in our timeline

posix locales, xml, terminfo and termcap layer, imap, emacs lisp, non-hygienic macros in erlang, many parts of C, extending highly standardized language that is only alive because that standardization makes it portable and predictable, X11, texinfo, prthon's stack implementation

gnome
systemd
advertising

Referer

>electricity

>Specter and meltdown being a REAL issue
Get the fuck OUT NIGGER

please, people have given x86 enough chances.
It should have been kept an 8 bit microchip for single user/ singletasking machines.

Yes they are big issues and even if they weren't they're pretty big fucking implications that there's deeper, more retarded shit that dwells inside x86

No one mentioned PHP yet. Classy Sup Forums

Java

Advertising
The internet of things
Wangblows
Crapple iCraps
Goolag
Scamazon
ISPs

>strcpy
It's fine.
>buffer overflow
Brainlet.
>segmentation fault
Brainlet.
>strings are literally char arrays
You're literally retarded.

>read the good,bad ugly about unix
>tfw you can't make up a good argument so you urge everyone to read a book instead

Kill yourself.

>Those flowers
New Game! is a nice manga.

x86 is mediocre, it's not that bad
the platform we use x86 mostly on, "IBM PC" is a real fucking joke, layers of layers of legacy

>this thread
delete this

>unix
Elaborate
It's one of the few things that has made most sense in the short history of computing

Sup Forums

>layers of layers of legacy
That's the only reason why its popular

>C strings
use strn* versions then

C++ is a mistake thats being corrected into something genuinely cool

I can defend, albeit with a pinch of autism, outside of javascript.

>strcpy is fine
jesus shut the fuck up this is how i know you're nothing more than a fizzbuzz aficionado
also
Saying bufferO and segfaults are okay and you need to cope with them is like saying putting landmines in your fucking house is okay and you need to cope with them.

>has only ever eaten dogshit
>whats wrong with dogshit??

wiki.sei.cmu.edu/confluence/display/c/SEI CERT C Coding Standard
follow it, use linters and clang's sanitizers and you won't have issues anymore

www

protocols: http and ftp
websites that centralize everything like reddit and facebook
desktop environments: mate, kde
os: windows 10 S, windows 8

>dude just avoid stepping on landmines and you won't have issues lmao
no thanks, i'd rather not use a shit language

posix shell and nearly every derivative
pthreads
fork+exec process creation model, especially with ^

x86 and http are the only valid complaints in this thread.

No, it was hacked together. In fairness to JS, once you have the program whitepapered out, it's one of the most straightforward languages to actually cobble together your program in because of how easy it is to pass around functions. Promises actually make it enjoyable to write code in.

computer networks

reCAPTCHA

fpbp

GNU
X11

I still use both though

>strings are literally char arrays
Kek

The "char, short, int, long, long long" naming was a mistake.

facebook, Instagram and twitter

>>x86
fuck all amount of registers
45 years of backwards compatibility
64-bit took forever and isn't even "real" 64-bit, but 48
FMA took forever
SIMD only got popular like 15 years ago
>>unix
le everything is a file
no concept of "drives" as they're part of your whole filesystem
bash is shit
scripts are required to do menial tasks
installed software is scattered around several directories across filesystem (good luck installing something manually)
trillion .conf files
"executing" a directory
9 bits permission (but not really)
no finer-grade permissions
no ACLs. usage of ACLs is total pita
shitty and toxic ""community""
bash is shit
>>C
no ability to use common cpu instructions without using some serious boilerplate
>>javascript

Not him, but agree 100%. You're retarded if you think C should have implicit checks for segmentation faults or overflows, C is a low level language, if you were to eliminate all undefined behavior and added checks to the standard, all software with exception of the ones written in assembly would become slower. Your OS would become much much slower.

>x86
>>spectre
>>meltdown
>>Intel Management engine
>>AMD PSP
How retarded can you be? Spectre isn't indigenous to x86, and ARM has trustzone which is the same level of untrustworthy blackbox.

I feel bad that I took this shitty bait.

>Being born

>No standardized WaitForVSync API call/Callback across all the operating systems
>Open GL ES
>Inkjet printers

Turing machines
Lambda calculus
Cellular automata

>C
>>strcpy
>>buffer overflow
>>segmentation fault
>>strings are literally char arrays
If a language would prevent you from doing stupid things, it would also prevent you from doing smart things.
>x86
>>spectre
>>meltdown
>>Intel Management engine
>>AMD PSP
None of these are inherent to x86, and the first two aren't unique to x86. The real reason x86 is bad is that it does alot to convince people that assembly programming is hard, kind of like Linux and Windows do for C and sockets do for networking.

>>plan9 never replaced unix in our timeline
It was never supposed to, so you can't say it was a failure. Its proper purpose was to be a sane computing environment for the people that made it, and they did use it as their daily computing environment, so it obviously succeeded at its proper goal.

It's not a book. It's slides of a talk by Rob Pike.

And yet its very creators moved on from it and were glad to do so.

>everything is a file
This is a good thing.

>mini-ITX
>noctua

Holy shit, you managed to be more retarded than OP!
strncpy and strncat are both:
1. dangerously misleading, and
2. inefficient.

The same concepts apply for strncat, but I'll explain strncpy because it's the easier example.
char a[] = "abc", b[4];
strncpy(b, a, strlen(a));
/* b is now: {'a', 'b', 'c', UNINITIALIZED} and thus possibly not NUL-terminated: dangerously misleading */
strncpy(b, "Z", strlen(a));
/* b is now: {'Z', 0, 0, UNINITIALIZED} and thus more than one NUL byte has been written: inefficient, especially for larger buffers */

>2018
>either lunix nor wangblows solved deadlock

ouch I fucked up user, I always mistake strn* for strl*, my bad I suck

All is forgiven. It happens.
Meanwhile on glibc, welcome to "we still don't have strlcpy".
man-pages even tells people straight up to use strlcpy via libbsd.
man7.org/linux/man-pages/man3/strcpy.3.html

Cumming inside my sister. We don't speak anymore..

owned

fpbp

You parents not aborting you while they had the chance.

Almost everything, because they could have been made better in hindsight. This includes impregnating your mother.

...

...

...

Proprietary software.

sauce on the image?

>Sup Forums

> C
You can use compiler flag to prevent buffer overflow and segmentation fault and write "safer" code, but the main reason you use C is because you don't want overhead so you don't use those flags.
> unix
Suggest something better?

delet this

bump

it stopped being shit when 7.0 was released