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

211–220 of 360 posts

Re: Angular 4.0.0 Now Available

#211

Post by wyldfire »

danielpatrick wrote: post #192
nkkollaw wrote: post #91

Earlier quoted context omitted.

I have a question. Who thought it was a good idea to make Angular 2 incompatible with Angular 1? You had it, and you blew it. Most people aren't going to use any version of Angular, now, and have switched to React and Vue.

Angular 2 is a different framework, plain and simple. You can continue to use AngularJS 1.x if you were on that framework. I understand the frustration of someone who has used AngularJS 1.x. There is not really a straightforward and low risk path to upgrading a production app. But that is like saying there is not really a straightforward risk to switching from AngularJS 1.x to React. They're different frameworks. Ang…

> Angular 2 is a different framework, plain and simple.

I wonder if, strategically, it would have been a better idea to give it a new name rather than a subsequent version number?

Re: Angular 4.0.0 Now Available

#212

Post by alttab »

danielpatrick wrote: post #189
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'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…

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.

Re: Angular 4.0.0 Now Available

#213

Post by mikewhy »

humanrebar wrote: post #160
cheapsteak wrote: post #58

Earlier quoted context omitted.

It seems that lockstep versioning makes semantic versioning less meaningful A major version bump for a module could signal a breaking change, or it could just be due to the packages it's locked to having had a breaking change

A breaking change in your dependencies is a breaking change for you. If it weren't, minor version upgrades would cause you to pull in incompatible dependencies. This is why keeping your dependency list as tiny as possible is imperative.

Wait, I'm confused. Say I'm the author of a library. Some of my dependencies had breaking changes, but they didn't affect the users of my library, as it's handled in some method.

Should that be a new major version of the library?

Re: Angular 4.0.0 Now Available

#214

Post by bigmanwalter »

git-pull wrote: post #17

I'll probably try it. But man, am I getting jaded about all this javascript framework stuff. Every 6 months stuff breaks, every 2 years there's a huge shift. The problem with javascript I've been facing is value. Time and effort doesn't always correlate to what I get in the other end. In fact, I can say when building, going single-page is a time sink. And it's almost always a mistake to go SPA first. Using a django o…

Preach brother. I've been saying the same thing for years now after a similar experience moving from an Angular SPA to a Django + Pjax app. I noticed an order of magnitude increase in productivity.I can't imagine going back now.

Re: Angular 4.0.0 Now Available

#215

Post by hacktothefuture »

alttab wrote: post #212
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…

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.

Great question. This is a cause for concern for me as well.

Re: Angular 4.0.0 Now Available

#216

Post by kamarg »

alttab wrote: post #212
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…

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.

You can tell the Typescript compiler to generate source maps that allow you to debug your Typescript code in the browser with a single configuration item in tsconfig.json. Chrome (and maybe Firefox?) will download them by default when you open up the debugger.

Re: Angular 4.0.0 Now Available

#217

Post by wincy »

alttab wrote: post #212
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…

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.

Re: Angular 4.0.0 Now Available

#218

Post by alttab »

jneal wrote: post #47
aprdm wrote: post #14

Even with SemVer versions it looks really weird to see a new Angular relase branded as 4.0.0. Angular 1 to Angular 2 made me drop angular entirely, that happened less than 6 months ago I believe. Just reading Angular 4 gives me the creeps. Is 4 widely different from 2? How am I suppose to know if you using semver and already have a really bad history?

I've been testing out 4 since it hit beta, and haven't had any issues. Code literally just works after updating to the new version with 0 issues, in my case at least.

How big is your code base and how many people work in it and how many paying customers do you have?

Re: Angular 4.0.0 Now Available

#219

Post by alttab »

tannhaeuser wrote: post #136

First of all, congrats to the Angular team. I'll say personally I've never been a fan of Angular, but I think if you want Java/J2EE-ish all-encompassing component model and decorator-/annotation-based GUIs, it certainly is a very strong contender (though kindof the thermonuclear option and absurdly complex IMHO, at least if you have some prior web development experience). I think Google's track record wrt. long-term…

Rails, bootstrap, react when necessary on portions of pages. Use regular links again - use regular forms again, remember - AJAX can be cool, but it doesn't have to be the whole app.

Remember when the server generated HTML? You could middle click a link!

I'll even use normal browser history, instead of re-implementing it in Javascript for my app (with bugs).

Re: Angular 4.0.0 Now Available

#220

Post by recursive »

d3ad1ysp0rk wrote: post #206
fatal510 wrote: post #117

Earlier quoted context omitted.

Because Angular was the only real choice for awhile. That's like saying PHP is still bigger than you think because half the web runs on PHP but that is old legacy shit. Almost othing new and serious is using it.

What do you consider "serious"? Plenty of large applications are being built right now in PHP 7.

"Serious" means it was started by a person who regularly blogs or tweets about how to choose a technology.
Post reply on HN