3 ms·
> What are we getting very wrong about programming languages? Perhaps it's the fact that languages have always had to accommodate the hardware, rather than the
by Razengan 10y ago
> What are we getting very wrong about programming languages?
Perhaps it's the fact that languages have always had to accommodate the hardware, rather than the other way around.
Why don't we have CPUs and memory controllers with built-in support for type safety and garbage collection etc. on the silicon yet?
- pmontra 10y agoI guess it has to do with this quote from Coders ar Work, from the interview to Fran Allen > Allen: By 1960, we had a long list of amazing languages: Lisp, APL, Fortran, COBOL, Algol 60. These are higher-level than C. We have seriously regressed, since C developed. C has destroyed our ability to advance the state of the art in automatic optimization, automatic parallelization, automatic mapping of a high-level language to the machine. This is one of the reasons compilers are . . . basically not taught much anymore in the colleges and universities. > Seibel: Surely there are still courses on building a compiler? > Allen: Not in lots of schools. It's shocking. there are still conferences going on, and people doing good algorithms, good work, but the payoff for that is, in my opinion, quite minimal. Because languages like C totally overspecify the solution of problems. Those kinds of languages are what is destroying computer science as a study. > Seibel: But most newer languages these days are higher-level than C. Things like Java and C# and Python and Ruby. > Allen: But they still overspecify. My guess is that it is left to the programmer because that was the way C did (no type safety and malloc) and the CPUs were developed to work with C. We're still stuck with that.
- dnautics 10y agoYou don't want to do that. That level of complexity will consume power by requiring more transistors... For something that can be done once, on compile time (instead of each time code is run). Already we have things like microcode translation and out of order execution, which can be thought of as "hardware JITting"... And x86 is running against a power/performance wall. Probably a better solution will be to backend microcode compatibility on our compilers, and then "run once to generate optimized".