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

Angular 4.0.0 Now Available

angularjs.blogspot.com

Post reply on HN
Print view View original

321–330 of 360 posts

Re: Angular 4.0.0 Now Available

#321

Post by smdz »

ssijak wrote: post #183

Hmm. I see that Angular is getting aaaaalot of hate here. I really tried to understand why but have not found really valid reasons, just preferences. I have used Angular 1.x a lot and have just tried Angular 2. It really enables me (somebody who comes from primarily strong backend dev experience) to work on frontend SPA apps productively and fast. It does not 'feel' heavyweight or that it gets in my way too much, but…

Angular 1 was great. It was first of its kind. And it was just a bit complex - but not too much.

Ng2 felt too different. Ng1 to Ng2 made me look outside and there was React gaining ground - perfect timing. In its original state React is so much simpler than Angular. But then React with just the basics can make you create bad code - that's what happened to me. React with best practices - is hard to digest.

So I went back to Ng2 - soon enough I was craving to go back to React. Suddenly I started hating Angular2 (but loved TypeScript).

I spent time learning React best practices - that require some patience. But one thing I brought on from Ng2 was TypeScript. TS makes you a lot more productive. Now React and TS is not a widely accepted combination - but its very productive as your app grows.

Re: Angular 4.0.0 Now Available

#322

Post by alttab »

wincy wrote: post #217
alttab wrote: post #212

Earlier quoted context omitted.

What's been your experience with browser-side debugging? The one thing that scares me about typescript is you end up debugging something you didn't write.

At least in Chrome it'll pick up the mappings and let you directly debug the typescript you wrote. Worst case the javascript isn't nearly as gnarly as you'd think.

But then you need to be good at Typescript, React, AND Javascript to build a feature. And that's not even considering databases, server middle ware, etc.

Re: Angular 4.0.0 Now Available

#323

Post by tomelders »

kapv89 wrote: post #306
tomelders wrote: post #297

Earlier quoted context omitted.

But why? If you're adding all of that to make Angular work the way you want it, what benefits are you actually getting from Angular?

Same question can be asked for react. FYI you can easily build decent sized apps in react without redux

Exactly. Thats my point.

Re: Angular 4.0.0 Now Available

#324

Post by jondubois »

leshow wrote: post #320
jondubois wrote: post #231

Earlier quoted context omitted.

I don't particularly like TypeScript. It slows me down because of several reasons: - Compile time means that it takes more time to debug anything. - The rigid interfaces mean that I need to spend more time researching how to use various modules/libraries (maybe code completion would offset this problem but this is only possible with a heavy IDE that has intellisense or similar - Not Atom). - When I want to test somet…

> - It requires more planning to do anything That's the idea. You think about what you're going to write in a strongly typed language rather than just throwing stuff at the wall hoping that something will stick. > - The rigid interfaces mean that I need to spend more time researching how to use various modules/libraries I don't understand this. In one case you have an API where the types of all the functions is avail…

>> - It requires more planning to do anything

> That's the idea. You think about what you're going to write in a strongly typed language rather than just throwing stuff at the wall hoping that something will stick.

I think this is a valid point for developers who only have a few years of experience but I've been coding professionally for over a decade now - I don't need the compiler to artificially slow me down - I'd rather spend my mental energy thinking about the algorithm/architecture in its purest form without getting caught up in trying to satisfy the compiler's tedious requirements.

For me programming in a typed language is like using software that always asks you "are you sure you want to do this?" every time you tell it to do something. It's OK if you're a beginner, but I just find it frustrating.

I spent many years programming in ActionScript 3 and then Java so I feel like I've given typed languages a fair shot.

Re: Angular 4.0.0 Now Available

#325

Post by usrusr »

ErikAugust wrote: post #4
elmigranto wrote: post #2

I'm so out of the loop… Feels like a week ago everyone talked about how cool and performant v2 will be when it's finally out of the beta and officially ready for production, and now there is v4 release. What's going on with versions?

SEMVER - Semantic Versioning - http://semver.org/

Aka when in doubt, increment leftmost, also we won't tell you wether we did a complete conceptual overhaul or just found a corner case that is provably incompatible. And I really thought it would be good.

Re: Angular 4.0.0 Now Available

#326

Post by sundvor »

lldata wrote: post #199
sundvor wrote: post #170

Earlier quoted context omitted.

I want to move on from Jquery... Have been learning C# on the back end for the past year and a bit, but now it's time to do the front end. Looking at both A1 and A2 has confused me, so might just try React and see if that is more compatible with my ageing me. :) Nevertheless, I also really like the looks of Typescript. Could your possibly recommend a(n opinionated) way to get started with the two?

https://github.com/wmonk/create-react-app-typescript

Thanks - that looks good, will check it out.

Re: Angular 4.0.0 Now Available

#327

Post by usrusr »

timdavila wrote: post #314
Matthias247 wrote: post #83

Earlier quoted context omitted.

All hiring posts that are looking for "Angular 2" developers are now outdated and have to be switched to Angular 4 :) And recruiters will probably not understand that the difference between ng2 and ng4 is minor, while the difference between ng1 and ng2 is night and day.

I can see it now Required: 3+ years experience building Angular 4 apps

And the person who eventually gets hired points out that this is impossible, he could not possibly have made more than the two years he has on Angular 3. And he must be really ahead of the curve, all the other losers who applied barely got that much on 2...

Re: Angular 4.0.0 Now Available

#328

Post by sundvor »

doczoidberg wrote: post #198
sundvor wrote: post #170

Earlier quoted context omitted.

I want to move on from Jquery... Have been learning C# on the back end for the past year and a bit, but now it's time to do the front end. Looking at both A1 and A2 has confused me, so might just try React and see if that is more compatible with my ageing me. :) Nevertheless, I also really like the looks of Typescript. Could your possibly recommend a(n opinionated) way to get started with the two?

I came from C# WPF/Winforms and have to say that Angular 2 is more familiar to me than react. Of course the whole web stack is a new thing. Angular makes web app development much more productive.

Interesting; perhaps I ought to learn both, at least to a certain minimum level - to assess where I'm at with each as such.

Re: Angular 4.0.0 Now Available

#329

Post by coldtea »

vog wrote: post #222
alttab wrote: post #212

Earlier quoted context omitted.

What's been your experience with browser-side debugging? The one thing that scares me about typescript is you end up debugging something you didn't write.

That's why I'd personally prefer Flow for that. It has a more elaborate type system anyway. [1] Moreover, Flow is pure annotation, which can be removed by Babel. And Flow is also backed by a large company (Facebook instead of Microsoft). However, if you do want to generate JS, use a language that elminiates runtime errors almost completely, such as Elm or OCaml (through bucklescript or js-of-ocaml). [1] The following…

>And Flow is also backed by a large company (Facebook instead of Microsoft).

Only Facebook doesn't care much to back or promote Flow, besides the occasional blog post, whereas Microsoft has created a whole IDE / VS Code support for it, great tooling, documentation, etc.

Re: Angular 4.0.0 Now Available

#330

Post by coldtea »

jondubois wrote: post #231
danielpatrick wrote: post #189

Earlier quoted context omitted.

I've been using Angular 2 for a medium sized application that will be going into production within the next few weeks. I'm not affiliated with the Angular team at all. I started using it when this app was very much a POC last summer, just as the Angular team was finishing up the 2.0 release. I learned firsthand last summer the issues with using a framework that was still in the oven: constant updates and some depende…

I don't particularly like TypeScript. It slows me down because of several reasons: - Compile time means that it takes more time to debug anything. - The rigid interfaces mean that I need to spend more time researching how to use various modules/libraries (maybe code completion would offset this problem but this is only possible with a heavy IDE that has intellisense or similar - Not Atom). - When I want to test somet…

>The rigid interfaces mean that I need to spend more time researching how to use various modules/libraries

Why, otherwise you'd just throw random parameters in a module's functions and see what sticks?

>Compile time means that it takes more time to debug anything.

Most people compile their JS anyway, TS or not, with Babel et al.

>maybe code completion would offset this problem but this is only possible with a heavy IDE that has intellisense or similar - Not Atom

VS Code has code completion for TS and is similar to Atom. And even Sublime Text has code completion for TS (based on tools MS itself provides for "intellisense" style predictions).

>- It requires more planning to do anything (since you have to design the interfaces before you can start to implement). This is also not good if you just want to try something quickly and then roll back later

Doesn't make any sense. It's not as if you don't need to know the interfaces before you start to implement with regular js. Only there you need to hunt for the documentation to tell you what's expected to pass -- instead of seeing what the types are directly (e.g. with intellisense).

>- Changes to one class/interface tend to have a large cascading effect on other classes/interfaces so it takes more time to make changes to code - This happens with JS too but to a much lesser extent.

It happens to the exact same extend in JS. Only with TS you are shown where the problems are automatically, with JS you have to hunt those places or discover it at runtime.

The rest goes downhill...

Post reply on HN