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

31–40 of 62 posts

Re: Angular 2 docs for ES6/7

#31

Post by ascorbic »

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 think you should allow developers to write using straight-up Javascript.

They do, just not ES6. "The examples of the docs are planned to be written in TS, ES5 and Dart". I tend to agree with their argument that if you're using ES6, why not just use TS.

Re: Angular 2 docs for ES6/7

#32

Post by mrspeaker »

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…

If you're going React I suggest starting out with (or at least checking out) Flow over Typescript. It's well integrated with the React ecosystem and has type soundness as a goal.

Re: Angular 2 docs for ES6/7

#33

Post by ungzd »

ralfn wrote: post #15
ungzd wrote: post #11

Another sign that it's designed for enterprise Java camp: old Angular was very popular in such shops because of IoC and service factories. Now it requires java-like language on top of javascript, with type system designed primarily for autocomplete in IDE to work (even unlike Java in which type system is primarily intended to make runtime do less computations).

That's a common misconception about the JVM. Although the language features allow type-erasure, the JVM actually stores the types with the data and uses tracing for optimization. This keeps the compiler output smaller and allows classes to be compiled independently.

Still it doesn't have to check overloaded arithmetic operators each time and to look up class instance properties in hash table.

Re: Angular 2 docs for ES6/7

#34

Post by abalashov »

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…

Angular 2 strikes me as a manifestation of the inevitable tendency of all perfectly good frameworks to, just as they reach a likeable maturity, suddenly explode into a morbidly obese, suffocatingly bureaucratic J2EE-type Mother of All Frameworks, because merely working well and serving a purpose just isn't good enough.

Re: Angular 2 docs for ES6/7

#36

Post by nkw »

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…

> Routing in AngularJS 2. > It is bad.

I'm curious what you don't like about the Angular2 router. Since router 3.0 (agreed there were some false starts) I've found it to be a pleasure to work with.

Re: Angular 2 docs for ES6/7

#37

Post by egeozcan »

scarmig wrote: post #26
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.

> segues into a whine about a discontinued product from 2013

I see this happening too often but I don't see how that happened in the parent comment though.

Re: Angular 2 docs for ES6/7

#38

Post by Kudos »

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…

What's Green Tea team and why is Angular tailored for them?

Re: Angular 2 docs for ES6/7

#39

Post by mholmes680 »

stephenhuey wrote: post #27
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.

So I never heard of Aurelia, but now I've watched their video and explored the website. Looks cool, but... Google:Angular :: BlueSpire:Aurelia, no? So I'm betting on a small company surviving, vs Google at a whim killing off a thing they probably won't kill off unless they make a whole new v3 that is not related to v2 ?

What am i missing?

Re: Angular 2 docs for ES6/7

#40

Post by douche »

shados wrote: post #29
douche wrote: post #20

Earlier quoted context omitted.

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.

Baby steps, baby steps. It's a process.
Post reply on HN