/g/ shits on programming languages

>python

Im not learning the language of the devil

>>59264298
>Rust
>who

>>59264298
rust

>>59264298
C = CANCER

>>59264684
t. Java """"programmer""""

itt: a bunch of "jokes" about language names and stereotypes because no one on this dead garbage board actually uses programming languages

>>59264704
t. supreme turbo (((expert))) C kernel hacker master

>>59264729
>his languages needs a fucking VM to execute
LOL

>>59264745
Rust needs no VM thank you very much

C is Communism

C is for Cucks

>>59264757
C is Cancer

File: 1488248151444.jpg (233KB, 503x662px) Image search: [Google]

233KB, 503x662px

>>59264757
>>59264764
>>59264754

>Python
Dynamic typing
>Lisp (CLISP, Scheme, Clojure, ...)
Dynamic typing
>Ruby
Dynamic typing
>Java
Type reflection - might as well be dynamically typed
>Lua
Dynamic typing and shitty primitive data structures
>Perl
Dynamic typing
>Javascript
Dynamic typing
>C++
Unreadable error messages, language standard that grows faster than you can understand it
>Erlang
Dynamic types
>OCaml
Ugly syntax
>Haskell
No dependent types

how is this different from /dpt/

>>59264778
It is distilled /dpt/. This thread throws off all pretenses of meaning.

C
No concept of security
Produces vulnerable binaries
Shit concurrency
Fuck ton of undefined behaviors

>>59264785
>no concept of security
PEBCAK
>produces vulnerable binaries
PEBCAK
>shit concurrency
not an argument
>undefined behaviors
PEBCAK

>>59264805
>PEBCAK
Nice try NSA

>>59264805
The 0 day exploits don't care who's fault it is.

>>59264805
Typical NSA/C shill damage control anthem

>>59264837
>>59264840
C is Turing complete, any code errors are the fault of the corresponding programmer

>>59264855
Guess we should all use Brainfuck now. Or are you too dumb and need a language like C to hold your hands and babby you?

>>59264855
>C is Turing complete
ok
>any code errors are the fault of the corresponding programmer
Nice one. Come back when C gets proper dangling pointer prevention, data race prevention, smart pointers and default immutability

C apologists are NSA shills plain and simple. Rust makes it harder to produce vulnerable programs as it actually implements safety precautions like Bounds checking, dangling pointer prevention, data race prevention, lifetimes etc. This is against the interest of the NSA and so they are shilling C so that people continue to produce exploit prone, unsafe and vulnerable programs.

Ignore the NSA/C shills. Programming in C should be banned and outlawed.
Say no to security exploits, say no to the NSA. Your data and your privacy is worth preserving.

>>59264855
Sure, but it's a language that uniquely sets you up to make disastrous coding errors. And it doesn't matter whose fault it is once the fucked up programs are widely distributed and people are getting their shit stolen because of a stupid exploit because the original idiot couldn't manage the memory correctly.

>>59264862
>>59264867
Also this.

>>59264862
>C
>holding hands
It doesn't hold hands at all, which is why Pajeets get buttblasted when a buffer overflow is shoved up their ass

>>59264883
Why aren't you writing x86 assembly? Are you a babby who needs a C compiler to hold your hands?

>>59264883
Sorry __xXL0rdGhostCHaxx05Xx_, everyone makes silly bugs unlike your super sophisticated academic fizzbuzzes

File: 1488284269319.png (461KB, 1220x3705px) Image search: [Google]

461KB, 1220x3705px

C.ucks BTFO

>>59264867
lmao, it's almost like you have no idea what the purpose of C is and why that's relevant as to why it doesn't have those """features""" - wait no, it's not almost like that it's exactly the case

>>59264901
>he can't collect his own garbage
>he can't check his own bounds
>he needs objects and other cock cage abstractions
t. code toddler

>>59264912
>what the purpose of C is
was*

C was built around 80's model of computing.
It assumes you still use 800MHz single core processor.
It assumes you have 64MiB memory.
It assumes you are producing binaries that needs to be ported with a floppy disk.
C holds back technology.
C is Cancer that does not address the fact that hardwares have evolved so much.

>>59264924
le sophisticated turbo expert (((C))) fuzzbuzzer doesn't need bound checker for his ultra sophisticated 1M LoC hello world program, check it out

>I have to proofread my C code
looks like i'm a #JavaMissile now

>>59264901
I got a question


How will C toddlers ever recover

>>59264924
>he can't figure out his own jump offsets
>he can't pop his own values off the stack
t. code toddler

>>59264929
Don't forget : 0 (ZERO) security

>>59264867
>data race prevention
Rust doesn't even claim to prevent this.

C is for hipsters

>>59264963
>C(ancer)
Give me 5 reasons why should I be using C instead of machine languages and VHDL or AHDL

>>59264970
1. You don't give a shit about the security of your programs
2. You are a hipster retro faggot that pretends to like old and obsolete technologies
3. You are a beginner programmer, too retarded for C++
4. You have been living under a rock
5. You don't like C, you only like to promote C as NSA wants you to do

>>59264963
>he posted this from an OS most likely written with C and x86 assembly
really makes you think

>>59264980
My browser uses JS and Python too. I never see a C toddler address that

C.ucks getting BTFO
B T F O
T
F
O

>>59264979
KEK

>>59264951
They won't. C is finished and bankrupt.

>>59264979
>2. You are a hipster retro faggot that pretends to like old and obsolete technologies
Not an argument
>3. You are a beginner programmer, too retarded for C++
Not an argument
>4. You have been living under a rock
Not an argument
>5. You don't like C, you only like to promote C as NSA wants you to do
Not an argument

>>59264980
>he posted this from a computer most likely built with transistors
Really makes you think.

>>59264986
>blames C for security vulnerabilities
>uses Javascript, second to none other than Flash in terms of security vulnerability on the internet

It's over lads.
Rust won.
C.ucks on suicide watch

>>59264997
>Not an argument
kek cry some more C pajeet

>>59264929
>MiB
Wait, you are one of faggots, who beebees instead of normal prefixes?
No wonder you're such a shit.

>>59265004
C is the mother of all security vulnerabilities

Why do C tards need a compiler to babby them? Are they simply too dumb to write assembly?

File: 1479106914008.png (289KB, 1280x905px) Image search: [Google]

289KB, 1280x905px

>>59265012
Permanent reminder

>>59265005
>Rust won
Says who?

>>59265015
C programmers are novice

>All pajeets people shiting on C

>>59265026
Dennis Richie and ken thompson

Use Go

Now seriously, why does /g/ hate Java so much ?
I never managed to get a rational explication out of this if there's one.

>>59265023
Beebee prefixes were invented by HDD manufacturers who didn't want to give full binary megabytes.
Any apologist of bee prefixes is a jew, who likes to fool goyims.

File: 1488243967666.jpg (27KB, 300x492px) Image search: [Google]

27KB, 300x492px

>>59265031
13 rupees have been deposited to your NSA C apologist campaign, pajeet

File: 1487822049152.png (231KB, 342x342px) Image search: [Google]

231KB, 342x342px

C tards are rekt HARD ITT

>>59265031
>Day 1 of Intro to C
>Pajeet opens up Eclipse and writes a Hello World program

fatal error

JUST

It's decided:

You want a program full of possible security exploit: C(ancer)

You want a robust and rock solid program Rust.

I use F# exclsuively, debate me.

>>59265064
>typical C experience
While Chads are getting work done and fucking your non existent gfs

>>59265071
>MS cuck
More pathetic than C(ucks)

>>59265067
I think the R in Rust stands for Robust

>he doesn't program in his processor's machine language
what the fuck

>>59265085
What does C stand for?

>>59265089
Communism

>>59264901
How old is this?

Java has had string switches since java 7.

>>59265089
Cancer

>>59265097
Last time I used Java it was java6 back in 2012-13

>>59265089
Code

>>59265089
C.rippled programs

>>59265112
Do you dream in codes?

>>59265085
more like Retard

>>59264979
saved

File: 1488576749381.jpg (187KB, 1426x650px) Image search: [Google]

187KB, 1426x650px

C is trash, use D

>>59265033
Dennis Richie is dead you piece of shit.

File: Screenshot from 2017-03-06 20-45-21.png (97KB, 1934x1069px) Image search: [Google]

97KB, 1934x1069px

>>59265189
see >>59264770


Picture related: typical (((C))) experience

>>59265207
>using C(rippled)
What did you expect? Getting things done?

>>59265071
null

>>59265207
Only if you're mentally handicapped and know nothing about C. I find it bizarre and dangerous your piece of shit meme language permits altering the same piece of memory from different places at the same time. Any sane programming would avoid such a practice.

int i = 3;
printf('%d %d %d GO!!!\n", i, i -1, i-2);
i -= 2;

>>59265273
That was an amazing demonstration of damage control. C#, Java, D and thousand other languages do it without producing heartbleed

>>59265207
OH BOI NEVER TOUCHING THAT CANCER EVER AGAIN

>>59265289
And yet, none of those languages offer the performance and versatility of C, and will never come close to replacing C.

File: 1486275222031.png (139KB, 228x260px) Image search: [Google]

139KB, 228x260px

>>59265207
Tell me this is photoshopped

>>59265289
>buffer over-read
AKA pajeet's first time playing with numbers

>>59265321
>>59265273
So you are saying C would be bad if it produced the same result as shown on top?

>>59265326
see>>59265273

File: 1487974409142.jpg (79KB, 640x640px) Image search: [Google]

79KB, 640x640px

>>59265359
Just tell me it would be bad if C allowed you to do so, anon

>>59265207
Proves C people are mentally ill

>>59265326
Yes, because it promotes poor form by modifying pieces of memory at the same time. Obviously, a computer can't modify the same piece of memory at the same time, which is why different compilers and systems produce different output and the behavior is undefined, but if you were to model the system as a logical circuit, it would produce a massive error because you're trying to drive the same piece of memory at the same time from different places.

No language that encourages such poor practice could ever be a "systems" programming language like C is.

>>59265396
>No language that encourages such poor practice could ever be a "systems" programming language like C is.
Clang produces the same result as shown on top


Checkmate, C tard

>>59265412
It's still undefined, and Clang producing what you wanted doesn't change the fact you shouldn't program like that.

Prolog:
>No.

>>59264855
Magic: The Gathering is turing complete, any code errors are the fault of the corresponding programmer.

>>59265023
Applel and ISO on the left side kind of evens it out...