Very glad someone who is entrenched in the Ember community could provide the same necessities and insight to the same problems I was able to fix for Backbone developers. Tools like Brunch and Yeoman attempt to accomodate all libraries, which is an admirable goal, but I feel like developers who write applications in a specific framework every day are more keen on providing necessary defaults.
Perhaps soon we'll have some agreed upon common ground: (CommonJS modules, template pre-compilation, image optimizations, source maps, etc.) and leave the scaffolding and defaults to specific projects that address the needs and desires for developers using those frameworks.
4 comments
[ 2.4 ms ] story [ 17.1 ms ] threadVery glad someone who is entrenched in the Ember community could provide the same necessities and insight to the same problems I was able to fix for Backbone developers. Tools like Brunch and Yeoman attempt to accomodate all libraries, which is an admirable goal, but I feel like developers who write applications in a specific framework every day are more keen on providing necessary defaults.
Perhaps soon we'll have some agreed upon common ground: (CommonJS modules, template pre-compilation, image optimizations, source maps, etc.) and leave the scaffolding and defaults to specific projects that address the needs and desires for developers using those frameworks.