Attached: HaskellBTFO.png (1263x135, 49K)
Haskell BTFO
Ryder Price
Lincoln Moore
is this true?
i want to learn haskell just because it's the most well known pure functional language but is it useless in the real world?
Jaxson Miller
Yes, just look over complex code from Haskell experts agains average Java Code and Java still wins.
benchmarksgame-team.pages.debian.net
Haskell is an eternal research project, no practical language.
Thomas Gray
>is this true?
it is true for every language in existence, you simply can't write simple code for complex problem.
competents mathematicians wrote on this in the 50-60s, see Turing article on AI or Kolmogorov complexity for example.
>is it useless in the real world?
yes, FP is NOT superior to "traditional" imperative programming.
Anthony Lewis
Just learn D and use pure, nothrow functions where you can and design by contract to avoid many bugs. Boom, you just got 100x more productive than you would be with Haskell.
Jackson Brooks
The problem is that nobody knows at the beginning of a software project what it will end up being in the end, unless they spend enormous amounts of time and money up front, like they have to do with stuff that they shoot up into space. The consequence is that the awesome solution that you built to elegantly solve the problem you thought you had at the beginning now looks a lot less awesome and elegant because the problem changed on you.
Gabriel Thompson
D finally backtracked on GC (as least partially), and it will be a decade before they realize that exceptions were a mistake too.
Julian Campbell
>Individuals and interactions over processes and tools
Shit developers write shit code, good developers try hard not to write code at all, because once the shit developers touch it, it will turn to shit. Language is orthogonal.
Luis Baker
Fuck you exceptions are great, go is cancer
Asher White
Exceptions are cancer in every language that has them
Wyatt Parker
Factually false
No boomers allowed on this board
Ethan Howard
Okay, now tell me why unpredictable stack unwinding and oodles of spaghetti and boilerplate code is a good thing, rather than returning an optional or a result/status tuple.
Samuel Perry
Haskell is useless, just learn F# to leverage the CLR and .NET ecosystem while still working within an FPL
Robert Green
Learn J
Grayson Harris
>if err != nil
>if err != nil
>if err != nil
Wow, so clean and intuitive.
Benjamin Morales
Early return is far more intuitive than try ... catch a thousand nested times.
Also
>His programming language doesn't make null falsy
Pleb
Leo James
That's why Haskell is superior, monads avoid this kind of boilerplate
Jaxon Rodriguez
Fuck you acronym nigger.
Oliver Ramirez
>D finally backtracked on GC
They didn't 'backtrack', so much as they recognized that everyone who actually used the language actually used custom memory management and couldn't afford to rely on their garbage-garbage collector and so they added the option to just strip it out officially. It always supported manual memory though, as it was always intended to work in the same domains as C++.
Jordan Perez
Monads just obscure the error so now you have no idea why something failed.
Ian Thomas
Dont learn J, it's a meme language
Adam Lopez
They don't. The Except monad interface is in fact similar to the one of exceptions, but it's actually nothing but a wrapped Either.
Brody Ward
Uhhh no
The GC is why the C++/rust faggots refuse to touch the language. The idea that "everybody" is using custom allocators is completely retarded and overblown.
There's a -betterC mode but it's just a subset of the language (no classes for example). SOME people are using it.
People are happily using the normal language, with GC, no matter what all the manual memory management zealots say.
Chase White
use D as a betterC with no GC.
what's the excuse now?
C is deprecated and people insist on using it for elitist purposes
Nathan Brown
That's fine but I was responding to the moronic notion that vanilla, GC'ed dlang is somehow unusable and unwanted by all.
Jacob Jones
>GC'ed dlang is somehow unusable and unwanted by all
It's not "unusable" and can work fine for tons of things, but a lot of the projects people use D for are latency sensitive and hence there was real demand for more non-gc features.
Kayden Adams
There are exactly 2 acronyms in my sentence and both are 100% recognizable if you spent more than a day on Jow Forums
Carson Baker
haskell is literally java of functional languages, dont learn it, better learn erlang, its much more fun
Dylan Brown
Lack of exceptions is LITERALLY why C is safer than Ada
en.wikipedia.org
You don't use exceptions on critical infrastructure. It's a recipe for disaster.
Jeremiah Edwards
Almost everything you read in here is ass pulls without any arguments or evidence.
Jaxon Ross
You're an idiot. It crashed because they tried to fit a 64 bit value into a 16 bit slot, didn't check for overflow and never tested the code on a simulator. If anything, Ada made the right decision. It hung under undefined behavior with no handler. If this was C, it would have just filled the 16 bits with junk data and tried to navigate based off of that. More importantly, all modern hardware is exception based. When you fuck up, you get an interrupt, not a return value. You seem to think programming languages shouldn't have support for the same error handling that the physical hardware has.
Andrew Scott
java is great though, no one can hate on it without pajeetFactory memes
Isaac Baker
it does the job but the language is really ugly, boring and tedious
Andrew Flores
>imagine listening to a fucking reddittor. Sage and kys
Matthew Davis
>>D finally backtracked on GC
>They didn't 'backtrack'
Read the early shit Bright wrote about GC being better than manual management in every regard, including theoretical performance. It absolutely has not aged well.
Unfortunately GC is already baked into core language libraries and types, so no amount of waving 'nogc' around can fix everything.
Isaiah Moore
Are you some Windows/SEH babby who magically equates segfaults with catch() blocks?
Software exceptions are language control flow frameworks, not hardware watchdogs. Protip: a single term can have different meanings in different contexts.
Luis Anderson
Link if you don't mind, I'd like a peak into history