C is a horrible language. It's made more horrible by the fact that a lot
of substandard programmers use it, to the point where it's much much
easier to generate total and utter crap with it. Quite frankly, even if
the choice of asm were to do *nothing* but keep the C programmers out,
that in itself would be a huge reason to use asm.
In other words: the choice of asm is the only sane choice. I know Miles
Bader jokingly said "to piss you off", but it's actually true. I've come
to the conclusion that any programmer that would prefer the project to be
in C over asm is likely a programmer that I really *would* prefer to piss
off, so that he doesn't come and screw up any project I'm involved with.
C leads to really really bad design choices. You invariably start using
the "nice" library features of the language like stdlib and stdio and other
total and utter crap, that may "help" you program, but causes:
- infinite amounts of pain when they don't work (and anybody who tells me
that stdlib and especially stdio are stable and portable is just so full
of BS that it's not even funny)
- inefficient abstracted programming models where two years down the road
you notice that some abstraction wasn't very efficient, but now all
your code depends on all the nice typedef models around it, and you
cannot fix it without rewriting your app.
In other words, the only way to do good, efficient, and system-level and
portable C ends up to limit yourself to all the things that are
basically available in asm. And limiting your project to asm means that people
don't screw that up, and also means that you get a lot of programmers that
do actually understand low-level issues and don't screw things up with any
idiotic "portable assembler" crap.
Whatever, dude. Why don't you crawl back to your mommy - shes the only one that ever understood you anyway.
>>55228097
Programming in Assembly sucks ass, and it's not like you can do better than a compiler unless you're a wizard
>>55228097
>It's made more horrible by the fact that a lot
>of substandard programmers use it, to the point where it's much much
>easier to generate total and utter crap with it.
Non sequitur in the second sentence, well done OP.
>cfags will defend this
>$(date +%Y)
>not writing everything in Rust
>>55228240
You don't know what a non-sequitor is, you should probably stop using that word because it makes you look like an idiot when you misuse it.
>>55228289
>non-sequitor
Indeed I've never heard of that.
>>55228289
You look like an idiot trying to correct people on 4chan
>>55228097
>all your code depends on all the nice typedef models around it, and you cannot fix it without rewriting your app.
Just how retarded are you?
>>55228357
Still is a non sequitur in OPs post no matter what u say.
>substandard programmers use it
>therefore it's easier to generate crap with it
This does not follow.
>>55228389
And you're committing the fallacy fallacy.
Just because a conclusion is arrived at via a logical fallacy does not mean the conclusion is false.
>>55228263
As much as I love C, I think those are really good points... Sadly.
>>55228404
>hurr durr the argument is correct because the conclusion is correct
I don't give a shit what OP thinks of C, just calling him out on his inability to form a coherent argument.
no hate, just use Go
>>55228452
Go is pretty cool. Clean and fast language, with simple rules (visibility based on case, etc). Will it replace C? It was made for server software after all
>>55228522
No, but Rust will
IIRC Go isn't a feasible choice for some things due to garbage collection
>>55228357
Has nothing to do with the typo. Arguing on 4chan is inherently pointless so you look stupid for doing it.
Peace famalam
>>55228263
I'm not the biggest fan of C but that is one of the stupidest posts ive ever read.
>I know, ill just write drivers in python or java
It's not that writing things in C gives a performance gain, its that SOME THINGS SIMPLY MUST BE WRITTEN IN C
you fucking moron, neck yourself
>>55228389
That's not a non-sequitur at all. Learn the meaning of words
>substandard programmers use C -> lots of garbage libraries are written in C -> it's easier to generate shitty code based on those shitty libraries; it is easier to write garbage because the entire C ecosystem is filled with garbage
Isn't C just shittier version of PL/I because "hurr it's too good for my shitty computer"?
>>55228753
>SOME THINGS SIMPLY MUST BE WRITTEN IN C
Why?
>>55228753
>C, Java and Python are the only languages that exist!
>i am so mad i am going to tell someone to neck themselves
code in rust you stupid triggered faggot
>>55228890
how would you write a driver or a kernel in anything but C or maybe C++ (the C++ you would be using for these tasks would be as dangerous as C anyway)
>>55228910
People that think the only language to program low level is C are some stupid. On the other hand, Rust is probably cancer.
>>55228913
LISP.
https://en.wikipedia.org/wiki/Symbolics
>>55228913
samefag from
>>55229003
You could theoretically write an operating system/kernel and drivers in any language that can do some low level operations.
>>55229003
tagged registers don't exist anymore grandpa
fucking autists
http://article.gmane.org/gmane.comp.version-control.git/57918
>>55229035
I need more Linus rants
Love to see more done with assembly. Understandable why people don't though.
>>55228939
How is Rust probably cancer?
