Real programmers understand machines

Garbage Collected programming languages collect garbage programmers, who are ignorant about concepts like memory management and would only write garbage code.

High level programming languages are made by real programmers, for real programmers, who already understand these concepts. Attraction of shitty programmers to these languages is a side effect.

https://groups.google.com/d/msg/sci.logic/hZ4uvIFf_QQ/_cxg_qFXCAAJ

Programming in logic without logic programming

http://www.amazon.com/dp/B00FKJY1WY

the anti GC joke is retarded and has gone too far

its not funny and makes you look like an idiot

Manual Memory Management programming languages allocate garbage programmers, who are ignorant about concepts like garbage collection and would only write garbage code.

High level programming languages are made by real programmers, for real programmers, who know better than to waste time plugging memory leaks. Attraction of shitty programmers to these languages is a side effect.

>>5
But I have a right to change any bit in the memory of my computer.

>>6
Sure, if you're fucking around with drivers, or mashing the CPU state to swap user-space threads and such.

But data, algorithms, and procedures don't need to be identified by their memory location, but by their semantics of processing. Therefore, dealing with such things at the "bit of memory" level is not the appropriate level of abstraction.

It certainly is when you're creating the garbage collector or compiler, though, because that is where the declarations of how your program manifests on the hardware exist.

>>6
Except CPU microcode and firmware protected from modification.

>>5
Exactly! The programming languages that require understanding of programming, make it easy to spot bad programmers, because writing good software requires knowledge, not copy-pasting code snippets from the web.

While the concept of GC is wonderful, given enough resources, it makes it harder to find an outstanding programmer writing good code, because he knows what he's doing, instead of running into a code monkey, that repeats memorized code snippets and creates puzzle that works, but nothing more.

>>8
CPU microcode patching is not that hard. Both AMD and Intel provide microcode patches for their CPUs.

Modification of firmware, while not directly from under the OS, is doable. Sometimes it might require some hardware tinkering.

>>10
Microcode that is encrypted and processed by CPU DRM firmware.
http://scripting.com/98/04/stories/openSourcePurity.html

>>9
Real Programmers™ understand machines. "Machines" include compilers, GCs, runtimes, VMs, standard libraries, etc.

Real pogrommers program with nothing but front panel switches and blinking lights.

>>13
Multicolor LED keyboard+vim.

Get with the pogrom, Sally