So if not Angular then... what? If I wanted to do a single page app with REST backend (little to no db access), what would you recommend?
2 years with Angular
161–170 of 216 posts
Re: 2 years with Angular
#162Sorry, did I miss the part where the author explained the "right (tm)" way to do things these days? Seriously though, I've used Angular just as long as the author and for the most part I wholeheartedly agree with the complaints (and I have complained myself for some time). However, what is the "better" way? People keep throwing out things like React, but React solves much less for app developers. Also, that answer do…
Try vue.js. Same general idea as angular, way less bs. However, the author did just get hired by meteor, so that is something to consider.
Re: 2 years with Angular
#163I work at Google, and have been using AngularJS in different projects for about three years. The OP raises a couple of good points (in particular his "The Bad Parts" are mostly valid), but I cannot understand some others, nor do I share his take away. AngularJS is not a silver bullet or panacea. It has bad parts such as the directives API (making it hard to create reusable components), the global namespacing in the i…
This is in an established corp (best practices, standards, workflows etc) - you could build things out of mud and they would still hold. Doesn't say much for/against this particular framework..
Re: 2 years with Angular
#164Angular is a result of the over-engineering that is endemic to web development right now. Programmers are taking strategies designed by Google and Facebook and places that actually need the high level of conventions prescribed by software like Angular and applying it to their personal blog, their half-done only on github "startup," etc.
JavaScript isn't really a good place to adopt convention - you're dealing in a mixed-code environment almost from the start, speed is constantly an issue if you're doing something complex, and there's no such thing as "one size fits all."
I've looked at almost every JavaScript framework out there, and they really don't offer much more than what you would get out of a very lightweight jQuery (or your library of choice) abstraction. I want very much to find something that is as useful as the programming friction it introduces, but I haven't really found anything that meets that criteria yet. React seems to be very good at face value, but in general it isn't saving you nearly the amount of code that you might hope it does. Ember is probably the best at this, but it has its own tradeoffs (namely speed).
Re: 2 years with Angular
#165You know, I'm just going to say it: Angular is the Rails of Javascript. That probably sounds like a derogation. But behold: I offer nuance! They're both big and powerful, and capable of rewarding dedicated study with enormous power. Thus they develop a devoted following whose members often do things lesser mortals find little short of wizardry. They're also both built to be friendly and welcoming to the newcomer, and…
My opinion of Angular is now that it's basically the equivalent of PHP (if we're comparing it to other languages.) PHP is super easy to get started with and is magical and with enough forethought and planning, proves to be a serviceable language suitable for small projects. However, if you don't draw lines in the sand for yourself and watch performance very carefully as you scale, your app will suck. For reasons of m…
Comparing Angular with PHP doesn't strike me as entirely fair; Angular, whatever else one might say about it, has a high degree of conceptual consistency in its internals, whereas PHP, for all that it's improved over the past few years, remains an utter farrago and likely always will. Comparing Angular with Laravel might be more reasonable, but my lack of knowledge of the latter framework forbids me from commenting further on the comparison.
Re: 2 years with Angular
#166While most of the arguments presented in this article are somewhat valid but I hope with the release of Angular 2.0 majority of the issues will be addressed (though does it make sense to make such drastic changes in the upcoming is another debate and already taken care of at: https://news.ycombinator.com/item?id=8507632 ) I'm currently working on a comparatively large webapp built in Angular and it was after about 7…
Why look forward to angular 2.0? I mean, it's a completely different framework, so why are you anticipating it, and not any of the millions of other new frameworks coming out?
Re: 2 years with Angular
#167Earlier quoted context omitted.
You can use React without JSX. It is especially easy if you are using CoffeeScript which makes the syntax quite terse. I personally like JSX. It is more of a variant of Javascript that lets us mix HTML into JS seamlessly. It was inspired from XHP ( https://www.facebook.com/notes/facebook-engineering/xhp-a-ne... ), a PHP extension developed and used by Facebook that lets PHP understand XML. I think that the cross-poll…
Sure,but you need to learn JSX to read code exemples around the web.So you cant really use React without knowing JSX. That's a subtle thing but important enough when you're working on big projects.
Sure, but if you can read HTML and you've read the above list of caveats: congratulations, you can now read JSX. The attributes are simply passed to children as props. There's really not much to it.
Re: 2 years with Angular
#168Earlier quoted context omitted.
Actually it depends more on the time of development and project specs. For now I'll probably choose ReactJS. If by the time Angular 2.0 is launched then I'll definitely give it a shot, it seems promising and is based on ECMA6 utilizing the new features provided by it will be a plus. IMO AngularJS can be scaled _IF_ used with caution, though I won't recommend it unless one has a good experience with its core.
But ReactJS isn't a full replacement for AngularJS (and I don't see why people apparently fail to make that distinction); React is just the V in MVC, Angular is / can be the rest.
There are a lot of routers, http abstractions etc. out there. What people mean is "use React, along with some of the readily available modular ecosystem that exists already"
Re: 2 years with Angular
#169Earlier quoted context omitted.
Angular's scope system is only weird because they picked the name 'scope'; more modern angular applications / usage drop that one and use the 'controller as x' syntax, where instead of assigning values to a $scope object, it's assigned to the controller itself via 'this'. It's still effectively the same, but you won't be confused with scope anymore. The dirty-checking loop is IMO a compromise they made because the ES…
There are many ways to check if a object has changed in JavaScript, Angular's version of it is probably however the worst approach. The fact that it loops its a fundamental flaw that can't be taken seriously. Its a hack and should have never passed code review. Diff the virtual DOM to determine the minimal amount of imperative real DOM operations needed. Why is this so hard to understand as the optimal solution? Heck…
I'm not very familiar with React or Angular's history, but wasn't the idea of diffing a virtual DOM something that React kind of came up with, after Angular had been around? Isn't your comment kind of unfair, because you have the advantage of hindsight?
Re: 2 years with Angular
#170I've actually never used any javascript framework. It is stuff like this that drives me away. If you pick any one framework, you get half of a crowd telling you that it sucks, and then a year later your version is now deprecated/replaced and you get to re-do everything again. I've attempted to avoid the whole web-app scene, but with the current job market, looks like one has to know one of these frameworks...
Angular got a lot of its popularity, I think, from people with a similar mentality as you. Since it had the Google stamp of approval, it was seen as being more stable. Unfortunately, this was not actually the case.
I say, be thankful for the flux currently underway, and realize that it will result in some really good tech when it's all sorted out. Until then, either get used to learning new things, or leave front end dev to the professionals.