Marko VS stenciljs

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. - Source: dev.to / 9 months ago

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. - Source: dev.to / over 1 year ago

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. - Source: dev.to / over 1 year ago

And that is a similar feeling to the exploration we've been doing recently. Inspired equal parts from React Server Components and Island solutions like Marko and Astro, Solid has made it's first steps into Partial Hydration. - Source: dev.to / over 1 year ago

I first posted this a year and a half ago but it's been haunting me ever since. I keep revisiting it. In my dreams, and my day job. When working on Marko 6, we couldn't make a decision and decided to throw an error if one tried to read a value already updated in that cycle until we could make up our minds. - Source: dev.to / almost 2 years ago

First a disclosure: I never actually used Stencil, only played with it a bit locally in a hello-world project while writing this post. - Source: dev.to / 3 months ago

This is my main concern too. I don't understand why tools like this "pick a winner" with a specific framework instead of rendering to Web Components with a framework wrapper, or using something like Stencil[1] that can render to any framework. [1] https://stenciljs.com/. - Source: Hacker News / 4 months ago

I was recently able to sit down with some of the core members of Ionic, who also created Stencil a toolchain for building Design Systems and Progressive Web Apps. We talked at great length how typically companies are approaching Ionic from a Design Team and need help building components. As a developer I wanted to talk about the Web Components that are used within the Design System first. There was a decent amount... - Source: dev.to / 4 months ago

A web component should do ONE thing whereas a JS framework is a whole ecosystem. I made a video player web component that could take in various inputs, with a torrent file being the most complex of them. I was then able to port it to Vue/React with StencilJS [0] (although it was good to go without). Just drop the `https://stenciljs.com/. - Source: Hacker News / 5 months ago

Examples like this bug me. The React example is using a high level abstraction, the web component is directly using the API. A more accurate example would show how those React calls eventually boil down to document.createElement() I don’t think the Web Components API was meant to be used directly all the time. You can use a framework like StencilJS: https://stenciljs.com/. - Source: Hacker News / 9 months ago