3 ms·
>and we would have massive amounts of reusable code Haskell even has problems coming up with a single string / text interface. It's not some magic bullet for c
by coldtea 5y ago
>and we would have massive amounts of reusable code
Haskell even has problems coming up with a single string / text interface. It's not some magic bullet for code reuse, any more "everybody would write Java and we would have had massive amounts of reusable jar libs".
- amelius 5y agoBut at least we'd have referential transparency.
- ParetoOptimal 5y ago> Haskell even has problems coming up with a single string / text interface. That's orthogonal to the claim that if everyone used Haskell we'd have better code reuse. > It's not some magic bullet for code reuse Not a magic bullet, but makes code reuse much easier than any other lanugage. That can be attributed to a focus on sound abstractions, referential transparency, and laziness[0] mean that code is much easier to reuse. 0: Yes, laziness helps composition and code reuse!
- native_samples 5y agoWell, in fairness, the industry has got quite far with "everyone writes JARs". There are a heck of a lot of them out there. And now with Truffle you can mix JARs, Python packages, Ruby packages, JS packages ..