News for hackers. Stuff that matters.
Re:Learn AngularJS by randomdrake on Friday April 03, 2015 @12:20PM (#9316714)
> Your latter two points are odd since they are directed at Angular when they can be used to describe literally every frontend framework ever created.

I'm going to wager you haven't used, or are even aware of, "literally every frontend framework ever created," so we can agree you're being hyperbolic.

There are plenty of front end frameworks that utilize JS, HTML, and little else, without introducing "magic" or vocabulary that isn't applicable. I agree with the OP that Angular, in particular, has a great deal of vocabulary to learn and a lot of things that are only applicable in the Angular world. This is one of the main reasons that I, and many other folks, have not spent much time with it.

> The third point, in particular, is fundamentally what a framework does... it does some "magic" in the background to prevent you from HAVING to understand what's going on in the background.

Just because you don't take the time to understand what's going on the background, doesn't mean the framework is "preventing" you from you having to understand what's going on in the background. Au contraire, we hear stories over and over about how the "magic" introduced by a framework caused issues that actually required knowledge of what's going on in the background. This isn't the fault of the framework, or the goal of the framework, it's a fundamental part of software development.

For what it's worth, you're contradicting yourself by saying that "literally every framework ever created" applies to the OP's points, yet concede in your own point that "This does not necessarily translate from one framework to another, but can."

Frameworks get in your way only as much as you let them. The underlying technologies are still there.

> In the same way that learning Rails is not learning Ruby

Learning Rails is a perfectly fine way to be introduced to Ruby. You're learning syntax, constructs, philosophies, and you can break out of Rails and do things with Ruby at any time. I mean, what do you think you're writing Rails code in?

When learning to counter an argument, its best if you don't reiterate all of the points they made in some other way. You basically repeated all of their points, but I don't know if you're aware of it.

OP:

> This is Angular 1.x course. Angular 2, which is in the development right now, totally different.

Your point:

> Angular 2, an in-development long-term replacement for Angular 1 uses a very different approach to development, and will not translate well from 1.x to 2.x

OP:

> Much of the code abstracts away the DOM and some Javscript nuances, so don't expect learning a front-end framework to be the same as learning JS

Your point:

> Knowledge you learn from using Angular is unlikely to be applicable to any other client-side framework, as original creators invented many new terminology as well as their approach to many things is unique

OP:

> A lot of "magic" will prevent you from understanding what is really going on behind scene.

Your point:

> Much of the code abstracts away the DOM and some Javscript nuances, so don't expect learning a front-end framework to be the same as learning JS

I'd be interested to hear some valid counterpoints to the OP, since I tend to agree with them, but these don't appear to be them.

Re:Learn AngularJS by jhall1468 on Friday April 03, 2015 @02:31PM (#9317532)
> I'm going to wager you haven't used, or are even aware of, "literally every frontend framework ever created," so we can agree you're being hyperbolic.

The definition of a framework is abstraction. That's not hyperbole, that's fact. Frankly abstraction is programming since all programming languages are is an abstraction of machine code.

I'm not going to bother responding to you point to point, since I made valid counterpoints that you are hardly qualified to dictate as "not valid". The OP's post was opinionated half-truths designed to be pissy about Angular because that's what the Cool Kids(TM) do these days. It's gotten boring...

But hey, it won't be but a moment before more boring people have more boring complaints about React. Naivety has no end.

Re:Learn AngularJS by hippich on Friday April 03, 2015 @03:10PM (#9317762)
It is funny how you bring up another "Cool Kids" tech aka react.js, which is not even comparable to angular's scope in the first place. React at best is abstraction on view layer. And over engineered one, btw. If you want to have separate view layer with little binding boilerplate I personally recommend checking ractive.js (this is only view part! not a full framework, so don't try to compare it to angular)

Also it is not "Cool Kids" thing, it is personal observation how backwards some angular solutions are from working for a year on large team and large angular project and reading ALOT on all possible best practices.

Re:Learn AngularJS by jhall1468 on Friday April 03, 2015 @03:40PM (#9317937)
You miss the point. The Cool Kids comments was about how it's become fashionable to talk down about every new framework, UI library or whatever that becomes "big" because something 12 people use is OBVIOUSLY so much better.

To me much of this "this is better because this" is a lack of understanding your tool and/or personal bias leaking into the design decision for a piece of software.

I like Angular for what it is and using it on a year long project with a large team on a large project suggests that your decision makers did virtually NO research on what Angular excels at.

The problem (judging based on your small comment history on this thread) suggests that Angular isn't a problem, it's that EVERYTHING is over-engineered if it's not modular. And while I appreciate the modular approach having many benefits over non-modular frameworks, pretending that it's "The Only Way" is just as silly as pretending Angular is the answer for everything.

Re:Learn AngularJS by hippich on Friday April 03, 2015 @04:22PM (#9318247)
As i mentioned in other reply, you are wrong about reasons I dislike angular and why I can not recommend it to newcomers. Reason is - incorrect foundation of the whole framework, the rest is just consequences of it. Angular 2.x might change whole picture, but, again, it will be totally different beast. To the point that I am not sure it is reasonable to call it angular anymore, except for marketing purposes.

In fact if you spend a bit of time to see where from creator came, you understand why he did what he did. Also, if you had experience with server-side mvc frameworks you find all these concept very familiar. Also, if you built any type of complex client-side application, you will find, that server-side MVC concepts, based on single request = single response are not appropriate for long living client-side apps.

Sorry, there is just lack of perspective on your side and there is not much we can argue about.

Re:Learn AngularJS by ssmoot on Friday April 03, 2015 @02:59PM (#9317708)
> "The definition of a framework is abstraction."

It's actually "a basic structure". Which seems to work much better. Your definition would make this:

  trait Storage {
    def put(path: String)(bytes: TraversableOnce[Byte]): Unit

    def get(path: String): TraversableOnce[Byte]

    def rm(path: String): Unit
  }
A Framework. Which is obviously wrong.

Reusing a basic structure to short circuit some engineering tasks and hopefully accelerate the development of others. That's a Framework.

Re:Learn AngularJS by jhall1468 on Friday April 03, 2015 @03:32PM (#9317893)
You do understand the difference between oversimplification and being wrong, yes?

But the funny part:

"Reusing a basic structure to short circuit some engineering tasks"

So, you mean abstracting away some difficult task?