DEV Community

Cover image for Is Angular Dead in 2022?

Is Angular Dead in 2022?

Jonathan Gamble on January 25, 2022

In case you're unaware, Google has had an interesting track record in the Framework category. Not all of these are technically frameworks, but can ...
Collapse
 
gaul profile image
Info Comment hidden by post author - thread only accessible via permalink
Berrou

What a waste of time reading this post

Collapse
 
jdgamble555 profile image
Jonathan Gamble

You're probably right 😆

Collapse
 
sarcevicantonio profile image
Antonio Sarcevic

SvelteKit FTW :)

Collapse
 
ivan_jrmc profile image
Ivan Jeremic

React > Svelte

Collapse
 
mellunar profile image
mellunar • Edited

Yeah, because it's better to keep on:

import React, { useState } from 'react';
function Component() {
  const [count, setCount] = useState(0);
}

Enter fullscreen mode Exit fullscreen mode

instead of:

let count = 0;
Enter fullscreen mode Exit fullscreen mode

🤷

Thread Thread
 
ivan_jrmc profile image
Ivan Jeremic

You got hooked by the popular talk but lets be real there will always be people who like the react way more its just a function which returns UI no matter ho clean svelte or any new framework that comes out is there will always be people who like the react way more.

Thread Thread
 
sarcevicantonio profile image
Antonio Sarcevic

we got hooked by the underlying philosophy that creating interactive UI doesn't need to be a chore :D

Thread Thread
 
ivan_jrmc profile image
Ivan Jeremic

But it isn't for everyone, as I already said there are people who will always like the react model no matter what comes out because they come maybe more from a programming background first, in programming you build an application by composing functions together that do a certain job. In react you use functions and each one returns a piece of UI and its logic which makes sense and people build UIs that ways easier.

Thread Thread
 
kresli profile image
Eduard Jacko • Edited

@mellunar The React example is not a valid component ;) Maybe you should write an actual simple component as you are pointing to difference between state management only. This is more fair to compare

<script>
    let name = 'world';
</script>
<h1>Hello {name}!</h1>
<button on:click={() => name = "Hi"}>click me</button>
Enter fullscreen mode Exit fullscreen mode

vs



function Greeting() {
  const [state, setState] = useState("world")
  return (
      <>
          <h1>Hello  {state}!</h1>
          <button onClick={() => setState("Hi")}>click me</button>
      </>
  )
}
Enter fullscreen mode Exit fullscreen mode
Thread Thread
 
ivan_jrmc profile image
Ivan Jeremic • Edited

A javascript function body is your script tag in Svelte the javascript return is your svelte file for markup, some people like programming some like XML style.

Thread Thread
 
sarcevicantonio profile image
Antonio Sarcevic • Edited

Implying writing HTML isn't programming

Thread Thread
 
ivan_jrmc profile image
Ivan Jeremic

Writing jsx is.

Thread Thread
 
sarcevicantonio profile image
Antonio Sarcevic

Im glad you feel superior for making your life harder 🤣

Thread Thread
 
ivan_jrmc profile image
Ivan Jeremic

I'm sorry for you that your brain can't grasp it.

Collapse
 
sarcevicantonio profile image
Antonio Sarcevic

less features, more code, bigger bundle, worse performance ... 🤷‍♂️

Thread Thread
 
ivan_jrmc profile image
Ivan Jeremic

Bigger bundle on hello world apps yes, but once you have an bigger app react is smaller. Also less built in features(maybe) but overall more feature because of ecosystem, worst performance, nahh do you feel it?

Thread Thread
 
heydan83 profile image
Adan Ulloa

Svelte is faster because of the way it was designed without the virtual dom. That doesnt mean you will feel the diference on a modern pc. But been faster means that your application will be compatible with older devices or IoT devices which doesnt have that big of a hardware.

Collapse
 
ssergdev profile image
SergDev • Edited

There's no silver bullet. The framework we choose is really depends on the task (and the team we working with). Maybe I would not go with Angular for some lightweight site, but for complex enterprise application I believe Angular may be a good choice.

Collapse
 
kristher1619 profile image
Kristher Vidal

@jdgamble555

"You learned Angular through fireship.io, although he now prefers React (SMH)"

I think he still prefers angular, but React is where the views are.

so yeah so sad...

Collapse
 
spock123 profile image
Lars Rye Jeppesen

Our enterprice app, with 4 language versions compiled at build time, takes 1 min to compile.

Wth are you doing with your code?

Collapse
 
jdgamble555 profile image
Jonathan Gamble

Sorry, I was referring to installing Angular Universal with all its dependencies on Cloud Run, not a local compile.

Collapse
 
spock123 profile image
Lars Rye Jeppesen

ah makes sense. thanks

Collapse
 
nssimeonov profile image
Templar++ • Edited

Angular seems pretty much dead actually according to insights.stackoverflow.com/trends?...

Franewirj Popularity

Collapse
 
joelnietoll profile image
Joel Nieto

You know that the line you're highlighting isn't Angular, right?

Collapse
 
kresli profile image
Eduard Jacko • Edited

true. but still, the green is dying slowly

Collapse
 
seanperkins profile image
Sean Perkins

Ionic Framework developer here; Ionic's components are built with web components. We ship framework specific packages to help with framework integrations (React, Angular and Vue).

No Angular isn't dead.

The packages you mention as dead are just the predecessors to the current packages.

Thank you for acknowledging that Ionic isn't from Google. That is factual.

Collapse
 
kresli profile image
Eduard Jacko

You know, Microsoft is moving to use react-native in UWP so you are not right saying "Google and Microsoft build most of their apps with it." Microsoft did some experiments with Angular but they run away from it as fast as they could.

docs.microsoft.com/en-us/windows/d...

Collapse
 
andrewbaisden profile image
Andrew Baisden

Angular and JQuery don't get a lot of love anymore 😂

Collapse
 
mellunar profile image
mellunar

React is the one that should be dead

Collapse
 
liviufromendtest profile image
Liviu Lupei

The death of Angular was really visible on our side.

Lots of folks who were using Protractor for testing switched to Endtest.

Collapse
 
themikesanto profile image
Mike Santo

That could be due to the team's plan to deprecate Protractor by the end of the year.

Collapse
 
liviufromendtest profile image
Liviu Lupei

Oh, yes. That's a known fact.

Collapse
 
datumgeek profile image
Mike Graham

thank you sir - great perspective... building enterprise apps myself. love angular :)

Collapse
 
davishek7 profile image
Info Comment hidden by post author - thread only accessible via permalink
Avishek Das

This dude knows only one way to write clickbait titles, 'This technology is dead'.

Collapse
 
basspod profile image
Paul ODell

Sorry guys. Flutter is the way to go.

Collapse
 
jankapunkt profile image
Jan Küster • Edited

You know that a framework became mature and stable when people say it's dead while at the same time it has an ongoing roadmap and zillions of apps running at production.

Some comments have been hidden by the post's author - find out more