Re:Grunt and RequireJS are out, it's all about Gulp and Brow...
by goldenkey on Monday February 03, 2014 @04:35AM
(#7169674)
The problem with the frameworks is the very definition of the word. Not every problem/process fits in the workable frame, and then you end up with a pentagon shaped framework with dingles off the end, and nobody knows what the hell you did except you. Better to just write straight prototype OOP and use a preprocessor thatll add KVO to accessors/modifiers if you really need events (which most apps do.)
Emscripten is good for that. And there are many languages that have KVO that will compile to JS using emscripten. Really, JS isn't ideal for large projects, and these frameworks are silly, because they're targeting this lowly base for UI when a better language with better standard libs could be used to do lots of the logic, ie. Clojure.
Re:Grunt and RequireJS are out, it's all about Gulp and Brow...
by lobotryas on Monday February 03, 2014 @05:09AM
(#7169771)
>We have over 400 complicated web app pages that need testing to make sure we haven't broken any edge cases.
Reading your comment I get the feeling the impression that testing these pages is time consuming and difficult.
What kind of QA automation do you have in place?
The learning curve is tough, the maintenance is tougher and the churn is terrible. It's a living hell on a large project. It makes me long for WPF or even Win32 where 20 years without significant reengineering is a good bet.
On the web, the basic DOM API is the most stable. Sacrificing convenience for maintenance these days is what I'm for. Screw the frameworks.