I stumbled across this project while checking out some new web technologies.
My initial impressions:
Very interesting concept, and what a nice editor. Also the integration with Github is really good. I started doing the To-do List tutorial. It is very easy indeed to get started. But it seems that looks can be deceiving. My first try to load my generated html-page with one H1 and a button wasn't an immediate success. I was sure I was doing something wrong because there was no rendering, even after several seconds. After a couple of refreshes I picked up Chrome Dev console and noticed that it was doing 160 request, 1.8 MB, and loaded in over 8 seconds. With local caching enabled: 35 kb, but still 6 seconds to load the page. (page load: 895 ms, DOMContentLoaded: 586 ms, rest of the time was network latency). I'm using an i7 with 4 cores, 16 GB RAM, 100 Mbit/s fibre.
I do understand that your free webserver might not be the largest machine out there, and that optimizations can reduce this quite a bit. But still. This doesn't look right. You guys did a really nice job here, but it's just too heavy in the end, not really useful for any serious applications.
- on my way to becoming an anti-framework anarchist
oDev, thanks a lot for the feedback, but you know, the road to no-framework is paved with smaller projects, inevitably. It's not a viable solution... The performance issues you're reporting are indeed concerning and surprising, we'll be looking at it. The current backend may have had a role, but you should also know that Montage applications should be mopped before released. Mop stands for Montage optimizer, it's a tool that recombines js and html templates as little as one file, or more if desired. The mopped project also injects scripts tags vs our no-build developmemt require. If you could share the Montage Studio preview URL of the project you mention having issues, that's be great. What version of Chrome were you using at the time and what OS?