✨ HTML Reimagined 🔬 Fine-grained Bundling 🚿 Streaming Render 🛠️ Targeted Compilation @ebay & the @openjsf

Joined February 2015
Learn about the future of Marko in our ViteConf talk! We're up next, live in 30 minutes 👀 viteconf.org/live
4
14
356
Could it be that every reason to reach for a SPA got fixed elsewhere since 2012? * SSR for weight * Routers for URLs * Paint holding for the white flash SPAs look a lot like the thing they tried to replaced. Hear from Luca LaValva (Marko) if the distinction still makes sense. @ViteConf, today 14:00 UTC viteconf.org
4
1
17
2,167
I can’t digest why Marko.js didn’t win. It’s sad that most web devs don’t really know how the web works. They just go with whatever is hype-driven. Marko was never optimized for hype. Whenever I look into resumability, it’s always Marko for me, and Qwik comes second. Try Marko. It’s a compiled option for any server-driven web architecture. And Ryan used to be on the Marko core team. You know him, right? He does pure OSS. Solid is generational ❤️ Don’t just stick to React, Next.js, or TanStack. Modern OOO streaming is basically the upstream of old-school Marko-era ideas. Marko was already doing async fragments and streaming back in the early 2010s. React mostly brought those ideas into a component-level programming model. Go with the least popular frameworks sometimes. That’s where the real home of the web lives. ex : Backbone, Knockout, Ember. I love all of them. Just don’t stick to one framework.
9
3
62
3,144
Marko retweeted
And we've made friends with the front of the JS framework benchmark 🏎️
3
6
34
1,296
Hardening & development continues! More news about persisted pages later this month
1
3
214
And we've made friends with the front of the JS framework benchmark 🏎️
3
6
34
1,296