Earlier quoted context omitted.
Try jQuery - even more simple.
I tried jQuery and found it to be more difficult to manage a single page app.
[deleted]
Angular 4.0.0 Now Available
171–180 of 360 posts
Re: Angular 4.0.0 Now Available
#172Re: Angular 4.0.0 Now Available
#173Earlier quoted context omitted.
1) I'm still new to this, but why would someone not use Angular Universal/why is it not default? I have only read positives, but am sure there must be a reason. 2) Why do we need Angular Material 2, when Google's official Material Components Web project is meant to be used with all kinds of frameworks and even has framework integration examples with Angular2: https://github.com/material-components/material-components…
1) the core of Angular Universal "graduated" into @angular/platform-server with 4.0 - previously it was a more experimental project. We're officially supporting a "renderToString()" API that can be used however you like. So really, it's brand new, and we're excited to see what the community does with it. Philosophically, pre-rendering every SPA server side isn't a silver bullet. For a ton of cases it makes a lot of s…
Thank you, that was really helpful!
Re: Angular 4.0.0 Now Available
#174I really hope the Angular team find their path again, because it seems like they've lost it a long time ago!. I remember learning Angular 1, 5 years ago, it was an awesome experience but now ... let's say I wish them the best for real.
Re: Angular 4.0.0 Now Available
#175Earlier 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.
There was Ember.
Emphasis on the past tense -- "was" :)
Re: Angular 4.0.0 Now Available
#176Earlier quoted context omitted.
Angular is a mess but typescript is alive and kicking on its own, even with react. Personally I'm one of the apparently rare breeds that hate angular but loves typescript. I wish there were more of us. They're really in different realms and please don't make them part of the same whole. Typescript is a transpiler but the transforms it does are designed to mimic accepted JavaScript idioms. When I'm debugging typescrip…
I agree 100%. TypeScript is an invaluable, mature technology that provides large productivity boosts to any team that maintains a mid-sized code base. It plays extremely well with React too, and it's benefits are independent of the tech stack. If you are used to typed components/templates, you will NEVER want to go back. I would argue that is more important to have static typing in the front-end compared to the back-…
> There is more state, lot's of shared entities and unit tests are expensive to write and maintain.
Good point, but only to an extent: Unit tests boilerplate in dynamic languages that is redundant with static typing is only a (minor) subset of unit tests that you should be writing for your code. Static typing is not an excuse to skip unit tests altogether. I've unfortunately met people claiming exactly that...
Re: Angular 4.0.0 Now Available
#177Is Angular ever going to support web standards such as web components?
You can already use most simple web components in Angular without issues - as far as Angular is concerned, it's just another DOM element. We also support native (or emulated) Shadow DOM out of the box. It gets a little more interesting when you start interleaving Angular and WebComponents, but one of the deprecations in 4.0 (regarding Angular's use of the tag) is squarely aimed at making that easier in the future.
Thanks, what I was asking is when are Angular components going to be Web components?
Re: Angular 4.0.0 Now Available
#178I'll be that guy. I'm sure the Angular team are great people, and they're clearly talented devs... but stay away from Angular. It doesn't help with the problems you will actually face. Typed Javascript is a cargo cult. Angular just plain confusing for no apparent benefit. Dependency injection is bizarre. The distinction between modules, components, and directive is unnecessary. The Javascript community in general is…
Angular is a mess but typescript is alive and kicking on its own, even with react. Personally I'm one of the apparently rare breeds that hate angular but loves typescript. I wish there were more of us. They're really in different realms and please don't make them part of the same whole. Typescript is a transpiler but the transforms it does are designed to mimic accepted JavaScript idioms. When I'm debugging typescrip…
I've never seen anyone conflate TypeScript with angular before GP's comment.
(And I happen to agree with him on angular being confusing and not well designed)
Re: Angular 4.0.0 Now Available
#179Earlier 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.
"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/
If you are not going to answer it, don't add noise to the discussion.
Re: Angular 4.0.0 Now Available
#180Even 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?
Angular 1 to 2 was a complete rewrite with a change of paradigm, but 2 to 3 then 4 is just because semver (i.e. there may be some breaking changes, it's not 100% backward compatible).
Yeah, but why?
With all people complaining about Java, we don't have to deal with this shit so often.
Most breaking changes I see on the JavaScript ecosystem seem like mostly cosmetic. It has been a rough road trying to make decisions on tech that won't get stale quickly and have support dropped in a 1-2 year frame.
Angular is really one of the worst offenders in this regard. What was so fundamentally broken with Angular v1's api that could not just be worked internally and incremented?
It also has ramifications which are pretty dire in my opinion. We have an app written with Ionic 1, so I go check out Ionic 2 see what's going on, and oh look such shiny things, how do we migrate? Nope, full rewrite of course.
There are some decision makers in these teams which are completely disregarding the fact they are burning through several work hours of people around the globe without real value.
Stop breaking things because new. Fine, use semver, but don't you change that first digit lightly, it hurts when you do.