marko VS EJS

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.

Templating language - ejs

Its Github repository is https://github.com/mde/ejs and it Complies with the Express view system but along with pros there are some cons of EJS like it is very difficult to read its code, especially for designers and HTML people who don't focus on Backend languages and one more con is that it has no support for block by default.

With our Yugabyte database setup, let’s install the dependencies for our application. Install typeorm,pg, and ejs with the command below:

We need a frontend client to interact with authorization server. For this purpose we are going to use koa and EJS in combination. EJS is a template engine. It gives us the ability to write HTML files with more flexibility.

ejs to generate HTML template views

EJS: https://github.com/mde/ejs

You can use striate, a superset of ejs, to control which code gets generated within the files. The answers given to the prompts in yogini.json are available as variables within the scope of your template files.