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

311–320 of 360 posts

Re: Angular 4.0.0 Now Available

#311

Post by danielpatrick »

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 (maybe code completion would offset this problem but this is only possible with a heavy IDE that has intellisense or similar - Not Atom).

Obviously, to each his own.

I'd encourage you try Typescript again though. Your given reason doesn't make much sense. Regardless of whether the language is strongly typed or weakly typed, you still need to use modules and libraries correctly. "Not having to research" means you're just going to end up throwing data at a library without knowing what it's expecting. The research has to happen in both scenarios, but with typed languages it's easier. The research is just in the code already. (Try VS Code, not a "heavy" IDE by any means, but it has native support for TS code completion.)

If I have any modular interface, you need to know what to pass me. If you're receiving data from me, you need to know the structure of what I'm sending back to you.

In a weakly typed language, you can guess at what data structure I'm going to want. You can fish around in my returned data for what you're looking for with no guarantees. You have to look for docs, which may or may not be up to date.

But in a strongly typed language, the code is the doc. You and I and your IDE and my IDE are all on the same page. And the docs are always up to date. You can't pass me data that I'm not expecting and you always know how to access the data I'm returning to you.

Re: Angular 4.0.0 Now Available

#312

Post by danielpatrick »

zdragnar wrote: post #234
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…

I have built multi-10k+ line applications in angular 1, 2 and react. My personal preference is react by a mile. The concept of modules and dependency injection was nice before we had any sort of module systems, but at this point it's essentially entirely busy work, given tools like proxyquire when testing. Template compilation errors are a nice step up from 1, but those that I've seen have been very misleading and ha…

You've build multi 10k+ line applications in Angular 2?

It was released 5 months ago.

Re: Angular 4.0.0 Now Available

#313

Post by danielvf »

danielpatrick wrote: post #312
zdragnar wrote: post #234

Earlier quoted context omitted.

I have built multi-10k+ line applications in angular 1, 2 and react. My personal preference is react by a mile. The concept of modules and dependency injection was nice before we had any sort of module systems, but at this point it's essentially entirely busy work, given tools like proxyquire when testing. Template compilation errors are a nice step up from 1, but those that I've seen have been very misleading and ha…

You've build multi 10k+ line applications in Angular 2? It was released 5 months ago.

Not GP, but it's been publicly available long before that.

Re: Angular 4.0.0 Now Available

#314

Post by timdavila »

Matthias247 wrote: post #83
coding123 wrote: post #10

I suspect there's going to be a bit of pushback to this acceleration in numbering.

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

Re: Angular 4.0.0 Now Available

#315

Post by zdragnar »

danielpatrick wrote: post #312
zdragnar wrote: post #234

Earlier quoted context omitted.

I have built multi-10k+ line applications in angular 1, 2 and react. My personal preference is react by a mile. The concept of modules and dependency injection was nice before we had any sort of module systems, but at this point it's essentially entirely busy work, given tools like proxyquire when testing. Template compilation errors are a nice step up from 1, but those that I've seen have been very misleading and ha…

You've build multi 10k+ line applications in Angular 2? It was released 5 months ago.

One in angular 2, two in 1, and another that was a maaasive project in react. Team sizes varied from 3 devs to 12 or 16 (I forget which)

Re: Angular 4.0.0 Now Available

#316

Post by fuzzy2 »

rocky1138 wrote: post #274
fuzzy2 wrote: post #132

Earlier quoted context omitted.

Angular is different. It is not concerned with the server side at all. It's just about so-called Single Page Applications. This SPA would typically talk to services via "AJAX" (though probably with JSON). These services could be implemented using any technology.

This still doesn't describe how Angular is objectively "better." In fact, because it requires Javascript just to render HTML, it is objectively worse than straight up HTML delivered from a server-side solution.

> This still doesn't describe how Angular is objectively "better."

Of course. Because it isn’t. It’s not worse either. It’s different. It’s a completely different approach to creating web applications.

Everyone has different criteria to meet. Working without JavaScript usually isn’t one with modern web applications.

Re: Angular 4.0.0 Now Available

#317

Post by ZoeZoeBee »

caleblloyd wrote: post #193

What is one supposed to type into Google when trying to differentiate from Angular 1 and Angular >= 2? I used to type Angular2 but posts going forward may mention Angular4 now and not show up.

Angular 2+ is just Angular.

Angular 1.x is AngularJs.

If you are trying to differentiate the two in google, add -AngularJS to the end of the search. Also pretty good bet you're going to want to search within the last year for up to date posts.

Versioning and Releasing Angular http://angularjs.blogspot.com/2016/12/ok-let-me-explain-its-...

Re: Angular 4.0.0 Now Available

#318

Post by leshow »

danielpatrick wrote: post #221
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.

Yes, good question. I use VS Code (with the Chrome debugger plugin) and that works like a charm. I don't debug javascript in the browser anymore. TS provides source mappings to map the compiled javascript back to the source (similar to a .dll's .pdb maybe?). It took me some time to set up the config file which proved to be a headache (because webpack was screwing with the source maps), but again once that was set up…

Odd, I'm new to vscode, but I tried to set up this plugin and it was completely unusable to me.

Perhaps you can describe the steps you followed? I tried installing the plugin and launching chrome with the debug flag, then setting a breakpoint in vscode. Is there something I am missing there?

Re: Angular 4.0.0 Now Available

#319

Post by davidjnelson »

davedx wrote: post #168
pasta wrote: post #106

Earlier quoted context omitted.

"Who thought it was a good idea to make Angular 2 incompatible with Angular 1?" This is so much discussed that I am not going to answer that. Google it. But according to the latest StackOverflow survey [1] Angular is still bigger than you think: AngularJS 44.3%, React 19.5% [1] http://stackoverflow.com/insights/survey/2017/

Most companies don't switch quickly. We have a huge Angular 1.x app, but after hiring some new developers for our team we found the pool of React devs was huge compared to Angular devs. So much developer goodwill and mindshare has been lost. After carefully evaluating the technical aspects of Angular and React and externalities like the above, we decided to start building new software with React. Angular won't go awa…

Similar to what happened with backbone when angular gained traction.

Re: Angular 4.0.0 Now Available

#320

Post by leshow »

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…

> - 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 available, so you can see almost right away how to use it. In the other case you have to rely on someone providing you really good documentation OR you read the implementation.

> - 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's either you find the error at compile time or at run time. Don't kid yourself, there's a 'cascading effect' in both typed and untyped codebases, just in the typed one the compiler will help you find errors.

Granted, I'm not the biggest TS fan, I'd take Elm or Purescript, or even Flow. But your gripes seem to be directed to typed languages in general.

Post reply on HN