It’s not as powerful as in Idris or Agda, but still reaches that convenient middle point where you can describe almost anything, and yet type inference works well. Igor Shevnin ( interphx): A great type system. John Doe: Strict, strong (even fascist, I’d say) typization. Building abstractions of data and algorithms is rather simple, which allows to think about the task at hand without getting distracted by little annoyances too much. Yuri Syrovetskiy: It’s (subjectively) easy to adapt your thoughts to code, it has a great balance of imperative and functional paradigms. No wonder half the libraries there are on EDSL (or at least it feels like it). Yuri Syrovetskiy ( cblp): the hardest thing is to learn Haskell as your second language, when memories from learning the first one are still fresh, What is Haskell good and bad it? Doctor_Ryner: It’s concise, elegant and flexible. Tutorials aren’t too user-friendly, though, plus its imperative background prevents new concepts from emerging. I was fascinated by its unique concepts and how neat it was. First I practiced in JavaScript, but then I learned about Haskell, considered to be the “true” functional language.
Haskell language trial#
Doctor_Ryner: Once I failed my trial period at a job because of a Redux fuckup, so I tried to get a bit more comfortable with it by watching videos from its creator. Maybe that’s why it’s so hard for them to learn Haskell: it gets harder to learn new stuff with age. People tend to forget (or smooth out) their earlier memories: like when they were struggling to understand what a “pointer”, “function” or “class” was.
Haskell language code#
It’s like learning to code from scratch all over again. When you start learning Haskell, you have to cram a lot of new concepts into your mind. Then I found a job as a Haskell programmer. I’ve written one of my term papers, plus the graduation paper, on GHC. Then we also had a functional programming course that included Haskell. Denis Mirzoev ( nolane): When I was in college, they’ve offered me to do a Coursera course on Haskell for extra credit. Nevertheless, a couple of people did tell me about their experiences, which are shown below. Instead, they focused on building a logical, principal way of solving real problems over trying to appease the widest audience possible” Someone wrote to me: “One of the defining features of both Haskell itself and its community is that they didn’t try to achieve any kind of mainstream recognition.
Haskell language full#
If the topic is ever brought up, it’s only talked about in full depth and as objectively as possible. Haskell doesn’t lend itself to popular explanation, and people seemingly don’t even try. I was quite afraid at first, and, as it turned out, I was right. To get to know Haskell programmers better, I came to a topical Telegram chat with some questions. Until then, all I heard about Haskell could be summarized as “be VERY careful in dealing with it”.
And even though the answer was rather polite and well-supported with arguments, it still sounded like “Come on, don’t even bring up these toys”. I carefully asked if they considered using something more popular and new. Which was part of the reason he came to Moscow. The work stack included Haskell and C++, among others, and the founder was complaining about how hard it is to find competent programmers.
I once had a discussion with a founder of an Israeli startup developing a GPU-based database with a focus on speed.
0 kommentar(er)
