8 ms·
Is it because they might be overqualified, so any company that happens to do haskell (which I can imagine aren't many) are intimidated? I mean how many people
by Cthulhu_ 5y ago
Is it because they might be overqualified, so any company that happens to do haskell (which I can imagine aren't many) are intimidated?
I mean how many people here, currently working in language X, would want to hire someone that is better than they are? I mean rationally it makes sense - bette for the company, learning opportunities, etc, but emotionally it would seriously piss me off if someone came swooping in and basically made me obsolete and look stupid. (I'm not saying the author of the article would do so, I'm just speaking in general and thinking up hypothetical scenarios)
- deleted 5y ago[deleted]
- dagw 5y agobut emotionally it would seriously piss me off That is why choices like that should be left to project managers. As someone who is coding less and managing more these days, I have none of that ego left. If I could hire someone twice as good as me I would do so in a heart beat[1] and then go home and celebrate my great luck. [1] Assuming they aren't an asshole etc. etc.
- omnicognate 5y agoThat attitude among Haskell devs is one of the problems. The conviction that it is a fundamentally better way of programming and that anybody who chooses anything else for anything is a worse programmer certainly hampers its success. But the main reason, at least in my 20+ year career in my industry, is that it simply doesn't have a track record of success. Haskell isn't remotely new. It was mainstream in academia when I was at university and since then I've seen multiple attempts at adopting it in a large scale commercial setting. I've seen a couple of successes, on small, well defined projects that were relatively "academic" in nature (i.e. the challenges were in the comp-sci type aspects rather than the engineering, and the interactions with other systems were minimal). I've seen more failures, projects with lofty goals that went nowhere. F# has been more successful, and I've seen some significant infrastructure built with it, but it's certainly not proven itself superior to the alternatives (in an industry where successful solutions always get mimicked). Basically, it's 2022. People have tried it and it hasn't worked out.
- captaincaveman 5y agoI have similar opinions on Scala, lots of theory that it makes things better, but the only measurable difference is that its a nightmare to hire for, more expensive and we often have to invest time training people ... who then leave to become contractors. I'm not anti functional or Scala, but I'm yet to see any reports etc that actually indicate there is a pay off.
- grumpyprole 5y agoI don't even view Scala as a functional language, as functions (methods) are not first class. Lambdas are encoded as objects with a single method. It's much more expressive than Java and so better at expressing many functional programming ideas, but it's not a functional-first language, it's an evolution of Java. The underlying issue is that it's a complex language with many experimental and interacting features, which can and do cause a lot of distraction. This is not the fault of functional programming. Have a go at OCaml or F#, which are nice practical sweet spots.
- hocuspocus 5y agoThe JVM has had specialized bytecode for SAM types for a long time now, you cannot really get more "first-class" than that. And really it's just an implementation detail than doesn't make the language more or less functional. Scala isn't simply an evolution of Java. It offers a type system that goes beyond what you can do in F# or OCaml. The fact it's multi-paradigm and plays nice with Java's OO model doesn't make it less functional than these two.
- grumpyprole 5y ago> it's just an implementation detail than doesn't make the language more or less functional. It affects the language very much, awkward currying and tupling, needing to wrap methods in objects. Subtyping also has many complex consequences. There is limited type inference and tail call optimisation versus functional-first languages. > Scala isn't simply an evolution of Java. It offers a type system that goes beyond what you can do in F# or OCaml. It offers higher-kinded types, but F# has units of measure, OCaml has polymorphic variants. Each has advanced features not offered by the other. > The fact it's multi-paradigm and plays nice with Java's OO model doesn't make it less functional than these two. It was not designed as a functional programming language first and foremost, that is my point.
- tluyben2 5y ago> I mean how many people here, currently working in language X, would want to hire someone that is better than they are? I have always tried to hire better than I am (and ever will be); not to say i'm very good, but a lot of people are very bad. I hired, multiple times in my (30+ year) career people who are much better than I am at pure tech stuff like creating great code. I would love for someone to make me obsolete (I don't think looking stupid is a thing), then I can focus on other stuff. In my first company I was the founder and CTO; I replaced myself with a much better CTO who was so much better that I suddenly had literally nothing to do. So I went on to create + run our research (r&d) group which was a lot more fun than being CTO. Far too many people stay in positions they don't like for pure ego; I don't care what they call me as long as I like the work and I get paid enough, in that order. I guess when you have a job and this happening it would be less good. Although I would see it as a sign to go do something else.
- jodrellblank 5y ago> "as long as I like the work and I get paid enough, in that order." If you can deal with not getting paid enough, in what way is it "not enough"?
- jen20 5y ago> I mean how many people here, currently working in language X, would want to hire someone that is better than they are? Isn’t the adage “A players hire A players, B players hire C players”?