eta (η) VS marko

ERDIA uses the ETA template engine to generate documentation. The reason for using a template engine is that it allows you to customize the documentation the way you want it. If you want to customize documentation that ERDIA generates run the following command.

Just stumbled on this: https://github.com/eta-dev/eta

Eta : a lightweight and blazing fast embedded JS templating engine that works inside Node, Deno, and the browser.

I've been using Eta: https://eta.js.org/

It doesn't do gzip or image optimization, but such features might be better suited as server middlewares separate from the template engine.

Haven’t used it yet, but Eta supports Deno: https://eta.js.org/

Eta is a very similar template engine to EJS. It's supposed to be faster, lighter, with async templates.

https://eta.js.org/

https://github.com/eta-dev/eta/

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.