151
all 40 comments
sorted by: hot top controversial new old
[-] squaresinger@lemmy.world 51 points 3 weeks ago

Why do programs written in Haskell not have side effects?

To have side effects someone would have to run the programs.

[-] MonkderVierte@lemmy.zip 0 points 3 weeks ago
[-] squaresinger@lemmy.world 2 points 3 weeks ago

Yeah, there's like two projects that use Haskell. Doesn't change the fact that it's the language that most people know and will never write anything productive in it.

[-] MonkderVierte@lemmy.zip 3 points 3 weeks ago* (last edited 3 weeks ago)

Eh, i'm not a math type but for them, Haskell is chef's kiss from what i've heard.

[-] RustyNova@lemmy.world 31 points 3 weeks ago

Count us rust folks in. Typescript may doing it's best, but it's not as great

[-] Redkey@programming.dev 11 points 3 weeks ago

I started programming in a time when the idea that the computer could keep track of your variable types for you automatically was a fever dream, so it's wild for me to see some programmers now throwing shade at particular langages for "not implementing proper variable typing functionality".

It feels like someone saying that low-fat milk producers are too cheap or lazy to put enough fat in their milk.

Fashion really does go in cycles.

[-] calcopiritus@lemmy.world 12 points 3 weeks ago

It was a dream when it wasn't available. Once it existed, we saw the many flaws it had. That's why statically strong typed languages still exist. And even new ones are being created.

[-] CanadaPlus@futurology.today 12 points 3 weeks ago* (last edited 3 weeks ago)

I don't even think it's fashion. Some ideas sound good but are bad. Or, overlappingly, are convenient to use but actually turn into nightmarish spaghetti code. I don't know how many people are still pushing MongoDB and BASE, for example.

Meanwhile SQL hasn't changed, and C didn't until someone figured out memory safety in Rust.

[-] squaresinger@lemmy.world 9 points 3 weeks ago

Fashion really does go in cycles.

This here.

When I got into programming I figured it would be mostly linear technological progression. Every once in a while something new gets invented that's better than the last iteration, so we discard the last option (except for legacy stuff) and everyone moves to the better thing.

But since then everything that was cool back then became uncool and cool again at least once.

I like the SQL/No-SQL cycle. SQL is powerful, but it's also slow and clunky and if you do it badly it gets really slow. So we invented No-SQL DBs. They are fast, lightweight, but also barebones and limited. So we add functionality here and there, and before we know it we have another variant of SQL with a different syntax. So we head back to use real SQL. But then we realize it's slow and clunky and if you do it badly it gets really slow. So we invent a new No-SQL DB and the cycle continues.

[-] Feyd@programming.dev 5 points 3 weeks ago

It's more that nosql makes sense of you have very specific performance characteristics and can accept very specific constraints.

Alternatively, you want to use a document db because you don't understand that delaying implementing schema integrity or implementing it yourself in the application layer instead of having it baked into your database will be more complex and slow you down in the long run. RDBMS isn't slower than a generic document DB.

[-] squaresinger@lemmy.world 1 points 3 weeks ago

That's pretty much my point. Actual Nosql does have use cases, but more often than not it was used for hype reasons. "Everyone uses Nosql, let's not become legacy and hop on the Nosql train!"

Document DBs came out of Nosql, and are pretty much the same as SQL for most use cases, just with their own funky syntax.

And then again there are the use cases where people use SQL without relations, basically as a Nosql DB. Just do ORM for everything, do the database stuff in memory in Java and just use SQL to dump crap into.

[-] Feyd@programming.dev 9 points 3 weeks ago

1950??? Statically typed programming languages are very old....

[-] Redkey@programming.dev 4 points 3 weeks ago

Sorry for not being clear; when I said "keep track automatically" I meant dynamic typing. Of course you're right that "keeping track of your variables" could also be interpreted to refer to static typing.

[-] chonglibloodsport@lemmy.world 3 points 3 weeks ago

Haskell keeps track of your types automatically. You can ask it “what is the type of this expression” and it will infer it for you. Haskell is of course fully static typed (types erased at compile time).

[-] MonkderVierte@lemmy.zip 1 points 3 weeks ago

GOTO is all i'm saying.

[-] onlinepersona@programming.dev 9 points 3 weeks ago

The same reaction whenever I look at haskell. A "pure" language with an escape hatch that has a fancy name. Once you open the escape hatch, you can write entirely impure code in Haskell and never see a pure function in your life. So much for "pure".

[-] chaos@beehaw.org 21 points 3 weeks ago

You say your house is clean, yet nothing's stopping me from dumping out this bucket of mud on your floor, curious!

[-] Redkey@programming.dev 1 points 3 weeks ago

Reading current discussion, it seems more like "You say that it's impossible to dirty your house, yet nothing's stopping anyone from dumping out this bucket of mud on your floor, curious!"

[-] davidagain@lemmy.world 4 points 3 weeks ago

Same goes for rust and memory safety. What's your point?

[-] into_highest_invite@lemmygrad.ml 2 points 3 weeks ago

the only languages that don't have an escape hatch of some sort are languages with no safety in the first place. the escape hatch is an important part of treating your developer like an adult

[-] marcos@lemmy.world 6 points 3 weeks ago

Are extensible records usable already?

Not that I would pick TS because of that, but the disdain is undeserved when it has some very useful features that Haskell has been trying to copy for years.

[-] ultimate_worrier@lemmy.dbzer0.com 8 points 3 weeks ago* (last edited 3 weeks ago)

The features Haskell has been “trying to copy” from TypeScript are, without exception, features TypeScript copied from type theory research that predates TypeScript by decades – row polymorphism from Didier Rémy’s 1989 work, untagged unions from the intersection type literature of the 1980s, type-level computation from Martin-Löf’s 1975 intuitionistic type theory – and what you are observing is not Haskell enviously watching TypeScript and taking notes, but rather two languages drinking from the same well of ideas, one of which is doing so with a formal semantics and a proof of soundness, and the other of which is doing so while standing in a JavaScript runtime and hoping no one looks down.​​​​​​​​​​​​​​​​

Purescript > Typescript

[-] davidagain@lemmy.world 4 points 3 weeks ago

Elm for ever!

[-] MonkderVierte@lemmy.zip 4 points 3 weeks ago
[-] kcuf@lemmy.world 4 points 3 weeks ago

This is true

[-] Blackmist@feddit.uk 4 points 3 weeks ago

Yeah, but you still can't explain monads.

[-] sommerset@thelemmy.club 3 points 3 weeks ago

Php has real enforced types

[-] raman_klogius@ani.social 2 points 3 weeks ago

Haskellers when someone boasts about Typescript's fake type system.

[-] MonkderVierte@lemmy.zip 1 points 3 weeks ago

Haskellers when someone boasts about Typescript's fake type system.

[-] sirico@feddit.uk 2 points 3 weeks ago

It puts the fun in functional

[-] _stranger_@lemmy.world 0 points 3 weeks ago

HOW CAN TYPES BE REAL IF OUR EYES AREN'T REAL

this post was submitted on 09 Apr 2026
151 points (96.9% liked)

Programmer Humor

31253 readers
1914 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS