11–20 of 66 posts
I don't really know JQuery either, so I can't say he is right or wrong with that criticism but currently Angular seems to be hyped up a lot in my opinion. (Or am I just too spoiled by the decent development tools we have backend?)
this guy describes himself as a "Programmer Extraordinaire" on linkedin
"Here’s an idea of pricing for you. I work on projects based on complexity. If you have 100 pages with simple text and images on it, the task is not complex. Just time consuming. So I consider that a complexity of 1, times 100 times. So, complexity is 100. If you have one page with one complex interactive form, with a calculator, that grabs prices from out there on The Web, then it’s a one page design, but complexity…
http://stackoverflow.com/questions/14994391/how-do-i-think-i...
If you want to compare, compare it with something like Backbone.
Secondarily, jQuery and angular.js don't serve the same use cases and are not directly comparable. Not all tools need to be general purpose. It's OK for a lathe to be a lathe, a drill press to be a drill press, a soldering iron to be a soldering iron. Complaining that a soldering iron makes a poor hammer just means you don't know how to use a soldering iron, it doesn't mean it's a poor tool.
What kind of spaghetti does this guy and his colleagues build where there is such strong back-end and front-end interdependency that the server-side code cares what the front-end is doing for DOM manipulation or client-side-MV* like this, I wonder.
Earlier quoted context omitted.
"Here’s an idea of pricing for you. I work on projects based on complexity. If you have 100 pages with simple text and images on it, the task is not complex. Just time consuming. So I consider that a complexity of 1, times 100 times. So, complexity is 100. If you have one page with one complex interactive form, with a calculator, that grabs prices from out there on The Web, then it’s a one page design, but complexity…
"Notice that we added a DOCTYPE to tell browsers what kind of document we have. We picked 4.01 Transitional because of its flexibility to allow deprecated elements, like ."
If you know PHP, you know that you shouldn't be doing it like that. He sounds like a novice. There's nothing wrong with that, but when looking at that kind of thing I would take an opinions as a grain of salt
To me this post boils down to "I already know jQuery, this isn't jQ, so WTF". Well, godspeed, you fancy bastard. I wouldn't use Angular for a small'ih average website where you want some minor JS-based UI functionality. But I found Angular much more suited than jQuery for big sites that are maintained by more than just one developer. You can look at some piece of HTML and you can tell from the list of directives what…
I think the distinction is more nuanced, Angular isn't intended for producing web sites, so much as web applications.