Live data from Hacker News

2 years with Angular

fse.guru

211–216 of 216 posts

Re: 2 years with Angular

#211
post #200
post #146

Earlier quoted context omitted.

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…

Whoops you're absolutely right! I think I had taken this early adoption by doubleclick inside of Google http://angularjs.blogspot.com/2012/06/doubleclick-super-powe... as my source of info.

In an interview last year one of the founders mentioned that angular was made for creating form based apps. That is its strong suit, which is fine, but it has been stretched so far now.

Re: 2 years with Angular

#213
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…

Amen. Look back 10 years ago and we were having the exact same discussions about mod_perl, php, and java servlets. Nothing has really changed except perhaps for an increase in the number of regurgitated comparisons.

Except that php won. As weird as that seems. CGI.pm was removed from the core Perl distro this year. React learned a lot from php/xhp and is easier to use because of it.

Re: 2 years with Angular

#214
post #204

Earlier quoted context omitted.

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.

> you have to wrap all your data structures into the mithril collections/models so that they can communicate with the views. Only when you need bidirectional bindings, and you're not forced to use the builtin `m.prop()` helpers, you can easily whip your own if they don't work for your use case. See my last link for an example.

Isn't that the whole point though? I mean, discarding existing DOM with forms is a horrible experience.

Re: 2 years with Angular

#215

Earlier quoted context omitted.

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.

Just saw this - thanks for the info, very interesting!

Re: 2 years with Angular

#216
I really think that the bigger the app gets the smaller the framework should be. If it lacks functionality, it should be possible to easily add it using the frameworks core functionality.

IMHO in general the core functionality of a clientside framework is to provide a way of structuring the app and allow for communication between logical units that are nestable and modularized.

If a basic framework does that, and only that, it should be bulletproof. I admit, it took me 10 years to rethink and recode this over and over - and there is no end in sight.

I love this discussion, it reflects much of my thoughts about the issue.

Post reply on HN