11–20 of 21 posts
Glimmer looks awesome! Is it easy switch out handlebars for some other templating language?
It would be possible to support other languages more directly but they will tend to have a Handlebarsy flavor.
Glimmer looks awesome! Is it easy switch out handlebars for some other templating language?
The typical strategy is to design a language that compiles to Handlebars, e.g. http://emblemjs.com/ . It would be possible to support other languages more directly but they will tend to have a Handlebarsy flavor.
The web frontend world is crazy to a backend engineer. We have hard problems to solve too, but ours usually arise from well-understood problems, such as CAP theorem.
Earlier quoted context omitted.
The typical strategy is to design a language that compiles to Handlebars, e.g. http://emblemjs.com/ . It would be possible to support other languages more directly but they will tend to have a Handlebarsy flavor.
Write in a language that compiles to another language that itself compiles to markup... The web frontend world is crazy to a backend engineer. We have hard problems to solve too, but ours usually arise from well-understood problems, such as CAP theorem.
Anyways, you can't think of a single analogue for the emblem->handlebars example?
Earlier quoted context omitted.
The typical strategy is to design a language that compiles to Handlebars, e.g. http://emblemjs.com/ . It would be possible to support other languages more directly but they will tend to have a Handlebarsy flavor.
Write in a language that compiles to another language that itself compiles to markup... The web frontend world is crazy to a backend engineer. We have hard problems to solve too, but ours usually arise from well-understood problems, such as CAP theorem.
Earlier quoted context omitted.
Write in a language that compiles to another language that itself compiles to markup... The web frontend world is crazy to a backend engineer. We have hard problems to solve too, but ours usually arise from well-understood problems, such as CAP theorem.
It's crazy, sometimes web frontend is an echo chamber and you will get burned to the stake if you suggest doing anything simpler like just writing markup instead of a template language that translates to markup or a language that translates to that language that translates to markup. But it keeps people employed.
I was playing with glimmer.js, it feels like you can now "NPM your way to a full app" similar to the react eco system (if you're into that sorta thing).
Glimmer looks awesome! Is it easy switch out handlebars for some other templating language?
Earlier quoted context omitted.
Write in a language that compiles to another language that itself compiles to markup... The web frontend world is crazy to a backend engineer. We have hard problems to solve too, but ours usually arise from well-understood problems, such as CAP theorem.
It's somewhat jarring when people use "we" as if they're in a faction and they're the spokesperson of that faction. It's almost as bad as using "you guys" when faced with a single commenter. Anyways, you can't think of a single analogue for the emblem->handlebars example?
The only analog I can think of is statically typed SQL, which is in fact awesome.
I was playing with glimmer.js, it feels like you can now "NPM your way to a full app" similar to the react eco system (if you're into that sorta thing).
Our company's main application is built on top of ember 1.13. We've pushed off doing the upgrade and are leaning towards a move to react (all our mobile apps are done in RN). This might be a solution.