Live data from Hacker News

2 years with Angular

fse.guru

131–140 of 216 posts

Re: 2 years with Angular

#131
post #34

"And whar are no-no factors for angular? Teams with varying experience. Projects, which are intended to grow. Lack of highly experienced frontend lead developer, who will look through the code all the time." I am greatly interested in learning what is the alternative that would be a 'yes-yes' in these bulletpoints.

This kind of distorts the issue here. The problem is not lack of highly skilled devs but rather the fact that you need highly skills devs to digest and maintain the level of complexity that Angular produces. I'm big believer on light frameworks that does least amount of abstractions and can get out of way if you need. You definitely want to avoid frameworks that claims to abstract everything away and especially those…

You don't need highly skilled devs, you need a disciplined team - which should review each other's members' code, stick to a style guide, research best practices, etc.

Like with every software development, actually.

Re: 2 years with Angular

#132
I am not a lover of angular, but the reason angular is so popular is because it gets the prototype out there.

So many things and places are just doing things "lean" and "iterating" so angular makes that easy.

I'm not sure anyone could tell me Angular isn't very productive and that it wouldn't be tempting to use it so you can get some fairly magical experiences for users and in demos.

Re: 2 years with Angular

#133

Earlier quoted context omitted.

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…

Clearly you like react, but react also doesn't do as much for you as Angular. It's "only the V in MVC."

Assuming MVC is the right choice for SPA development.

Re: 2 years with Angular

#134
I'm really disappointed that not only is this article on Hacker News, but it's currently at #1. The article contains almost no substance at all.

Angular's a controversial topic. So if you're going to write a long blog post picking a side, you really need to back it up with examples and offer alternatives. The six part "detail" posts aren't much better.

Re: 2 years with Angular

#135
Maybe I'm old fashioned but Angular just does too much for me. In fact many frontend frameworks simply do too much for me. I like to structure my web applications in a very minimal way.

I like having one layer that covers the UI display and UI events. This layer does nothing beyond styling, setting up the UI and using messages to pass back events in a generic way.

My business logic handles generic events. So say I have a button for saving, in my UI layer it registers the click event but then sends a generic message with a payload that is simply "Save". The business logic then saves it. This let's me drastically change any of the UI with zero affect on my business logic.

I wouldn't recommend it yet for production (very early) but I'm working on a small library that does much of this messaging and binding of messages directly to DOM objects. https://github.com/KrisSiegel/msngr.js

Re: 2 years with Angular

#136

Earlier quoted context omitted.

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…

Clearly you like react, but react also doesn't do as much for you as Angular. It's "only the V in MVC."

Even flux is a lot easier/faster than angular, of course doesn't came with everything angular comes, but is a nice step.

Re: 2 years with Angular

#137
post #134

I'm really disappointed that not only is this article on Hacker News, but it's currently at #1. The article contains almost no substance at all. Angular's a controversial topic. So if you're going to write a long blog post picking a side, you really need to back it up with examples and offer alternatives. The six part "detail" posts aren't much better.

I was hoping to read some examples and alternatives as well.. Presenting a problem without examples to back it up or a solution is just ranting. That's fine, but its just less productive.

Re: 2 years with Angular

#138

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…

And it's all so you can type `model.key = value` instead of `model.set(key, value)`. When I began using Angular I thought the latter was clunky and verbose. A few months in I would have loved to have that control back. And yes, the scoping was a nightmare. Like others here, the app I was working on hit a hard performance limit with the digest cycle. When the main table of our app got to a certain number of rows it st…

yeah, that's my experience too. I think it can be summed up with https://news.ycombinator.com/item?id=8652677

Re: 2 years with Angular

#139
post #96

I'm a big angularjs fan butI agree with all the points made by the OP. I will however stick with angularjs because frankly there is no better alternative. the selling points for me are: - Testing:Karma,Protractor,dependency injection are fundamental when working with a team.Everything is so easy to test,so easy to mock. - Speed:Sorry but there is no other framework that makes front-end dev faster.I can come up with v…

I plan on looking into react and mithril in the coming months

Re: 2 years with Angular

#140
post #103

Earlier quoted context omitted.

The author and I don't agree, except that Angular is not suitable for high-performance frontends (like games). The author suggests that Angular is only suitable for prototyping and that simply using the framework is technical debt. I particularly disagree with this statement: "Accept the fact that you will suffer in the future. The lowered expectations will help you stay happy sometimes." It seems like the author is…

> The author and I don't agree, except that Angular is not suitable for high-performance frontends (like games). Would you really use DOM/virtual DOM templates to make a game? it makes little sense. I dont believe any "MV*" framework is suitable for games,even if the game is DOM based. In a game,what you want is to make sure that at time T,the screen reflects the state of the game.Since you are manually pooling all s…

Actually that is the point :) The virtual DOM is equivalent to how you do write games. Declarative to imperative. React took its cues from how games are written. The renderer in react targets the DOM. React is a renderer.
Post reply on HN