Re:Three Months of Go, from a Haskeller’s perspective (2016)
by angry_octet on Sunday March 19, 2017 @10:54PM
(#13911360)
I don't know about you, but everything I work on is going to be something that someone will have to maintain, or will be actively developed by multiple people with different categories of expertise. Also, I usually want to build on other people's work (i.e. libraries).
So while I'd love to write big chunks of Haskell, if its just me doing it, that code will be nuked and rewritten unless I also undertake a project of education. So accessibility is key. Go/python/js seem to win in that regard, and likewise in access to libraries.
So unless as an organisation there is motivation to step up skilling, e.g. because there is a lot of money at stake if something breaks (e.g. trading software), or because there is a community of practice (compilers) its hard to see Haskell gaining much ground.
Likewise all those other languages has their niche, and it is hard to seem them displacing each other.
Re:Three Months of Go, from a Haskeller’s perspective (2016)
by rs86 on Sunday March 19, 2017 @11:59PM
(#13911564)
100 hours is really optimistic for haskell
Re:Three Months of Go, from a Haskeller’s perspective (2016)
by doall on Monday March 20, 2017 @01:54AM
(#13912053)
Just a typo, but you mean Clojure? :)
Re:Three Months of Go, from a Haskeller’s perspective (2016)
by sheepmullet on Sunday March 19, 2017 @06:34PM
(#13910090)
I completely agree.
While you might think it's worth spending 100+ hours learning Haskell, I don't (at the moment) have any reason to Haskell as a better time investment than anything else on that list.. why should I give it more than 10 hours?