31–40 of 42 posts
Earlier quoted context omitted.
The question is what's the best way to create an ng 5.1 app? i.e. what was just announced. I've just manually updated all deps to ^5.1.0.
If you grab the latest angular-cli and do `ng new foo`, you will get the latest 5.1.0 update. Or if you have an existing app, run `npm install` but make sure you update your package-lock.json file.
Even if you never use Angular you can thank them for finding and fixing a huge Webpack memory leak: https://github.com/webpack/webpack/issues/5992#issuecomment-...
I thought this was some kind of joke... until I realized they skipped v3. But still, v5 already? Or did I just get used to Bootstrap 4 being in Alpha for years?
4 -> 5 included some new cool features but was a smooth upgrade. 6 is coming out in March and then a new "major version" is scheduled every 6 months. This is common for end-user apps but feels very weird for developer libraries and frameworks. We are used to X.Y.Z releases where X are "major rewrite", Y are significant updates, and Z are bugfixes. That said, Angular's new scheme could be technically correct strict "s…
I work in a large corporation and they're still planning their transition to 1.5 and then to 2. I'm keeping up by building stuff in my off time, but trying to keep a fortune 200 corporation on a six month upgrade track? Not happening.
I've already heard rumblings from upper management of going back to some open source Java frameworks like Spring MVC, Vaadin or gulp Struts because of how fast they are releasing major versions and the time and cost of keeping up.
My fear is Angular will be regulated to startups, medium sized businesses or small autonomous business units within larger companies. When faced with a six month upgrade schedule, many larger organizations I fear are going to balk and just drop it in favor of something they are already comfortable with. . ergo my company wanting to go back to Java since 95% of everything built here is done with Java.
Earlier quoted context omitted.
Getting from 1 to 2 was quite an experience. Much discussed here and elsewhere. Thereafter though, they have been just relentlessly polishing, improving, smoothing rough edges, making bundle smaller, making compilation and execution faster, etc. It is really a model of exactly what you would want, in terms of a joint respect for backward compatibility with forward progress. I don't understand the "haters" in some pee…
Agreed - I have had a pretty pleasant experience with Angular in general, although it wasn't without its issues. Tests ran clearly slower than in AngularJS for example - the overhead in compiling TypeScript and setting it up is greater. Dynamically creating components was a painful experience for getting things done just right - I created a very flexible drag and drop module with it, I had to create some machinery on…
Can anyone speak to their successes with Angular post 2.0? I feel like any time it comes up, it's mostly horror stories about the transition or how shops have just moved on to Vue, etc. Is it worth still considering / where does Angular shine where React and Vue come up short?
I like React because it's easier to set up and get working; you don't need some ridiculous dev environment just to say "Hello world". I think React does one thing and does it really well, and its flexibility makes it easier to mix and match packages to do what you need to do.
Angular is ridiculously opinionated, and very complete. But for big projects or for multiple projects with different people coming in and out of the project this can be a strong asset. We've had some big React projects where you have to go out and get Redux, then start thinking about observables, maybe you want TypeScript but maybe you want Flow, etc. Angular already thought about all of that, made decisions for you, and structured it in a standard way so that once you learn the conventions it's pretty easy to reason about any Angular project.
And as a front-end dev who got started on the Web in the Netscape days, I appreciate that Angular doesn't treat CSS as a bug to be fixed. React (and the kinds of people who work on React) seem to desire a pure JavaScript world, while Angular keeps a more familiar HTML/CSS convention on the template level.
It’s pretty good but react is better. There is still no documentation on the details of projection which is super frustrating.
I'm still on 1.0. Not changing either.
Earlier quoted context omitted.
Agreed - I have had a pretty pleasant experience with Angular in general, although it wasn't without its issues. Tests ran clearly slower than in AngularJS for example - the overhead in compiling TypeScript and setting it up is greater. Dynamically creating components was a painful experience for getting things done just right - I created a very flexible drag and drop module with it, I had to create some machinery on…
So if I have no preference of my own, you'd suggest Angular over React? I want to get the product out soon and focus on generating business value rather than the framework itself.