Why are there high level languages?

Why the hell would anyone use Python or Ruby over C. The software should be nice to use. It's not nice when the program is slow as fuck.

Their dynamic nature makes debugging software increasingly hard. Basically developing with these higher level languages takes more time than with C.

Every program should be written in C. In most cases, it would be good to also optimize tight loops with Assembly. This way programs would be fast and fun to use.

Languages such as C# and Java have no point at all. They are essentially crippled versions of C. Limited pointers and limited memory management. The virtual machine takes forever to JIT-optimize the code, thus harming the user experience. Not to mention GC, which slows everything down, providing nothing useful in return. GC is shit.

Then there are these C++-retards. Sure, you can in theory make as fast C++-code as C-code, but is it really worth it? Every C++ program in practice is slower, harder to debug, and harder to develop.

Functional languages, such as Haskell are no answer to problem. They abstract the hardware to hell and are very slow in practice.

So tell me: Why is C and Assembly not used for every program today?

>>29

That could actually be a bad thing. Unrootable/unjailbreakable devices with DRM, only the corporate brainwashed drones would love that shit.

you're answering the wrong question. if you need to look for exploits and hack a device you already own to have full access to it, the problem is with the device itself. the answer is to use devices that are open by design and avoid closed systems as much as possible

That's the point. C makes it a lot harder to add bloat. You can write one line in an HLL that'll take a few thousand to implement in a lower level language. That tends to make you reconsider whether you should do anything and cause you to come up with a simpler solution. It's possible to write bloated code in C or even Asm, but you have to try really, really hard to.

from the perspective of an individual programmer - yes. from the perspective of a corporation - no. if higher ups decide that adding a fuckton of bloat will guarantee more sales, the bloat will be added even if you have to change opcodes with hex editor.

meanwhile, an intelligent individual programmer can write a reasonably efficient and non-bloated tool in a HLL without having to worry which of the similarly named functions (strcpy, strncpy, strncpy_s, strncpy_c, memcpy or whatever else) to use so that the string is still treated like string and does not cause buffer overflows.

BTW the whole string copying bullshit is the prime example of problems in C: it uses the fucktarded zero-terminated strings (instead of Pascal-style length-prefixed strings) because the difference in two or three bytes in memory was a big fucking deal back when the language was created in the fucking stone age. it then adds a safer version of an old function so your computer doesn't explode and when that function still makes your computer explode, they add another one. meanwhile, I still see programmers in a major multinational corporation use fucking gets().

everyday programming in C is like driving screws with a hammer