Angular feels like frontend framework built by backend java Spring developers, that hate frontend development.
as a Java Spring Developer that hates frontend development (and loves Java and Spring), I found this very funny :)
Angular v8.0
121–130 of 210 posts
Re: Angular v8.0
#122I feel Svelte is the framework that Angular author actually wanted to build since the first version.
Funnily enough, Ivy takes a pretty similar approach to Svelte with its markDirty calls similar to Svelte's $$invalidate calls. That said, Angular doesn't utilize its compiler the same way Svelte does (yet) so time will tell.
I think moving stuff from runtime to compiletime is the theme of most changes to Angular 2+ compared to Angular 1. So I'm very much expecting Angular devs to look at Svelte and start hitting ctrl-c ctrl-v repeatedly on their keyboards :)
Re: Angular v8.0
#123While the effort by the Angular team deserves praise, I think for the vast majority of use cases it is a mistake to do it all client side. With some exceptions, there is really no benefit in making a SPA but there are many drawbacks. I don't say this lightly. I used AngularJS in 2015 and since then I've been making SPAs in React, Vue, and Inferno + Mobx.
I've been building Angular apps for 3 years now, and all projects I've built have had a "relatively light" frontend, meaning little to no business logic there.
Angular as a framework doesn't prevent you from doing anything on the backend. It's all about the re-usable components imo.
Re: Angular v8.0
#124Angular is really a great framework. I think a lot of people complaining about Angular haven't actually built an app in Angular 4+. I also wish the Angular team had just called Angular 2 something else, since the 1 -> 2 transition frustrated a lot of people who jumped ship and never looked back. I also understand that people just have different preferences, which is fine, too. Out of the box, you get: routing with la…
I started working with angular 7 this February and I have to admit the learning curve was steep at first but after the slow start I quickly built my first project and now fully appreciate its power. I also think I am lucky to have taken a stab at it in its current stages, 4+ as I lost my patience for too much noise and too many changes. I also have many praises for Visual Studio Code. The reasons you mentioned are ve…
Are you using the angular CLI to generate components/services? That saves a lot of time.
The thing we love about Angular is compartmentalizing everything.
Re: Angular v8.0
#125Angular is really a great framework. I think a lot of people complaining about Angular haven't actually built an app in Angular 4+. I also wish the Angular team had just called Angular 2 something else, since the 1 -> 2 transition frustrated a lot of people who jumped ship and never looked back. I also understand that people just have different preferences, which is fine, too. Out of the box, you get: routing with la…
How do you guys keep up with these frameworks? You get stuck on one project or in one startup for 2 years and Angular has moved 6.5 whole number versions all while the rest of the job market is confused but kind of tolerating why you jump around jobs so much if I'm using Angular, my "side project" isn't going to be using a higher version of Angular every 6 months. Its going to be using React or something to see what…
Angular uses semantic versioning and adheres to it very strictly. Most of the time updating between versions merely involves running "ng update --all" and if that doesn't auto update everything you just see which items it errored for and update them. There have been articles showing how very large enterprises have updated their entire codebase in under a day.
If you're on one project or startup using Angular and you haven't kept up with the versioning that's a problem with the developers. There is no reason to be using a version lower then 1 back.
Features marked for deprecation will at minimum take 2 version to be removed, so 1 year after deprecation was marked. This isn't like Angular 1 -> 2 and I hope anyone who pays attention at all to front end will realize this. Complaining about angular versioning at this point would be like complaining that react bumped a patch version.
Re: Angular v8.0
#126Angular is really a great framework. I think a lot of people complaining about Angular haven't actually built an app in Angular 4+. I also wish the Angular team had just called Angular 2 something else, since the 1 -> 2 transition frustrated a lot of people who jumped ship and never looked back. I also understand that people just have different preferences, which is fine, too. Out of the box, you get: routing with la…
> get back up to speed on configuring Webpack only to forget how until next time Is this common? Thank goodness i'm not the only one! I keep telling myself next time i'm going to remember to bookmark the billion tabs I open on StackOverflow trying to figure out Webpack configuration, but nope I forget and start from scratch every time. EDIT: Also I've coded a project in Angular 2 and Angular 4 respectively; I have no…
I'm pretty sure it's more common than it should be, really. Everytime I had to create a new project I'd have to copy/paste the webpack configs left and right. Sometimes I miss the gulp days - it was way more straight forward and not so much magic involved.
> Also I've coded a project in Angular 2 and Angular 4 respectively; I have nothing bad to say about Angular but I still prefer Vue
I have used Angular 1 professionaly for more than 3 years with some big projects and when Angular 2 was released I ditched the idea of using it in a newer project. I was using Angular 2 since the alpha days and saw how some things got over complicated. And then I too chose Vue and fell in love with it.
Re: Angular v8.0
#127Angular is really a great framework. I think a lot of people complaining about Angular haven't actually built an app in Angular 4+. I also wish the Angular team had just called Angular 2 something else, since the 1 -> 2 transition frustrated a lot of people who jumped ship and never looked back. I also understand that people just have different preferences, which is fine, too. Out of the box, you get: routing with la…
As a long time React developer, I second this. Especially this part: > There's no need to evaluate different routers, form libraries These two things have been the bane of my React development experience ever since the days of "flux". Every new React project I start I end up using a different set of libraries, and it's not just me either -- a very experienced React dev I work with just switched our React e-commerce S…
If you were new to React or Angular, but needing to choose one for a single developer project, which would it be now in 2019?
Re: Angular v8.0
#128Angular is really a great framework. I think a lot of people complaining about Angular haven't actually built an app in Angular 4+. I also wish the Angular team had just called Angular 2 something else, since the 1 -> 2 transition frustrated a lot of people who jumped ship and never looked back. I also understand that people just have different preferences, which is fine, too. Out of the box, you get: routing with la…
I've been using Angular for a few months now and it's mostly been a good experience. We've been using Angular 7. My biggest gripe, and this might just be my inexperience, is fighting the change detector to try and ensure reasonable performance when displaying a large number of elements. There are certainly mechanisms to do this but it does seem to take some work.
what's your use case to display a large number of elements in the same page? Curious.
Re: Angular v8.0
#129Earlier quoted context omitted.
I started working with angular 7 this February and I have to admit the learning curve was steep at first but after the slow start I quickly built my first project and now fully appreciate its power. I also think I am lucky to have taken a stab at it in its current stages, 4+ as I lost my patience for too much noise and too many changes. I also have many praises for Visual Studio Code. The reasons you mentioned are ve…
Are you using the angular CLI to generate components/services? That saves a lot of time. The thing we love about Angular is compartmentalizing everything.
Yes, I am using Angular CLI and I love it. I'd become jaded over the years with all the Visual Studio way of creating projects, lots of dialogs, popups, template generators and in my opinion dumb boring click-click way of dealing with things where the meat is hidden from the the programmer. With the new stack I feel like I am getting a whiff of fresh air. I'm still using C#/EF to create web APIs and deal with the DB layer but on the front end i'm much happier with Angular/Node/Typescript.
Re: Angular v8.0
#130Earlier quoted context omitted.
What batteries does Angular include that Vue doesn't?
I think instead of meaning specific components (http and routing come to mind) that more often people mean by "batteries included" that Angular has an opinionated way to do most everything, and their docs/guides include examples. In my experience, Vue and React allow a higher degree of freedom in choosing how you would like to approach various things, and there are more choices for some core behaviors for them as wel…
Freedom isn't bad but in larger environments that freedom can lead to multiple ways of doing the same thing and in turn it becomes harder for new people to jump into current projects, they have to first figure out what the initial thought behind a design was. The way Angular is opinionated benefits this setup and unknown projects look more familiar when you first dive in. Also, searching for solutions online almost always fit your needs.