Java's Cultural Problem

1

Javalin

I agree with you about both magic and reactivity (meaning, IIUC, asynchronous rather than blocking APIs). Helidon Nima looks interesting. But what I'd really like is a non-magic, non-reactive server-side web framework that's designed to be used for full-stack, server-side web applications, including things like strongly-typed HTML templates, form validation and rendering, cookie-based authentication, and CSRF protection. Something we can use to develop a complete server-side web application, the kind that everyone used to write before the division into back-end API and front-end SPA became popular. Helidon Nima might be a good starting point for such a framework. Another starting point worth looking at is Javalin [1]. [1]: https://javalin.io/.

#Web Frameworks #Developer Tools #Python Web Framework 33 social mentions

2

Spark Framework

I can't stand any magic, it always inevitably feels like a massive liability to me and always bites me in the ass sooner or later. I use http://sparkjava.com in my projects. It's as tiny as web frameworks get, it only handles routing and request/response, and you get to do everything else manually. Only thing I had to hack into it was response streaming. The one most internally convoluted and enterprise-y dependency I use is, surprisingly, the official MySQL driver.

#Developer Tools #Web Frameworks #Runtime 28 social mentions