How’s it going, I'm a Adam, a Full-Stack Engineer, actively searching for work. I'm all about JavaScript. And Frontend but don't let that fool you - I've also got some serious Backend skills.
Location
City of Bath, UK 🇬🇧
Education
10 plus years* active enterprise development experience and a Fine art degree 🎨
How’s it going, I'm a Adam, a Full-Stack Engineer, actively searching for work. I'm all about JavaScript. And Frontend but don't let that fool you - I've also got some serious Backend skills.
Location
City of Bath, UK 🇬🇧
Education
10 plus years* active enterprise development experience and a Fine art degree 🎨
Architecture in angular is admittedly beautiful, but I'm moving away from Oop. I think the decipline in writing an Angular app is what it's good for and a lesson for future frameworks. It's easy to hate on angular and I am not a fan to be clear.
The classification of the frameworks in this way may be easy today, but we should also be talking about what Svelte does differently and how it affects web dev in the long term? As browsers become much better in what they do - maybe, just maybe, every framework must have a part of Svelte built into them (more specifically the DOM updates, similar to Ivy in Angular). See reddit.com/r/javascript/comments/c... for a live discussion where a number of framework creators have jumped in to add their view-point on vdom vs dom updates.
If I have to choose a framework today and I am a beginner/intermediate developer: I would certainly go towards Vue or React. Larger community = more help. If I have to choose one of them - I would choose one that I personally like (Vue) or the one that my team is comfortable working in. I don't build Facebook-level apps, but from what I have seen Vue is good for me in building a scalable enterprise-grade, JS-heavy app as React.
I will incorporate Svelte in some future work. I still am not sure how Svelte can manage DOM updates under a high workload - but do not see that as a technical limitation that makes it suitable only for a "light app or blog".
Cheers.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Angular is suitable for? 😅
... being deprecated 😅
... Slow applications
... Bloated applications
... Legacy applications
Architecture in angular is admittedly beautiful, but I'm moving away from Oop. I think the decipline in writing an Angular app is what it's good for and a lesson for future frameworks. It's easy to hate on angular and I am not a fan to be clear.
The classification of the frameworks in this way may be easy today, but we should also be talking about what Svelte does differently and how it affects web dev in the long term? As browsers become much better in what they do - maybe, just maybe, every framework must have a part of Svelte built into them (more specifically the DOM updates, similar to Ivy in Angular). See reddit.com/r/javascript/comments/c... for a live discussion where a number of framework creators have jumped in to add their view-point on vdom vs dom updates.
If I have to choose a framework today and I am a beginner/intermediate developer: I would certainly go towards Vue or React. Larger community = more help. If I have to choose one of them - I would choose one that I personally like (Vue) or the one that my team is comfortable working in. I don't build Facebook-level apps, but from what I have seen Vue is good for me in building a scalable enterprise-grade, JS-heavy app as React.
I will incorporate Svelte in some future work. I still am not sure how Svelte can manage DOM updates under a high workload - but do not see that as a technical limitation that makes it suitable only for a "light app or blog".
Cheers.