Mako VS marko

https://www.makotemplates.org/ are also nice in that they have a return functionality which lets you exit templates early, which is nicer than big if/else statements in Jinja

At least in Python, that's kinda what https://www.makotemplates.org is. Although if you're just using a subset of PHP suitable for templating, it's not really clear to me what benefit there is to PHP syntax versus, say, Jinja2 syntax.

Mako already exists - https://www.makotemplates.org/. Nothing says you can't use the same name, but it will mean you won't be able to publish to pypi and your searchability will be bad

Mako is also a fairly popular python template library.

https://www.makotemplates.org/

My current tech stack is: Python3 with Mako and CherryPy. NGINX as a reverse proxy

SolidJS and Tauri form another potent combination for creating performant, lightweight, and secure experiences. SolidJS is a reactive UI library that is similar to Svelte in the way it compiles away reactivity and updates the DOM directly, but it also incorporates a fine-grained reactivity system reminiscent of libraries like Marko, Knockout, and MobX.

Marko is a huge leap in the right direction. It has streaming, partial hydration, a compiler that optimizes your output, and a small runtime. I’ve also heard through the grapevine that Marko V6 also adds resumability to the framework as well.

Nevertheless, the future of JS frameworks is exciting. As we’ve seen from the data, Astro is doing some things right alongside Qwik. However, more noteworthy frameworks such as Marko and Solid are also paving the path forward with some similar traits and better performance benchmarks. We’ve come back full circle in web development - from PHP/Rails to SPAs and now back to SSR. Maybe we just need to break the cycle.

If you want more, take a look on Marko, fresh, qwik or pug. Dind't tested yet but they look like same as Nunjucks.