Ryan, I believe you mentioned somewhere that Marko is good for content sites/blogs/eCommerce while React is more suited for web apps. I'm starting work on a web app soon and I wanted to see if you still feel that way. Is SolidJS an alternative to React for more web-app-focused apps, or is Marko also a contender in this space now?
I'd like to make sure the app is offline-first (PWA) so that the experience is good on mobile and desktop.
I'd say the statement is still true. Nothing prevents Marko to be used this way, but Solid definitely more on the React side. And a lot more consideration given to SPA concerns. You could make a SPA with Marko, but there is less available there because of the MPA focus. The reason I mentioned Marko is good for content sites/blogs/eCommerce is because it is so good at those. Like unquestionably good. For the app side there are more options. I think on pure technology Solid one of the better ones(I would, wouldn't I?), but there are more to these sort of decisions that technology.
I'd like to make sure the app is offline-first (PWA)
A PWA doesn't have to be a SPA.
That's a misconception that came about when Google inadvertently coupled PWA with the App Shell Model. With ServiceWorker, and Cache (and perhaps IndexedDB) it can make sense to fashion a PWA as a MPA.
Ryan, I believe you mentioned somewhere that Marko is good for content sites/blogs/eCommerce while React is more suited for web apps. I'm starting work on a web app soon and I wanted to see if you still feel that way. Is SolidJS an alternative to React for more web-app-focused apps, or is Marko also a contender in this space now?
I'd like to make sure the app is offline-first (PWA) so that the experience is good on mobile and desktop.
I'd say the statement is still true. Nothing prevents Marko to be used this way, but Solid definitely more on the React side. And a lot more consideration given to SPA concerns. You could make a SPA with Marko, but there is less available there because of the MPA focus. The reason I mentioned Marko is good for content sites/blogs/eCommerce is because it is so good at those. Like unquestionably good. For the app side there are more options. I think on pure technology Solid one of the better ones(I would, wouldn't I?), but there are more to these sort of decisions that technology.
A PWA doesn't have to be a SPA.
That's a misconception that came about when Google inadvertently coupled PWA with the App Shell Model. With ServiceWorker, and Cache (and perhaps IndexedDB) it can make sense to fashion a PWA as a MPA.
Google Codelabs
So "offline PWA" doesn't really dictate the choice of the UI framework - some have been built with jQuery.
Why Progressive Web Applications Are Not Single Page Applications
In his 2018 talk Beyond SPAs: alternative architectures for your PWA Jeff Posnick presented a sample MPA PWA that uses lit for the UI.