3 ms·

Post is half finished, doesn't explain the interesting bit of why it's not wrong to be afraid. I also wonder if a small 2-week project is complicated enough to

Post is half finished, doesn't explain the interesting bit of why it's not wrong to be afraid. I also wonder if a small 2-week project is complicated enough to hit the usual idiosyncrasies of auto-magical frameworks that suddenly cause your code to contort into spaghetti. Usually it's things like "I have to get hold of the error, how do I do that? [Googling]. Oh, I can't. Bugger." or "I need to step in before it does this render to slightly tweak the data. How do I do that? [Googling]. Oh, I can't. Bugger.".

lerouxb 13y ago
I would like to see a follow-up post.
AdrianRossouw 13y ago
actually. the post is half finished. the next part is actually what I ended up thinking about angular on an intellectual level. The tone of the article veered so wildly that it felt right to stop there for now.
coldtea 13y ago
>Usually it's things like "I have to get hold of the error, how do I do that? [Googling]. Oh, I can't. Bugger." or "I need to step in before it does this render to slightly tweak the data. How do I do that? [Googling]. Oh, I can't. Bugger.". Well, if tons of big apps have been written in the framework, including by Google, then you shouldn't have problems, unless you're doing it wrong or your app is "unique".
- mildtrepidation 13y ago
  That sounds an awful lot like the scaling argument for PHP... just because a lot of people use something doesn't mean it does everything better than anything else. A project doesn't have to satisfy some snarky definition of "unique" to have different requirements and optimal paradigms than other projects. Also, the idea that if it doesn't work for you means you're doing it wrong is disingenuous at best. People have different ideas about what things a framework should or shouldn't do, and how it should or shouldn't do them. That doesn't make them wrong or you right.
- taeric 13y ago
  Agreed with the other poster on this. This is dangerously close to saying you should just use the framework that worked from years ago. I want to note that I actually agree with this mentality for a large portion of what is getting written. Many shops should spend less time building their apps than they do a framework to build all apps. Worse, many people should get a few more apps under their belts before they build another framework. It seems that the reason it is so easy to write todo lists in every framework is that is about as far as people are able to get them before they start hitting the dirty details.
  - taeric 13y ago
    I realize I have some typos up there. Apologies if that messed up any understanding.

lerouxb 13y ago

I would like to see a follow-up post.

AdrianRossouw 13y ago

actually. the post is half finished. the next part is actually what I ended up thinking about angular on an intellectual level. The tone of the article veered so wildly that it felt right to stop there for now.

coldtea 13y ago

>Usually it's things like "I have to get hold of the error, how do I do that? [Googling]. Oh, I can't. Bugger." or "I need to step in before it does this render to slightly tweak the data. How do I do that? [Googling]. Oh, I can't. Bugger.". Well, if tons of big apps have been written in the framework, including by Google, then you shouldn't have problems, unless you're doing it wrong or your app is "unique".

mildtrepidation 13y ago
That sounds an awful lot like the scaling argument for PHP... just because a lot of people use something doesn't mean it does everything better than anything else. A project doesn't have to satisfy some snarky definition of "unique" to have different requirements and optimal paradigms than other projects. Also, the idea that if it doesn't work for you means you're doing it wrong is disingenuous at best. People have different ideas about what things a framework should or shouldn't do, and how it should or shouldn't do them. That doesn't make them wrong or you right.
taeric 13y ago
Agreed with the other poster on this. This is dangerously close to saying you should just use the framework that worked from years ago. I want to note that I actually agree with this mentality for a large portion of what is getting written. Many shops should spend less time building their apps than they do a framework to build all apps. Worse, many people should get a few more apps under their belts before they build another framework. It seems that the reason it is so easy to write todo lists in every framework is that is about as far as people are able to get them before they start hitting the dirty details.
- taeric 13y ago
  I realize I have some typos up there. Apologies if that messed up any understanding.