[XBigTK13X]

A single tech stack can only teach me a limited amount. When I build something around an unknown-to-me language/framework/tool over a weekend, I usually walk away with new insights.

For example, playing with Meteor (js) was the first time I was able to understand the concept of pub/sub.

That knowledge can sometimes be brought back to other tools I use, sometimes not. When it cannot easily transfer, the new tool gains brownie points. Playing with the "flavor of the month" taught me something useful. If I stayed with the same established workflow I always use, then I wouldn't have had a reason to encounter pub/sub.

[gaius]

Sorry, but that's nonsense, go and try Haskell for a year and you will have barely scratched the surface.

[uniclaude]

Well maybe, but does this seriously matter?

That's a very bad thing to spread. Haskell might be deep, but after using it for a whole year in production, any developer worth his salt would know enough of it to build non trivial things.

This type of comments unfortunately keep developers away from Haskell. Haskell is no C++, you can actually learn it, and it is a very good language.

[XBigTK13X]

Barely scratched the surface of what the language can do or the possible insights available by using Haskell?

I ask because I have done exactly what I described above, both with Haskell and Haskell frameworks.