At first glance, Marko might look like another compiler-based library like Svelte. But with Marko being built for high-performance eCommerce, where millisecond delays translate to a loss of sales, they've attacked the problem from a completely different angle. It is an SSR first library. Everything that was done right from inception has been to provide the most performant SSR experience.
The techniques that they have been using for over half a decade in production on one of the world's biggest eCommerce platforms are things that libraries like React or Vue are only just dipping their toes into. I'm talking streaming asynchronous SSR, progressive, and partial hydration. These are things Next, Nuxt, Sapper, Gatsby wish they could leverage.
Marko scores performance numbers several times higher than other isomorphic libraries. I even realized in one of the tests that while Inferno looked close, the only reason was that the implementation wasn't escaping certain properties (a security vulnerability). Marko is heads above the competition on server performance. It's not even remotely close.
And that's before considering Marko 5 is is just around the corner. They've completely revised their compiler/build chain and further increased the ability to support multiple renderers and render targets.
If we are on the topic of significant performance differences, my library SolidJS has drawn similar attention in the browser. This is an area where Marko hasn't really stood out. It trades blows with React's performance in the browser. But Marko's a compiler. There is no reason why we can't use the techniques I've worked on the past 5 years to make Marko a performance leader in both environments.
More so, the granular techniques I've been developing are a reactive analog to things like Concurrent Mode coming up from React. This is an area that is yet to be tapped to its full potential and Marko, already a champion of SSR, is uniquely positioned to provide one of the best isomorphic stories. Backed by a company clearly invested in its success, it has the capability to make it a reality.
Nothing changes. I've worked Solid completely in my own time for years, while working long hours for a startup. So that doesn't change. Solid is the effort of a few core contributors championing a reactively transparent, functional programming driven paradigm.
I think Solid has huge potential, and it will continue to grow organically. I've recently been making large strides into SSR, we've been building the website and new tooling, and the API has been stabilizing towards a 1.0 release. If anything I expect my work with Marko to broaden my perspective.
To me, this is more like backing both horses because Solid and Marko while in the same space represent 2 very different philosophical goals. Marko is more than a compiler. It's a language. Solid might use a compiler but it is very JS(or TS) forward. There are just certain types of things easier/harder to do with both approaches. Certain decisions where the right answer is the complete opposite for each.
You can expect some Marko specific content coming your way. I'm still learning it, so perhaps you can learn along with me.