we just presented brunch at the vienna javascript user group (viennajs.org).
we still need some input on good client side testing tools that would make sense to be integrated with a js framework. further we need to get rid of some rough edges and will focus on providing documentation and examples.
currently we would like to get feedback on the chosen toolchain and love to hear suggestions on how to improve their integration (we currently ship a file watcher, still need to add uglify support and different build targets - build.phonegap.com, chrome webstore, …)
thank you for your feedback. npm support was a big win for us since we tried to get the dependencies (especially on languages and package managers) simple.
we definitely will keep sass/scss in mind since it is very popular in the rails community. once the core components work well together we will look into customization (also for the templating component).
that said, I believe there is value in a recommended set of components to have consistent documentation, code examples and a straightforward getting-started experience. but for people who know what to do it should be easy to switch components (comparable to replacing activerecord in rails). easy things should be easy, hard things should be possible :)
we still need some input on good client side testing tools that would make sense to be integrated with a js framework. further we need to get rid of some rough edges and will focus on providing documentation and examples.
currently we would like to get feedback on the chosen toolchain and love to hear suggestions on how to improve their integration (we currently ship a file watcher, still need to add uglify support and different build targets - build.phonegap.com, chrome webstore, …)
cheers, tosh