Hacker News Reader

>Can there really be no practical way to apply thousands of cores to boosting the programmer's productivity? What are we missing?

Surely that's the whole point of high-level languages?

View on HN

That's using the end user's cores. Using something at programming-time could be something like static analysis. Then there are entire tests the programmer doesn't have to write and bugs that never get pushed.

I've seen people write Java or C# like I would write plain C. Those first two are insanely high level with large standard libraries.

I disagre with "Those first two are insanely high level" but totally agree with the "with large standard libraries." part.

Java: "I've got a huge standard library!"

C: "See, you're doing it wrong! I've got a really lean standard library!"

Java: "Ah, so you just focus on the basics. You have a dictionary structure? That's pretty basic."

C: "...no."

BSDs have <sys/queue.h> and <sys/tree.h>; the former is standard on Linux as well.

To my eyes just having generics and hiding away pointers and vtables make them very high level, but I think my argument was more about what is coming with the language (aka their standard libraries) and I've definitely seen people ignore the available libraries, even in python.

Reply on news.ycombinator.com