Josiah Noel

> but once we start building content/html apps then I think we are going to get requests for an equivalent to JAX-RS Response I'm not following, why would html apps...

> Because then that code is specific to the webserver (Jex, Helidon etc) If we had more servers with differing API, this point would be more effective for me. Barring...

> if both JAX-RS & Spring have this abstracted... it just seems natural. For me, the difference is that the microframeworks used by Avaje-HTTP already have high-level abstractions that make...

> Yes. HTMX apps migrating between Helidon and Jex and for myself I've already done one of these. This isn't big/difficult work at the moment at all but I think...

> Also, I wanted to make a Jex-like abstraction and associated avaje-http generator for HTTP3. QUIC runs on UDP, therefore you can and should run with the same certificate/keystore and...

> I'm unconvinced by this. Is there any particular reason? Pros: - It all but eliminates "diff noise" due to whitespace and other insignificant formatting choices, allowing contributors/reviewers to focus...

do you have one in mind that I can setup automatic formatting with?

For me I couldn't care less about any particular code style, it's just that a standard format that can be enforced automatically makes contribution/reviewing easier.

what do you think about https://github.com/palantir/palantir-java-format

> it does kinda suck in some DSL cases [e.g. ebean query bean queries] okay, but are those DSL cases in this repo/pr? I'm not talking about changing what you...