Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@whimsical not just the web api, but also storage and the BL, everything, the whole backend!
It freaking blew my mind! -
@whimsical I have no idea why. As I said, I was as surprised as you are. As for what I‘m making, I don’t want to tell on devrant directly but you can look it up in my github if you like.
-
@whimsical nice! 😄
-
@Liebranca seems like it’s a trope in the functional space :(
-
@AlgoRythm the academic circle jerk does indeed breed higher forms of degeneracy.
but more on topic i vaguely recall trying both ocaml and haskell at one point out of curiosity forever ago, wanted to see what the fuzz was about. my lasting impression is that functional languages were specifically designed for mathematicians to cosplay as programmers, i really do get that vibe.
as i see it, strict FP makes nearly everything more complicated than it needs to be for no benefit, save a vague sense of correctness that i find to be more illusory than anything else. akin to writing an abstract class for the first time, not quite right but feels like it if you think hard enough. i can't stand the hyperfocus on theory rather than practice is what i'm getting at.
anyway, learn haskell, 0/10 it's the last thing i would recommend to a sentient being. but if you want to learn functional it'll do the trick. -
@Liebranca I spent today studying F# and I can confirm the stdlib is the main drawback: it's designed to be compatible with the .net framework 100%, so the function calls are not curried by default, they're tupled. So insted of calling them in a functional way, you call them in a traditional c# etc way;
F#:
print "hello %s" world
F# Standard library:
print("Hello %s", world)
Which was a major disappointment, so I'll be shelving this functional thing and moving to Haskell when I get the itch again. Shame. -
@Liebranca In reference to what you actually said, I agree. From my reading, the real benefits of functional languages is they're optimized for recursion (or, more to the point, they're more optimized to turn recursion into something actually performant!)
From the code I've been writing, it's a lot more difficult, but the code ends up being shorter and a lot closer to what you're actually trying to do.
Like, I saw a quicksort (unoptimized) that was essentially just the algorithm in plain f#. There was barely any implementation, it was just "here's how the algorithm works, here's how to say that in f#, done"
https://fsharpforfunandprofit.com/p...
I'm thinking of moving into functional programming. I'm deciding between F# and Haskell. I don't like that both have indentation as syntax, but that's neither here nor there.
I know the .net core stdlib like the back of my hand. I'm trying to decide - and, as the purpose of this post, trying to ask the community - if this is a *bad* thing when trying to learn a new programming paradigm.
In other words, I think I want to try Haskell because I won't be able to lean on my knowledge of the standard library. I'll be forced to actually understand the language and learn functional concepts, instead of trying to bring my OOP knowledge over from C#.
Additionally, the .net stdlib is obviously built in a OOP design, so I'm afraid that the F# stdlib might suffer from that too.
But I'm still thinking that maybe my knowledge of the .net stdlib will be more helpful than harmful? Like, yes, I'll be using it as a crutch but at least I won't be trying to learn three things at a time (stdlib, syntax, and paradigm) and can focus solely on the syntax and paradigm.
Anyone have any insight into this problem, or maybe some wild guesses?
question