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

Angular 2 docs for ES6/7

github.com

Post reply on HN
Print view View original

21–30 of 62 posts

Re: Angular 2 docs for ES6/7

#21

Post by spdionis »

ralfn wrote: post #17
SamUK96 wrote: post #13

I've been learning AngularJS 2 for around 2 weeks now, and I see why they push use of Typescript. They always have. AngularJS 2 was designed from the start to be typed. To be object-orientated. At the least be object-inspired. It makes sense to be consistent. Using a non-typed and functional-structured language for a typed and object-orientated framework is pretty dumb in my eyes. To digress a little, AngularJS 2 has…

In your logic you equate statically typed and object oriented vs dynamically typed and functional. Object oriented programming is by origin (Smalltalk) dynamically typed. Class based programming languages (which we really shouldnt consider typical for oop) tend to borrow all their modern type features from functional programming languages. (Think polymorphism, generics, interfaces, etc.)

By 'dynamically typed and functional' I think he meant javascript.

Personally i wouldn't call javascript functional but...

Re: Angular 2 docs for ES6/7

#22

Post by mindw0rk »

DigitalSea wrote: post #18

It's the attitude of the Angular 2 team that makes me glad I decided to choose Aurelia instead. Nobody seems to realise that Angular 2 exists first and foremost to meet the needs of Google's internal Green Tea team and not the public. This is just one of many things that should make people think twice about using Angular 2. The fact the team seemingly take input from a select handful of "Google experts" to guide the…

Nobody say that you are not allowed to write in es5/es6. It's just docs that not going to be updated for es6

Re: Angular 2 docs for ES6/7

#23

Post by rubber_duck »

DigitalSea wrote: post #18

It's the attitude of the Angular 2 team that makes me glad I decided to choose Aurelia instead. Nobody seems to realise that Angular 2 exists first and foremost to meet the needs of Google's internal Green Tea team and not the public. This is just one of many things that should make people think twice about using Angular 2. The fact the team seemingly take input from a select handful of "Google experts" to guide the…

>Nobody seems to realise that Angular 2 exists first and foremost to meet the needs of Google's internal Green Tea team and not the public.

Isn't Google using Dart internally ? From what I've seen all their NG2 projects use the Dart version and their Material design component lib is Dart ?

So if what you were saying was true they would dump the TS/JS version and migrate the team to work on the Dart version 100% and not maintain two separate code bases (like they are now after the Dart/TS source split) and wouldn't even bother with the Material design for TS ?

Honestly I'm not even sure why Google is spending all this effort on the ng2 TS/JS as what I said above would make more business sense - I doubt that ng2 is making them any money if they aren't using it (I'm talking about the TS version).

Re: Angular 2 docs for ES6/7

#25

Post by rubber_duck »

ralfn wrote: post #17
SamUK96 wrote: post #13

I've been learning AngularJS 2 for around 2 weeks now, and I see why they push use of Typescript. They always have. AngularJS 2 was designed from the start to be typed. To be object-orientated. At the least be object-inspired. It makes sense to be consistent. Using a non-typed and functional-structured language for a typed and object-orientated framework is pretty dumb in my eyes. To digress a little, AngularJS 2 has…

In your logic you equate statically typed and object oriented vs dynamically typed and functional. Object oriented programming is by origin (Smalltalk) dynamically typed. Class based programming languages (which we really shouldnt consider typical for oop) tend to borrow all their modern type features from functional programming languages. (Think polymorphism, generics, interfaces, etc.)

>In your logic you equate statically typed and object oriented vs dynamically typed and functional.

I think OP is talking about the narrower scope of Angular 2 + TS vs React + JS

Re: Angular 2 docs for ES6/7

#26

Post by scarmig »

DigitalSea wrote: post #18

It's the attitude of the Angular 2 team that makes me glad I decided to choose Aurelia instead. Nobody seems to realise that Angular 2 exists first and foremost to meet the needs of Google's internal Green Tea team and not the public. This is just one of many things that should make people think twice about using Angular 2. The fact the team seemingly take input from a select handful of "Google experts" to guide the…

I love how any discussion about any Google product or news inevitably segues into a whine about a discontinued product from 2013.

Re: Angular 2 docs for ES6/7

#27

Post by stephenhuey »

DigitalSea wrote: post #18

It's the attitude of the Angular 2 team that makes me glad I decided to choose Aurelia instead. Nobody seems to realise that Angular 2 exists first and foremost to meet the needs of Google's internal Green Tea team and not the public. This is just one of many things that should make people think twice about using Angular 2. The fact the team seemingly take input from a select handful of "Google experts" to guide the…

While I'm not using TypeScript in my Aurelia application yet, I'm thinking about using it at least partially in the future. I also agree about the risk of Google not committing to Angular users. In response to that, the makers of Aurelia have asserted time and time again that they are trying to have a very different mindset and wholeheartedly cater to their users.

Re: Angular 2 docs for ES6/7

#28

Post by VeejayRampay »

aichi wrote: post #5

ES6 is next version of ES5 so whatever works for ES5 should work for ES6, no need for special DOC for that.

I would think that ES6 offers more affordances in the ways you can express ideas in code. The new docs would probably offer slightly different examples taking advantages of those affordances.

Re: Angular 2 docs for ES6/7

#29

Post by shados »

douche wrote: post #20
wiredearp wrote: post #7

Earlier quoted context omitted.

I am sure that the clientside developers in your company will come to realize their mistake when they see your interfaces and level of tooling.

The willfull resistance to embrace practices that make development easier, more efficient, and safer is baffling.

then just get the logical conclusion and use ReasonML/Elm/PureScript/whatever for the frontend instead.

Oh, you meant easier/more efficient/safer but only within the comfort zone...makes sense.

Re: Angular 2 docs for ES6/7

#30

Post by mamp »

anupshinde wrote: post #9

After switching to TypeScript, I am not sure whether I will ever go back to JavaScript (after so many years of using JS). I don't use or like Angular2 - but I use React with TypeScript. Even if we could use ES6 JavaScript in the browser, transpilation isn't going away completely because we need HTML, uglification, vendor-libs, etc to be brought in together before deploying to production. WARNING: If you are starting…

React + Flow is great also.
Post reply on HN