4 ms·

Having read this, I appreciate much more why Dispatch is the way it is. As a newcomer to Scala, I wish this wasn't the standard recommendation then. I was alm

Having read this, I appreciate much more why Dispatch is the way it is. As a newcomer to Scala, I wish this wasn't the standard recommendation then. I was almost put off entirely when after 2 solid days I still couldn't issue an HTTP request. Fortunately I'm on the JVM and had other options, which I ultimately went with, but I was trying hard to embrace the Scala way and just coming up totally frustrated. If a simpler library were the starting point and Dispatch used for more advanced cases (again, as community recommendations), I posit there'd be a lot less vitriol.

weego 15y ago
But that's pretty much every Scala library right now. Every time I go out to find something I need it is always syntactically and documentationally complex/lacking and I wish that some of the visual simplicity that is available in things like python/ruby were available. After all, it is an incredibly versatile language right? So why is everything done in seemingly the most academically challenging way rather than in a way that allows developers to actually get shit done quick and go home for dinner. Any why do libraries get obsessed with having 2 or 3 ways to do something without documenting any one of them well enough or having any indicator of which one is better and if one is, why (Lift is particularly bad here though it is a fantastic tool once you get to grips with it).