4 ms·
It's not possible to have a slower development build which does template->bytecode conversion on page load? The point I'm trying to make it, there's already a
by bluepnume 10y ago
It's not possible to have a slower development build which does template->bytecode conversion on page load?
The point I'm trying to make it, there's already a huge amount of churn around the vast amount build tooling needed to write any javascript these days. Part of making a framework with a low barrier to entry is having the build tooling stay out of your way until you're ready to deploy.
I get that's not necessarily Glimmer/Ember's philosophy, I just think it's a shame that using the framework from day 1 requires buying into all of the technology choices around ember-cli.
- okket 10y agoMinimising time to first render/interaction is on the list what is important for Glimmer. I don't see how this is compatible with moving the conversion engine to the client. (Not to mention that the app size zealots will eat you alive)
- bluepnume 10y agoYeah, that's essential in production. Totally agree. I'm mainly talking about the development experience for first-time users, or for people who just want to throw Glimmer onto one of their apps on localhost and play around with glimmer.Component. The thing that needs to be fast in those scenarios is the developer experience, not the app.
- okket 10y agoIf you want to play around, have a look at Ember Twiddle: https://ember-twiddle.com/ https://ember-twiddle.com/ (No Glimmer there yet, only full Ember, but you can get a feel for what it can do, how it is like, test a things out...)