31–37 of 37 posts
Earlier quoted context omitted.
React fails the main requirements: “Server rendered web pages, no fancy client side js, just good old websites.”
React JSX is hands down the best templating engine for Server Rendered Pages, imo. Doesn't have to be a SPA or include a bunch of fancy client side JS or anything.
Earlier quoted context omitted.
React fails the main requirements: “Server rendered web pages, no fancy client side js, just good old websites.”
"By default, Next.js pre-renders every page. This means that Next.js generates HTML for each page in advance, instead of having it all done by client-side JavaScript. Pre-rendering can result in better performance and SEO."
PHP => Laravel/Symfony, Python => Django, Ruby => Rails You just can't go wrong with one of these 3 above. Boring. Tested. Server side web pages All the 3 above also have great communities, support, documentation and above all, plenty of experienced talent over the years. These are battle tested.
Earlier quoted context omitted.
React JSX is hands down the best templating engine for Server Rendered Pages, imo. Doesn't have to be a SPA or include a bunch of fancy client side JS or anything.
Cool, good to know. What makes JSX such a good templating engine?
My sense with many templating engines is they are trying to crowbar programming functionality into HTML and always comes across clunky. It's usually a separate language from your server code entirely. Inline If statements and For Loops embedded in your HTML. And composing a template with a subtemplate is often clumsy.
With JSX you just write your normal JavaScript or Typescript and output JSX. Then the JSX is turned into HTML and returned to the browser.
But of course I'm not familiar with every HTML templating library out there, but I've used a few and I really love working with JSX.
Earlier quoted context omitted.
Cool, good to know. What makes JSX such a good templating engine?
It's personal preference of course, but imo JSX is just a very clean way of writing frontends. Easy composability, easy data bindings which don't have to be two-way if you don't want. My sense with many templating engines is they are trying to crowbar programming functionality into HTML and always comes across clunky. It's usually a separate language from your server code entirely. Inline If statements and For Loops…
https://pagetemplates.readthedocs.io/en/latest/tal.html
These days I reach for Chameleon, another Python implementation:
https://chameleon.readthedocs.io/
I'm aware of at least five implementations for JS: template-tal, jstal, Distal, DomTal, ZPT-JS.
Earlier quoted context omitted.
It's personal preference of course, but imo JSX is just a very clean way of writing frontends. Easy composability, easy data bindings which don't have to be two-way if you don't want. My sense with many templating engines is they are trying to crowbar programming functionality into HTML and always comes across clunky. It's usually a separate language from your server code entirely. Inline If statements and For Loops…
My own favorite syntax(es) are TAL, TALES, and METAL (Template Attribute Language, TAL Expression Syntax, and Macro Expansion TAL). There are many implementations in various languages. The OG implementation was in Python as part of the Zope: https://pagetemplates.readthedocs.io/en/latest/tal.html These days I reach for Chameleon, another Python implementation: https://chameleon.readthedocs.io/ I'm aware of at least f…
PHP => Laravel/Symfony, Python => Django, Ruby => Rails You just can't go wrong with one of these 3 above. Boring. Tested. Server side web pages All the 3 above also have great communities, support, documentation and above all, plenty of experienced talent over the years. These are battle tested.
Could you recommend a new one to learn for someone who only knows spring boot? I can pick up any language quickly. The main thing I'd be looking for is good resources/blogs to learn the framework quickly from.