7 karma · joined February 12, 2016
To expand on this, a simple cryptographic hash stored in a safe can be used to do something like proving a digital item hasn't been tampered with. The blockchain seems to me to only solve for the problem where the "system" is so corrupt that you can't trust anyone. I just don't think the "system" is that corrupt. So, I doubt blockchain has any real-world merit. Time will tell.
This matters because management is often paid in options. So, managements have an incentive to allocate capital to share buybacks to boost their pay packages instead of reinvesting money in the business. If share buybacks were illegal and the only two options were dividends and keeping the capital in the business, managements might behave very differently.
How is this any different than the wild west days of stock sales prior to the regulations that came about during the great depression in the US?
C is optimal because it sits at a nice fulcrum point between assembly language (the code the CPU actually executes) and human-readable structured programming.
Java hides important things from the programmer, most notably how memory allocation works, the necessity of managing memory and freeing it at the right time. Java introduces higher-level abstractions such as classes which make programming more complex for a starting programmer without much benefit. Beginning programmers need to learn the simple process of conceptualizing and writing procedural code and adopting basic formalisms such as decomposing complex codepaths into functions for clarity and conciseness.
JavaScript compounds these issues. It makes it essentially impossible to see the actual code running on the CPU to execute a given set of instructions. It introduces functional programming concepts which, while important, are really better used once a programmer has developed more intuition about how CPUs actually process instructions. Its syntax is so fluid that it's difficult for a beginning programmer to understand what is "right" and "wrong" in many cases, because so many different idioms "just work."
I very commonly encounter programmers who have never used C and therefore have next-to-zero intuition about memory allocation and how CPUs actually process instructions. I'm not suggesting engineers should all learn x86 ASM coding, but I do think C provides the best basis for becoming a strong engineer later in life. As a general rule, the strongest engineers I know all have a significant background in C programming somewhere in their education or professional resume.