The dog is dead, post nonfunctional code

printf

x = 0
x = 1

while (<>) {
&processIt($_);
}

myAnus.hax();

>>2
you naughty boy

proof = (\f x -> lhs f x) === (\f x -> rhs f x)

Hello please gib asylum

>>7
Our textboard is suffering from low population. I'm sure these immigrants will enrich our culture and society, ushering us to a new age of multiculturalism and tolerance.
Refugees welcome.

>>8
not in my anus!

Haskell programmers are goblins.

check(&my_dubs);

>>11
check x = x /10 == x%10

>>12
only works correctly for \(n < 100\)

>>13
The correct one is (x%10==(x/10)%10)

(7%10==(7/10)%10) 7 == 0
(77%10==(77/10)%10) 7 ==
(777%10==(777/10)%10) nononono

>>15 What?
(7%10==(7/10)%10) -> 7 == 0%10 -> 7!=0
(777%10==(777/10)%10) -> 7 == (77%10) -> 7 == 7

I don’t think C gets enough credit. Sure, C doesn’t love you. C isn’t about love–C is about thrills. C hangs around in the bad part of town. C knows all the gang signs. C has a motorcycle, and wears the leathers everywhere, and never wears a helmet, because that would mess up C’s punked-out hair. C likes to give cops the finger and grin and speed away. Mention that you’d like something, and C will pretend to ignore you; the next day, C will bring you one, no questions asked, and toss it to you with a you-know-you-want-me smirk that makes your heart race. Where did C get it? “It fell off a truck,” C says, putting away the boltcutters. You start to feel like C doesn’t know the meaning of “private” or “protected”: what C wants, C takes. This excites you. C knows how to get you anything but safety. C will give you anything but commitment

In the end, you’ll leave C, not because you want something better, but because you can’t handle the intensity. C says “I’m gonna live fast, die young, and leave a good-looking corpse,” but you know that C can never die, not so long as C is still the fastest thing on the road.

As long as we program over Von Neumann architectures CPUs, C will be king. C is basically a description language for a Von Neumann pipeline process, and almost all languages we use run atop the same architecture.

Every programmer should know C, because it's a simple and beautiful language that teaches a lot about how programs and computers actually work.

Few programmers should actually work in C, because there really is no need to.

Types are actually VERY simple in C. bool is a boolean. int is a natural number. double is a real one. char is a character and a string is an array of characters. If you put a * after them they are pointers. They don't need to care about their size or how they are implemented either.

When you look at a program beginners would write C is quite simple and beautiful. Easy to understand what's happening.

I think learning C first, let's you appreciate Rust a lot more and also helps a lot in understanding it. C is a prettg raw and dangerous language, but it is also close enough to the machine, while not being a system specific assembler. So it can teach you about memory layouts and about the dangers of manual memory management and data races.

While Rust probably could teach you that, I think it is more likely, that you get annoyed, why you should have to deal with a stupid borrow checker. But when you already know, what is dangerous, your probably glad to have it. Also I think that C is just closer to how CPUs operate, so it is good to get a basic feel of low level programming.

>>21
Rust is very unsafe. Most of the Rust standard libraries have multiple unpatched CVEs. If you want memory safety, just use Java.

Only idiots spend time on something already automated by computers (memory management).

I just read on ha***r news that ruby will have types. What is this bullshit? Edited on 21/04/2019 16:55.

I just read on ha***r news that ruby will have tupes. What is this bullshit?
I just read on ha***r news that ruby will have types. What is this bullshit?

>>23
*tubes

Haskell the dog was born in 1999. In 2012 he was killed by a vile poacher.

sage

>>22
Rust in general is more safe than C spaghetti code that Stdlib is written in, with all its arcane macro magic(GNU quality).
Here is an example:
https://github.com/lattera/glibc/blob/master/libio/libioP.h

>>27
there is medical life support equipment that depends on this code. can you say the same for Rust?

>>28
Is this a good? Is it a good thing that my life might depend on a code written 30 years by someone whose main qualification is not skill, but anger?

>>28,29
It was tested for these 30 years and patched accordingly. It doesn't mean there are no exploits. The stdlib/system headers are pretty much a free buffet for hackers to explore, with convoluted and unintuitive code paths. Microsoft does even worse shit that doesn't comply with standards or pretend they're standard, which is evident in how Wine struggles to replicate windows interfaces(And why switching to Linux cures gaming addiction).

https://news.ycombinator.com/item?id=19737663

>>31
omfg...

check my functional dubs

>>31

I led the team that created the JavaScript interpreter JWST is using, and I still occasionally work with them on it. 16 (or so) years ago I was blown away at the amount of research NASA did covering all of the control language options, and of course glad that they selected ours. The language itself wasn’t so important as having adequate performance, robustness, memory use, reproducibility and extreme QC.. the way I remember thinking about it was that when your system is running a million miles away, you can’t send an IT tech to press ctl-alt-del when something goes wrong. IMHO they made a well-researched choice that continues to hold up.

Please keep the niggerlicious outrage culture away from prague.

>>34
Tsk.

https://news.sherlock.stanford.edu/posts/when-setting-an-environment-variable-gives-you-a-40-x-speedup

>>36
Wow mate thanks i can finally view the contents on my folder, _grouped_.

https://www.gamasutra.com/view/feature/194772/dirty_game_development_tricks.php

>>38
that one about self-exploitation was great. I was toying around with vulnerabilities-as-backdoors, but never expected to see this concept used non-maliciously

https://www.reddit.com/r/ReverseEngineering/comments/4cavn1/snes_code_injection_flappy_bird_in_super_mario/