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

Angular JS Kinda Sucks

okmaya.com

Post reply on HN
Print view View original

41–50 of 66 posts

Re: Angular JS Kinda Sucks

#41

Post by chrisfarms »

blueskin_ wrote: post #35

Anything that forces users to have javascript on sucks, by definition. It's exactly the same as the all-flash or flash-heavy sites of the early 2000s and I can't wait until javascript-only sites are consigned to the same dustbin of "why did we ever think this was a good idea?". Edit: It also breaks search engine indexing.

That may be true if your site is an article repository (blog, news etc) where the primary purpose is consuming text. If I'm on your site to read, then I certainly don't want to be "interacting" with the page.

But the browser is the new OS, complex applications are written for the web as a platform/runtime and this is not a bad thing. This is where Angular can help. It's not built to help you show/hide a few dom elements, it there to give you a powerful structure for developing web applications.

Re: Angular JS Kinda Sucks

#42

Post by [deleted] »

weavie wrote: post #27

I agree the documentation does suck. But there are several good books out now that explain things well. Get a book, read it, understand it, spend some time working with it. Then compare Angular to JQuery, I bet a lot of your 'its complicated' complains will have disappeared..

[deleted]

Re: Angular JS Kinda Sucks

#43

Post by prottmann »

binocarlos wrote: post #40
prottmann wrote: post #32

Earlier quoted context omitted.

But he write what most of the developers misunderstood. Many people use Angular for jobs, that will be easier and faster done with a simple jQuery. "Get the job done" got replaced with "its cool to use xyz".

I dunno - since I properly learned me some angular - I've been bashing through jobs like no tomorrow. Each time I've thought 'there has to be more to do than that'. If I were doing JQueries - there would be an entire stack of event driven DOM updates still to code.

For that you can use a simple library like http://www.ractivejs.org/

But it depends on the complexity and size of a project and how many developers are involved. I prefer frameworks too, but for a small WebApp, it is overkill to use frameworks like angular/backbone/whatever.

Re: Angular JS Kinda Sucks

#44

Post by kelmop »

I agree, if you are web designer and you only made some simple effects etc. etc. you should use jquery or plain js.

but if you are software developer etc. and you are creating a web-application you should angular or some other beefier framework, backbone/knockout/ember/whatnot.. or you can just re-invet the wheel

Re: Angular JS Kinda Sucks

#45

Post by Mimu »

Don't think he's serious. I mean why anyone that want to make a valid point would compare the speed of development between a jQuery expert and a person that know nothing about Angular? Not bad though, I would have pushed the troll a little bit further.

Re: Angular JS Kinda Sucks

#46

Post by finishingmove »

The quality of the documentation has admittedly gone down recently. Seems like people are just adding incoherent pieces of information to it as they go along and solve the problems they face. I really think it's the job of the core devs, to write, or at least edit the docs.

Ultimately, I don't think bad docs (which aren't actually all that bad...) are the reason newcomers find it difficult. After all, there's a bunch of resources by now, on various blogs, stackoverflow and even books were written on the subject. It's just that people are looking for quick wins and something they can start hacking on now, while completely ignoring the long-term benefits of adopting something as sturdy as Angular.

I've been working with Angular for about a year and a half now, and it's been very worthwhile going through the initial learning process.

Re: Angular JS Kinda Sucks

#47

Post by ux-app »

The comparison of jQ to Angular is apples to oranges, but I guess the author might be trying to make a argument for libraries vs frameworks.

In that sense I agree. After being burned multiple times by opaque, hard to debug frameworks, I'm now firmly in the libraries camp. I'd much rather piece together a number of small self-contained libraries that each do one thing and one thing only, and glue it all together myself.

My experience with frameworks has always ended in frustration and disappointment. Sooner or later you will reach the limit of what the framework was designed to do and it's at that point that the true pain begins.

I used to be mesmerized by framework automagic now its an instant red flag for me.

Re: Angular JS Kinda Sucks

#48

Post by pestaa »

vincentperes wrote: post #36
blueskin_ wrote: post #35

Anything that forces users to have javascript on sucks, by definition. It's exactly the same as the all-flash or flash-heavy sites of the early 2000s and I can't wait until javascript-only sites are consigned to the same dustbin of "why did we ever think this was a good idea?". Edit: It also breaks search engine indexing.

why is that? almost all browsers support JS, it's like saying we shouldn't force users to have CSS!

Well, surprise, we shouldn't force users to have CSS!

http://webaim.org/techniques/css/

Re: Angular JS Kinda Sucks

#49

Post by rikkus »

Ok not sure if it's a joke, but anyway, this point is valid:

"Architect it how? Are there examples? Some nice examples would be of projects that are relevant to the outside world. Data manipulation?"

Without documentation or at least full examples of architecture, not just toy samples, it's difficult to justify spending time working out what a good architecture _would_ be, because it would take so long to figure this out.

I keep following tutorials, watching PluralSight videos, etc. but so far I haven't seen any example that's even close to showing a real world app with complex forms and validation, complex entities to store, retrieve and manipulate, how to manage large test suites, etc. etc.

Still I'm persisting in trying to get started with Angular as it really does look great!

Re: Angular JS Kinda Sucks

#50

Post by mattmanser »

This is like people saying why use jQuery or MooTools or prototype 7 or 8 years ago.

Within 5-10 years we'll be transitioning to a world where SPAs/native-like apps are the norm.

The way I see it at the moment is:

1. SPAs/native-like apps are really hard to do well still and the reserve of the coders with lots of skill/time to play

2. Javascript is still very hard to manage when writing anything non-trivial. Unfortunately, it's not getting better but actually becoming relatively worse when compared to the speed/innovation of other languages.

3. Browsers will carry on refusing to let us use any language but javascript[1] because 'standards'.

4. As javascript/the DOM are too unwieldy to write complex apps, we need the equivalent of jQuery for SPAs/native-like apps

5. Enter backbone, ember, angular, etc. They are our saviours against the mess of the w3c and javascript. They are presently in the early stages where jQuery/MooTools/prototype were in the mid-2000s

6. Anyone who doesn't get with the program, like this fella, will find themselves suddenly sorely lacking in a key skill almost overnight, as happened with jQuery

[1] Most shamefully Firefox, the ones who should have lead the charge 4 or 5 years ago to drop javascript as the one-true-way, will refuse to innovate past js. So much for 'free' or 'open'. Imagine if all Linux distributions suddenly conspired to only allow PHP 4 to be written. Or Windows only allowed you to write VB. It's such a bizarre situation we're in. The web is like the operating system of the internet but we're being denied the freedom to choose our preferred language.

Post reply on HN