Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

2 years with Angular

fse.guru

Post reply on HN
Print view View original

81–90 of 216 posts

Re: 2 years with Angular

#81

Post by cloakandswagger »

mattgreenrocks wrote: post #74
atirip wrote: post #40

Earlier quoted context omitted.

IMHO Good Thing is to have set of libraries and not a framework at all. Start with handcrafting all HTML,CSS with interactions you need. You HTML skeleton will depend greatly on what you want to achieve - like when one page changes to other and theres a ajax call between - where you put the wait screen: as separate, on old page, then wait, transit to new at once, then wait and so on. If that is done you know broadly…

Meta: digging the downvotes in lieu of actual discussion here. Stay classy.

The comment above yours is a giant, unbroken paragraph of dogma. I'd say it's worthy of downvotes.

Re: 2 years with Angular

#83

Post by Alex3917 »

cmdkeen wrote: post #73
hassanzaheer_ wrote: post #14

While 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…

Angular 2.0 seems to be a long ways off - to the point where the presenters wouldn't show actual code examples in their demos of it at ng-europe. It rather makes me worry it is going to be the Python 3000 release all over again in terms of how much is changing.

> It rather makes me worry it is going to be the Python 3000 release all over again in terms of how much is changing.

The underlying technology is changing so fast (ES6, web components, mobile web, etc.) that it's going to make upgrading an obvious choice even if it involves relearning a lot of stuff.

Re: 2 years with Angular

#84

Post by pandler »

dynjo wrote: post #54

We built a pretty complex app with Angular ( https://slimwiki.com ) and have had nothing but great experiences. The main issues are no guidelines about the right/wrong way to do things, it needs to be more opinionated.

Awesome! I was just looking for something like that.

Re: 2 years with Angular

#85

Post by cmdkeen »

oinksoft wrote: post #78
cmdkeen wrote: post #73

Earlier quoted context omitted.

Angular 2.0 seems to be a long ways off - to the point where the presenters wouldn't show actual code examples in their demos of it at ng-europe. It rather makes me worry it is going to be the Python 3000 release all over again in terms of how much is changing.

I've not gotten the same impression and expect Angular 2 to be out sooner than later. Here's a code example: https://github.com/angular/angular/blob/master/modules/examp... It looks like `master' is all Angular 2 and coming along well.

It's a rather empty project compared to 1.X at https://github.com/angular/angular.js

138 JS files v > 1000

Fingers crossed that isn't the level of Hello World required either in the world of 2.0 and AtScript.

Re: 2 years with Angular

#86

Post by [deleted] »

aaronem wrote: post #46

You 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…

[deleted]

Re: 2 years with Angular

#87

Post by Alex3917 »

dasil003 wrote: post #62
Alex3917 wrote: post #57

Earlier quoted context omitted.

- Everything you need to know about Angular is explained in ng-book or the like. Trying to learn the framework by reading blog posts isn't going to work. There's just too much to know, and it's impossible to understand what's really going on unless it's presented in a logical and comprehensive way. - Angular isn't designed to render large tables. Go with DataTables for jQuery instead, or if you don't need all the fea…

Where is the disclaimer about data binding limitations? Tabular views with hundreds or even thousands of rows aren't inherently uncommon or non-performant. It's easy to sit here and say "wrong tool", but this is a pretty significant weakness IMO.

There probably should be a disclaimer in the official docs somewhere, but if you Google for ngRepeat performance there are tons of discussions on this. It's also a perennial favorite topic for angular tech talks. There is also a lot of information on how to improve the performance if for some reason you really want to do this. That said, even if the performance were great right out of the box without using one-time bindings or tweaking the trackby parameter, it still wouldn't make sense to do large tables in angular because you don't have any of the other datatables functionality.

Re: 2 years with Angular

#88

Post by oinksoft »

jrochkind1 wrote: post #79
oinksoft wrote: post #59

I've been using Angular on-and-off in professional settings since 2012. Angular is a framework obsessed with testability that treats usability as an afterthought. That said I've found Angular to be more than flexible enough to meet the needs of your typical CRUD apps, and generally enjoy working with it. One thing I agree with the author about is the importance of expertise for a successful Angular project. Some spec…

You say: > That said I've found Angular to be more than flexible enough to meet the needs of your typical CRUD apps The OP says: > Are there any use cases where Angular shines? > * Building form-based "CRUD apps". So I guess you and the OP pretty much agree.

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 simply unhappy to be working in a framework not of his own design: "Create a metaframework based on angular, tailored SPECIFICALLY for your project needs and your team experience!" That's the one thing you shouldn't do if you want to reuse code between projects.

Re: 2 years with Angular

#89

Post by username__ »

I've been using Angular now for a year and half, and a year professionally. The only issues I've run into are pages with large data bindings. I would love if the Angular team could recommend a solution other than "don't do that." That answer is simply unacceptable in my opinion -- their silence on this topic has been very frustrating.

Re: 2 years with Angular

#90

Post by jchrome »

swombat wrote: post #49

This seems to be the summary of every tech flame war ever, and applies rather well here: A: I've used tech X in a lot of Y contexts, and I find it's not great. I will generalise slightly imply that tech X is not the panacea that it has been presented as. B: Yeah? Well, I've used tech X in a lot of Z contexts, and I find it works fine! You're wrong! You're using it wrong! Maybe you're not wrong in context Y, but for m…

I never understand an article that is only negative and never presents a viable alternative.

OK - So you think Angular is not good for "professional" work. Then what is? Present an alternative and compare and contrast them. Then we will tear it up and come to our own conclusions like the ruthless masses that we are.

Post reply on HN