In 45 minutes I made a #kotlin#javalin application from scratch, which uses #webjars to include #htmx from a #maven pom file. It uses static #HTML files for the first load, and then renders HTML from #jte templates for #SSR of the parts of the pages that need that kind of interaction. There's no #springboot (or any #spring at all) and no #SPA like #angular or #react.
Now because simply setting up a project says close to nothing about its real world viability, next step is an actual usecase ( :
I haven't worked with Thymeleaf; I used to do SSR using #JSP and later #Freemarker.
As for natural templating: I expect it to make my fragments more clear when the serverside directives are explicitly not in the HTML, like with JTE, whereas the clientside directives are, as HTMX. Less confusing than when clientside and serverside logic are both inline in the same HTML template.
I have just learned that "#Java Bean" has two completely different and incompatible definitions.
One is a dumb, badly designed data object with getters and setters.
The other is... a service object managed by the Spring framework IoC container.
Holy hell. This is 10x worse than #Laravel "facades."
Am I wrong here? This is what I'm finding from online tutorials. Is there more nuance that is not coming through, because for now I just hate #Spring even more.
Here's yesterday's talk "Creative Coding in #OPENRNDR" at the #Kotlin Conf 2024. The first half show work by Edwin (principal developer of the framework) and the RNDR team.
The second part, starting at 6:32:25 (25 min. long), live codes a poster with two graphic layers and one with text.