602 karma · joined April 15, 2014
Hiring was actually Haskell’s strong side. I managed to hire 6 engineers in only one month. There were more than 50 applicants to the position. Just the idea of using Haskell in production is attractive to many.
It’s been a great experience overall. I worked at a python company before this one and it’s been refreshing not having unexpected runtime errors. Moving money around requires more robustness than your typical app.
On the other hand, if you have to explain how the for/yield in zio and why it works for so many different types, you have to basically explain Monad using another name.
By reading the docs I could easily recognize monads. If you replace “for” with “do”, they even have the same syntax! I could also see clear examples of things that were modeled as monoids and functors. I would claim that zio took inspiration from Haskell to model the composable parts.
Hey, I’m not complaining about any code, and specially not flatMap. I think it is a great design. It is the bind operator in the monad class in Haskell, and there is also syntax sugar to hide it and make it look like imperative code, just like Haskell. I like that!
It seems to me that it is fair to say that the abstractions are useful as you recognize in your previous comment. Maybe you just have an aversion against the abstraction names, or the way many Haskell-related articles go on and explain them… which is fair enough.
I learned Haskell without having to understand those concepts. I could just used them by experimenting with what was possible and seeing examples from other people. It was not particularly difficult. So, as you also figured out with zio, understanding the abstractions is not a requirement for using them.
That first example shows that the for syntax desugars to nested flatMap. Which is analogous to Haskell’s do notation, which desugars to nested bind.
The abstractions you said are not there, seem to actually be there in zio!
https://github.com/brendanhay/amazonka
I use the package directly from GitHub in my project.
Debugging has not been difficult either, but I have always use print debugging in every language, so there is not much I can compare.
https://hackage.haskell.org/package/optics-0.1/docs/Optics.h...
More likely, network effects can explain how something makes it to the mainstream. For example having a big corporation behind the development and marketing of the language.
You can load your entire project in the repl and try your functions there.
Does not match my experience. Haskell typically compiles to quite performant code, at least for all the cases that I’ve used it for.
Then few times I had to optimize anything for performance, it did not feel different than other languages. It was in almost every case about the architecture of the code and not something to do with the language itself.
We are a group of 8 engineers using Haskell exclusively working on payments and checkout related solutions.
The experience has been amazing so far. We are able to ship with great velocity considering the size of the team. We have also been able to refactor things easily when requirements change. Haskell has helped in keeping the code in good shape even after the many direction changes.
Polymorphism is front an central to everything in Haskell, which is why your comment sound off to me.
You can do `apt-get install my_package==4.1.*`, for instance and that will pass the validation and still be close to the ideal of having reproducible builds.
I have to anecdotes of having to drop features in a large python program due to memory leaks.
The first one was when someone introduced an endpoint that consumed data from a gRPC service. After weeks of effort trying to find where the source of the leak was, we decided to drop the change as we could not find the cause in a reasonable time.
The second case was when introducing jaeger for distributed tracing. Similarly to the previous story, it was cheaper for us to drop the feature and use something else than to figure out where the memory leak was.
I believe that it is a matter of balancing effort vs, benefit. I would not be surprised if someone working on their free time on an open source project decides to drop a feature because they cannot find the time to make it work properly.