3 ms·
I'm glad you brought up ember! I found it very confusing (and I have 5 years of ruby). I don't know what kind of approach I need for success there. I met peopl
by kristopolous 12y ago
I'm glad you brought up ember! I found it very confusing (and I have 5 years of ruby). I don't know what kind of approach I need for success there.
I met people who had only been programming under a year who were more successful with it ... and I have been doing Javascript since the 90s.
I wish I could unlearn all the things that create this mental blockage for me ... but I've been unable to overcome them. I don't know what to do - I feel like I'm missing out on a pretty lively movement.
I feel like I need to approach ember, angular et al as if "ok pretend that this isn't javascript. Pretend that it's something new." Because honestly they don't treat the language like the scheme-self hybrid I've become so familiar with.[1]
I think that approach will help, but I just don't have the discipline to be successful at it.
----
1. It's like with C++ how there's basically two kinds of devs ... the C-programmer who discovered some nifty organizational techniques, and then the C++ programmer. The second C++ programmer writes code that the other one finds very odd and confusing and the first one doesn't understand why anyone would go through all that trouble to do something that ought to be so simple, in her mind.
- afandian 12y agoI had a good go at Angular. I felt like it as a decent framework with interesting concepts. I built an app with it. Next project I thought I'd try Ember. It's very much my way or the highway. Huge amounts stuff learn. Not only concepts, but all those conventions. Very narrowly scoped models to which the whole world will conform (it doesn't, not without tying yourself in knots). The same thing that really puts me off Rails. I ditched Ember for the project and now I'm using React which I picked up in an hour and it's brilliant. YMMV. But I can't stand arrogance, and, to my mind, Ember drips with it. That includes renaming things that already have names.
- kristopolous 12y agoOne thing that many of these techs do is take one primitive, such as a function, and then call it half a dozen different things - making it look like there's a difference. I understand the goals of such an exercise, but I'm not convinced that it leads to quicker to deploy, easier to maintain, simpler to modify software. I think they must have different goals in mind when they write code - a lot of people clearly love the stuff. I just don't know what these goals are.