Ember.js is driving me crazy
softwaresimply.blogspot.com
Ember.js is driving me crazy
1–10 of 113 posts
Re: Ember.js is driving me crazy
#2Convention over configuration achieved with opaque magic can actually harm the dev process more than it helps.
Re: Ember.js is driving me crazy
#3Convention over configuration achieved with opaque magic can actually harm the dev process more than it helps.
Haskell: favor composition over configuration over convention.
Re: Ember.js is driving me crazy
#4I write a lot of ember.
It can, occasionally, be frustrating (for example run loop craziness), but in my opinion it's no more frustrating than working with any other stateful front end framework (WPF, backbone etc...).
Re: Ember.js is driving me crazy
#5Scala dev here who sometimes needs to do some JS (though haven't worked with ember). I feel your pain! Static typing and functional programming certainly make ones life easier once a project becomes bigger.
Anyway, for future reference, you may want to learn how to use the JS debugger (both Chrome and Firefox are quite good). You could have set a break/watchpoint on the variable 'foo'. Once it has changed, you can inspect the stack and would have found that the set('bar', ...) method was involved. Should be much quicker than printf-debugging...
Re: Ember.js is driving me crazy
#6Scala dev here who sometimes needs to do some JS (though haven't worked with ember). I feel your pain! Static typing and functional programming certainly make ones life easier once a project becomes bigger. Anyway, for future reference, you may want to learn how to use the JS debugger (both Chrome and Firefox are quite good). You could have set a break/watchpoint on the variable 'foo'. Once it has changed, you can in…
I use the debugger all the time. One problem is that when you're using Ember a lot of the call stack is cluttered with Ember internal calls, which obscures things. But even after I isolated the problem down to that line, the debugger still didn't help me fix the problem.
Re: Ember.js is driving me crazy
#7" but at some point I decided that the widget was no longer needed, so I commented out the widget's markup"
SOURCE CONTROL, DO YOU SPEAK IT?
In all seriousness, this is a major peeve of mine - the time that you're most confident that code can be deleted is when you're removing the pieces that depend on it. If the deletion really turns out to be wrong, you should be able to restore the code from source control. If you can't, stop using broken source control.
Leaving leftover dreck in your source files "just in case" is like stashing your leftover sandwich crumbs in your pocket at lunch. Clean up your mess!
Re: Ember.js is driving me crazy
#8Scala dev here who sometimes needs to do some JS (though haven't worked with ember). I feel your pain! Static typing and functional programming certainly make ones life easier once a project becomes bigger. Anyway, for future reference, you may want to learn how to use the JS debugger (both Chrome and Firefox are quite good). You could have set a break/watchpoint on the variable 'foo'. Once it has changed, you can in…
I use the debugger all the time. One problem is that when you're using Ember a lot of the call stack is cluttered with Ember internal calls, which obscures things. But even after I isolated the problem down to that line, the debugger still didn't help me fix the problem.
> a lot of the call stack is cluttered with Ember internal calls, which obscures things.
Your debugger should be able to display the corresponding .js file for each line in the call stack. Jump down the stack until you find your code.
Yes, it doesn't solve the problem (wanna talk about debugging freaking JSP or TinyMCE plugins? :p) but you won't
> spent the better part of a day trying to track down the source of this problem.
Re: Ember.js is driving me crazy
#9> The root of the problem is the system we were operating in: an impure programming language with weak dynamic typing.
Is it really fair to blame this on dynamic typing? Having setters with side effects seems like a design decision to me, and not one that is easily supported. I would be interested in hearing an explanation of why this behavior is javascript's fault.
Re: Ember.js is driving me crazy
#10Scala dev here who sometimes needs to do some JS (though haven't worked with ember). I feel your pain! Static typing and functional programming certainly make ones life easier once a project becomes bigger. Anyway, for future reference, you may want to learn how to use the JS debugger (both Chrome and Firefox are quite good). You could have set a break/watchpoint on the variable 'foo'. Once it has changed, you can in…
I use the debugger all the time. One problem is that when you're using Ember a lot of the call stack is cluttered with Ember internal calls, which obscures things. But even after I isolated the problem down to that line, the debugger still didn't help me fix the problem.
The Ember Chrome Extension (https://chrome.google.com/webstore/detail/ember-inspector/bm...) helps a lot.