My own approach to learning FP has been "Hello Haskell", "Hello Scala", "Hello ML", "Hello Clojure", "Hello Rust",...
I don't know why you say goodbye, I say hello.
Hello Haskell, Goodbye Scala
21–30 of 118 posts
Re: Hello Haskell, Goodbye Scala
#22For personal projects or for learning the principles of FP, there is nothing wrong with using Haskell. From personal experience however, I will not be using Haskell again for a larger professional project, because our team ran into too many time consuming issues and problems that have been solved successfully in other languages/environments (especially the JVM) like dependency management or reasoning over runtime cha…
What is a war file?
It's short for (Web Application ARchive), it's a jar file used for deploying web applications written to work on the JVM.
Re: Hello Haskell, Goodbye Scala
#23I've invested a lot of time in trying to learn Haskell properly. On one hand, it's incredibly rewarding when a completely new and strange concept finally 'clicks', then you write a few lines to test your understanding and it just works. On the other hand, it's frustrating to realize that there are still a lot of concepts you don't fully grasp, several libs that are still out of your reach, yet another completely new…
One of the things I like about Haskell is that there's never scarcity of new concepts to learn: Functors, Applicatives, Monoids, Monads, Monad transformers, Comonads, Arrows, Lenses, Foldables, Iteratees... And every one of these has a world in itself!
Re: Hello Haskell, Goodbye Scala
#24For personal projects or for learning the principles of FP, there is nothing wrong with using Haskell. From personal experience however, I will not be using Haskell again for a larger professional project, because our team ran into too many time consuming issues and problems that have been solved successfully in other languages/environments (especially the JVM) like dependency management or reasoning over runtime cha…
When did you use Haskell? The dependency hell situation has vastly improved (and there are plans to make it much better still). I agree that a downside of Haskell's very high level nature is difficulty to predict some runtime characteristics. This is just an instance of the general trade-off between low-level and high-level languages. Everyone is already comfortable with the loss of easily predictable performance inc…
Could you elaborate what 'real-world' means to you in this context? Millions of users, hundreds of servers, a personal blog? 'Real-world' is often a very broad term with a huge likelihood of misunderstandings.
Re: Hello Haskell, Goodbye Scala
#25I learned F# as this guy learned Scala. I too dived into Haskell after a while and learnt a lot of new things. Having learned some great functional tips, I came back to my regular C#/Ruby and applying LINQ and Ruby's blocks seemed more natural to me. However, monads, monoids, functors still don't matter when you switch over. I've used Yesod to write a small app. A typical form in Yesod (for model binding) has this si…
Comparing a statically typed language to a dynamically typed language is silly when talking about type signatures. Of course you don't have type annotations in Ruby, it's a dynamic language. But it also means you don't get compile-time guarantees.
Ask yourself what would be the type signature of a similar function in another statically typed language. You have a parametrized type with three parameters, which would give you something like:
MForm
Re: Hello Haskell, Goodbye Scala
#26Earlier quoted context omitted.
Maybe one shouldn't make general comments about a piece one hasn't read in its entirety. Especially for an 11 small paragraphs piece.
I did read it fully. Then I commented that I found it unconvincing, which in my book is one step below misleading.
I then find unconvincing your usage of the word unconvincing.
Re: Hello Haskell, Goodbye Scala
#27Earlier quoted context omitted.
When did you use Haskell? The dependency hell situation has vastly improved (and there are plans to make it much better still). I agree that a downside of Haskell's very high level nature is difficulty to predict some runtime characteristics. This is just an instance of the general trade-off between low-level and high-level languages. Everyone is already comfortable with the loss of easily predictable performance inc…
>When did you use Haskell? Roughly two years ago. >I think the silliness about PhD's is very very silly. Of course it is. I just wanted to make a point that the "average programmer" has probably never seen a single line of ML-syntax before. >About profiling -- I have never profiled a Scala/Java application, but how much easier is it compared with: "cabal configure --enable executable-profiling", and then running the…
Two years ago the situation was far worse, dependency-hell-wise.
About hooking up the process for some profiling information, take a look at:
http://ocharles.org.uk/blog/posts/2012-12-11-24-day-of-hacka...
Re: Hello Haskell, Goodbye Scala
#28I've invested a lot of time in trying to learn Haskell properly. On one hand, it's incredibly rewarding when a completely new and strange concept finally 'clicks', then you write a few lines to test your understanding and it just works. On the other hand, it's frustrating to realize that there are still a lot of concepts you don't fully grasp, several libs that are still out of your reach, yet another completely new…
I personally find the "universe of knowledge" to attain an attraction, not a repellent.
I guess it depends in what context you're looking at it. What makes Java so successful is its simplicity. You can get fairly quickly up to speed on it, and you can have junior coders on it producing code quickly without shooting themselves in the foot too much or spending a couple of hours trying to find out how to update a tree efficiently.
On the other hand, as a hobbyist, it's absolutely fantastic.
Re: Hello Haskell, Goodbye Scala
#29Earlier quoted context omitted.
When did you use Haskell? The dependency hell situation has vastly improved (and there are plans to make it much better still). I agree that a downside of Haskell's very high level nature is difficulty to predict some runtime characteristics. This is just an instance of the general trade-off between low-level and high-level languages. Everyone is already comfortable with the loss of easily predictable performance inc…
Could you elaborate what 'real-world' means to you in this context? Millions of users, hundreds of servers, a personal blog? 'Real-world' is often a very broad term with a huge likelihood of misunderstandings.
Serving my real needs both for a professional job:
* Debug information processing and analysis
* Concurrent execution of tests
* Build systems
* Various automation/scripting needs and other auxiliary projects
Also, in a different context, a structural editor for programming based on our own GUI framework (~10KLOC so far). This project is still preliminary but advancing at a (mostly) steady pace.
Re: Hello Haskell, Goodbye Scala
#30For personal projects or for learning the principles of FP, there is nothing wrong with using Haskell. From personal experience however, I will not be using Haskell again for a larger professional project, because our team ran into too many time consuming issues and problems that have been solved successfully in other languages/environments (especially the JVM) like dependency management or reasoning over runtime cha…
Interestingly, despite their respective reputations Haskell is by far more popular than Scala: