top | item 24464261

(no title)

codygman | 5 years ago

> I have written Haskell code and Haskell does not solve any real problem. Same goes for F# so no one uses

You are being down-voted for either lying or using such a ridiculous definition of "no one" to push your agenda while disregarding facts.

discuss

KingOfCoders|5 years ago

Ah sorry, took a look at your website, you're selling "Haskell consulting", so I might have insulted you personally with my post - which was not my intention.

With "no one" I exagerated and meant a tiny fraction of companies [1][2][3]

I will not use "no one" but "a tiny fraction of companies" in the future or at least make a note explaining "no one".

[1] https://redmonk.com/sogrady/2020/07/27/language-rankings-6-2...

[2] https://www.tiobe.com/tiobe-index/

[3] https://madnight.github.io/githut/#/

KingOfCoders|5 years ago

You can count the number of Haskell users here:

https://charliereese.ca/article/top-50-y-combinator-tech-sta...

"to push your agenda while disregarding facts. "

I have no agenda, what agenda would that be? What do you think my agenda is? I've written code in 20+ languages in 40 years from 6502 machine code to Prolog, LOGO and Blockly. Everyone of them has strengths and weaknesses. I like coding in most of them.

"while disregarding facts"

What are the facts?

If I have an agenda it's to split propaganda from facts. It's moving software development from strong opinions, fashion and cults towards facts and science, so as an industry and profession we can grow up.

"Haskell didn't solve a real problem"

lead to the downvotes, and not one reply with a counter example.

If Haskell solves a development problem the many people have and struggle with, what would it be? What problem does lazyness solve? I wrote 100k+ lines of Scala code with Monads and Monad transformers, it isn't better than my Typescript code. Purity? Good developers write pure methods in any programming language minimizing side effects. I could go on with immutability, which get's you down a rabbit whole of lenses ( I wrote a lengthy article here https://svese.dev/concurrency-with-immutable-data-primer/ ) with few benefits.

There are two possible prominent explanations for Haskells failure in the development world. First it didn't solve a real problem as Assembler (easier to read and write than machine code), C (everyone did 'C' already with extensive assembler macro collections), Perl (better shell programming), Lua (easy to embed), Java (garbage collection), PHP (everyone who can write HTML can write PHP), JS/Node (people allready know frontend JS), Ruby (Rails) and Typescript (JS with type safety) did and Rust (safe C) now does. Or every developer is too stupid to see the light.

tome|5 years ago

I don't think this kind of thing really needs to be engaged with. Let such commenters stew in their own juice. Pushing back only adds flames to the fire.

KingOfCoders|5 years ago

Thanks though for helping my point. No argument that counters my post but an ad hominem attack [1]. The state of our industry in 2020.

If you disagree with my point of

"Haskell didn't solve a real problem."

you could have a counter argument. Like "From my experience many companies struggle with X, which is essential to their development effort. Haskell does solve X nicely, a magnitude better than competing efforts like A, B and C from working with Haskell in a larger company and B in a startup. My opinion that companies do not use Haskell though is not that it doesn't solve a real problem - as shown above - but because of S and T".

Or you could downvote

"Haskell didn't solve a real problem."

[1] I like to be labeled "such commenters" - though I would prefer "such people", it's meaner and has more punch. So if you go ad hominem, go right for it.