2 ms·
> "What we need, Karpinski realized after struggling to build his network simulation tool, is a single language that does everything well." and later: > "Beza
by pmr_ 13y ago
> "What we need, Karpinski realized after struggling to build his network simulation tool, is a single language that does everything well."
and later:
> "Bezanson says it’s not exactly ideal for building desktop applications or operating systems, and though you can use it for web programming, it’s better suited to technical computing."
So, Julia is not what we need? ;)
Besides this contradiction I'm not entirely convinced that we need one language to rule them all. I'm not even sure I want multi-paradigm languages (C++ anyone?).
Aren't the problems explained in the introduction of this article not caused by the tools instead of the programming languages? I don't see how using multiple languages complicates patching (unless the article is talking about monkey patching which I doubt), but I would understand how going through 4 different debuggers could drive you crazy.
Disclaimer: I'm not familiar with Julia and I will not judge it based on a Wired article.
- john_b 13y ago> What we need, Karpinski realized after struggling to build his network simulation tool, is a single language that does everything well. That wasn't quoted in the article, so I'm assuming it was the author's words, not Karpinski's. The Julia devs seem to be more interested in solving the (prototype) -> (translate to low level language) -> (optimize for production) inefficiency rather than making one language to solve every conceivable problem.