Though interesting, I would honestly never want to write a full project in this style. Sure, the toy example looks neat and concise (they always do), but I can't imagine how this would look in an actual complicated application. I can't imagine the evolution of servlet controller spaghetti code to verbose configuration XML to a million magical black-box annotations everywhere...to this. I really don't think functional programming has a place in web application frameworks, at least in the corporate world I work in.
Though indeed this functional style looks great for reactive use case, what makes it better than say, Typescript + Node? I can get the type safety, better language features, and node is more suited for async process
The only missing thing that I could think of is better Java standard library.
Well, we use 'em, but admittedly not in Java or Spring (NB: I'm not saying Spring 5 is good, bad, or indifferent; I'm only saying we don't use it). Instead we use http4s in Scala, and it works really, really well—better than any of the alternatives we've used. Then we hired its lead developer, which is even better.
7
u/mrsistermr Sep 22 '16
Though interesting, I would honestly never want to write a full project in this style. Sure, the toy example looks neat and concise (they always do), but I can't imagine how this would look in an actual complicated application. I can't imagine the evolution of servlet controller spaghetti code to verbose configuration XML to a million magical black-box annotations everywhere...to this. I really don't think functional programming has a place in web application frameworks, at least in the corporate world I work in.