Hacker News new | ask | show | jobs
by GnarlyWhale 3546 days ago
For the record, you don't need to use Typescript for Angular 2, you can just use regular JS (or Dart for that matter). The documentation is definitely biased toward Typescript at the moment, but I anticipate the situation improving as the framework matures.
2 comments

I used it (ng2) across 3 versions (beta 3-5 iirc), I used the flow type transformer via babel, which worked well enough. It'd be VERY difficult to do without some transpilation that allows the directive-style to be used.

For me, a lot of things in the templating seemed goofy, and had horrible, or no error messages when they didn't work right... I also still don't care for the DI system, though it's definitely a leap from ng1, I'd still prefer React over ng1 or ng2.

That's technically true, but realistically false.

Just like people used to say that you don't need to use JSX to write React.

What's the point of using a heavy duty, opinionated framework without embracing it completely? that's just bound to get you into a whole lot of hurt.

JSX and React's a little different though, because its downright easy to use without. I prefer JSX, but typing div(null, { style: 'foo' }) isn't much harder than <div style="foo" />, if a little uglier.

And then you have tons of libraries to make it nicer.

You broke my hope to start using React. JSX smells too much for me. But thanks for the info, anyway.
That's typical for people who didn't use React yet. In practice JSX is awesome.