major props to @ryanbethel eating wasm whole this past week porting enhance/ssr from #nodejs to basically every backend runtime ever.

looking at what various backend frameworks look like with a native #webcomponents view layer next. feels very webby not necessarily needing a JS runtime to build a frontend.

still very early but if you like the idea of replacing handlebars/mustache/thymeleaf/etc with web standard superpowers pls join the enhance.dev discord and chime in!

all this work is Apache-2.0 fwiw

#dotnet #java #php #ruby #python #rust #go

@brianleroux excellent news! Very exciting
@brianleroux js template literal is far superior to handlebars, ejs and most other tempalting languages imo. Also the ability to use custom elements (and tags in them) is more ergonomic than partials with "context" or something
@nrk9819 @brianleroux I too think this way. JS can be THE template language. Someone needs to ship a JS runtime like QuickJS engine bindings for popular languages (pure functions only, no network requests or filesystem access). Only problem is convincing other language devs to use it 🙈🙉
@munawwar @nrk9819 think they'll be stoked. Frontend really bifurcating teams in a not good way. This allows them to work together again.
@brianleroux @munawwar Other language devs who have used javascript at some point (which most web devs would do anyway) won't find much problem adopting js as templating language.
Some confusion might arise in distinguishing which part of js is rendering in the server and which part in the client
@brianleroux Very much looking forward to this, especially the Ruby implementation (I believe you referenced this earlier in the week?).

@jgarber yup! Here's the first prototype for Ruby

https://github.com/enhance-dev/enhance-ssr-ruby

GitHub - enhance-dev/enhance-ssr-ruby: Enhance SSR wrapper for Ruby

Enhance SSR wrapper for Ruby. Contribute to enhance-dev/enhance-ssr-ruby development by creating an account on GitHub.

GitHub