3 ms·
I wouldn't mind a Rust based web framework that provides the same features as the base Servlet API. Everything else should be an optional library. When I look i
by palmfacehn 2y ago
I wouldn't mind a Rust based web framework that provides the same features as the base Servlet API. Everything else should be an optional library. When I look into it the rabbit hole goes too deep. It hasn't been immediately clear what the templating looks like. Usually they start talking about some "Reactive" framework, features I don't want and I lose interest. Afterwards, I realize that I'm already satisfied with my current web stack.
Jetty, HAProxy, JSTL, commons db connection pooling and Postgres.
- masklinn 2y agoIt’s really not clear what you mean by “basic servlet API”, because the main rust web frameworks are pretty much just routing by default, with (largely opt-in) parsing and serialisation support. It “hasn’t been clear what the templating looks” like because there isn’t any just as AFAIK servlets provide no templating.
- stefs 2y agojust out of curiosity: why commons db connection pooling instead of hikari? i've only ever used the latter.
- palmfacehn 2y agoI've been using version two for a long time now. It just works. I hadn't heard of Hikari until now.