Live data from Hacker News

2 years with Angular

fse.guru

191–200 of 216 posts

Re: 2 years with Angular

#191

Earlier quoted context omitted.

I knew someone who consulted a large bank not to use Angular for financial apps. They were insistent to use Angular until he finally showed them a fairly typical requirement of an app like that in angular: 5 tables with 100 rows and columns. It literally crawled when running on a Dell Workstation laptop. It is kind of nuts that angular is big.

I don't understand this. Were they using angular grid? Because I work on an app that has tables with ng-repeat attributes and it is insanely fast. It loads hundreds or thousands of rows into about 200 columns that are separated by tabs. The client side filter searches are instant.

looks like they've used ng-include in each cell.

Re: 2 years with Angular

#192
post #170
post #106

I'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…

The irony is angular was going to be the framework I learned the next time I had free time. Now I am not so sure.

Re: 2 years with Angular

#193
post #99
post #69

Earlier 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.

I don't think its a big deal. I use ClojureScirpt and Om, but often read React sample code (sepecially the React-bootstrap snippets). JSX doesn't map to what my ClojureScript code looks like at all, and neither does the pure JS React code, but I don't find it hard to read or understand at all and its fairly easy to learn what I need from it.

Re: 2 years with Angular

#194
I totally disagree.

I've spent the last year working on a complex and widely-used site that is built with Angular. It is maintainable, performant, has a smooth UX, and is mobile-friendly.

I'm usually extremely cautious about relying on frameworks for long projects, because easy setup doesn't matter after you've been working on something for a year. In our case, using Angular was the best choice we could have made. I would absolutely not replace Angular with my own in-house MVC, even if you gave me a year to develop it.

-The testing tools are some of the best I've used, and hugely contribute to making the app easier to maintain

-It's not as much of a framework as a set of tools. Angular mostly stays out of the way and mostly allows us to structure code to match our needs

-You absolutely need to have top-notch developers, and ideally someone experienced enough to mentor people on the team who are new to Angular. There are a lot of JS developers who are former Flash designers who learned how to use a few jQuery plugins. If they don't know the fundamentals of programming really well, they will make a huge mess of the project.

-We've definitely run into performance problems, but they're manageable. We've had to write code that bypasses Angular's digest cycle, but it feels similar to writing a bit of inline assembler in a C++ program. I wouldn't stop using C++ because of that.

Re: 2 years with Angular

#195

Earlier quoted context omitted.

By this reasoning, functional programming is only the "method" in OOP. Surely that means OOP is a necessarily fuller abstraction? React gives you a powerful V that expresses things so intuitively that for most cases it eschews the help of a C or an M. That's a good thing when it's achievable.

It doesn't seem true to me that the "V" React gives you is so good that you don't need anything else. It does seem common (though not universal) to eschew MVC for React apps, but in most cases it is replaced with something like the Flux architecture, which is no more or less complexity than MVC, it's just different .

Even inside Facebook Flux isn't used everywhere; Yes, for heavier modelling, sure. But for most common cases you're very fine with using only js objects.

Re: 2 years with Angular

#196
I feel somewhat conflicted about this blog post. I can agree with what others are saying in the comments that all frameworks have there pitfalls. A lot of development is dealing with trade offs and your teams varying experience.

On the other hand, I agree with the author that there is a tipping point where a framework/tool becomes too much of a burden. Sure, we can all do it the "right way" but teams don't always have people with the experience to even know what the right way is.

We should think about the frameworks we use as tools. Make sure the tool is right for the problem and the team. Also, don't try to apply all your older experience to the new tool. Take time to learn about the thing you use.

Re: 2 years with Angular

#197
post #179

Earlier quoted context omitted.

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.

I've seen many people repeating it; but I don't know what it even means. It definitely is the V - since it renders the view. But it is also the C - a component encapsulates the view and view logic together. From within the component, you have lifecycle events: when the component is mounted for the first time, whenever it receives new properties, when it is unmounted etc. In any of these events, you can receive data f…

I think the point is a bit moot. Since it’s just JavaScript, you can put pretty much any logic in a React component just like you could also put any kind of logic in an PHP template or inside a view in iOS.

Re: 2 years with Angular

#198

I find the rise of Angular kind of baffling. Angular's scope system is exactly analogous to the scope system of a programming language. This is a solved problem! When you make a scope system, make it lexical, and require explicit declaration before use. If you're not making those choices, then at least acknowledge that these are the standard answers, with very clear advantages over other scoping systems, and explain…

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…

Regarding dirty-checking, this stackoverflow answer by Misko might help understand the reasoning behind it: http://stackoverflow.com/a/9693933/520129

Re: 2 years with Angular

#199
post #47

This post reminds me of these other two [0, 1] that ultimately lead Leo Horie to create Mithril [2], a tiny (5 KB down the line) but complete MVC framework that also eschews most of the criticism raised by the OP. The Mithril blog is also worth a look, it addresses a lot of concrete scenarios with recipies to solve common front end problems with the framework. For example, here's a post on asymetrical data binding [3…

That framework has its own problems, like you have to wrap all your data structures into the mithril collections/models so that they can communicate with the views.

Re: 2 years with Angular

#200
post #146
post #105

Earlier quoted context omitted.

1) Google was behind angular, Google has a huge marketing team, and there is a surreal amount of Google love in the developer community. 2) Angular was the first framework where you could take developers who didn't know JavaScript (or hated it for its worst parts / memories from the bad old days), but were used to learning frameworks (think Java people) and dealing with framework workarounds, and say, use this, you'l…

It is a DoubleClick invention that Google bought. They then attached "from Google" to the logo and it took off like a rocket.

> It is a DoubleClick invention that Google bought.

Not really.

It is the remnants of a failed web startup. They offered a freemium backend as a service, but it didn't take off.

http://web.archive.org/web/20091230110525/http://getangular....

http://web.archive.org/web/20100215054417/http://www.angular...

Then I believe that one of the founders/authors was hired by google, and...

> They then attached "from Google" to the logo and it took off like a rocket.

Yeah.

Post reply on HN