WEBVTT

00:00:00.080 --> 00:00:03.210
Exactly 10 years ago today, which
is really

00:00:03.240 --> 00:00:07.229
mind-blowing I have to say,
was a pretty important day for me because

00:00:07.360 --> 00:00:11.280
I released the first version of my Angular
course, my Angular 2

00:00:11.340 --> 00:00:15.200
course, back then. And just like Angular,
this course, of course, has

00:00:15.240 --> 00:00:19.220
evolved a lot over those 10 years.
It has been updated countless time by

00:00:19.300 --> 00:00:22.440
me because, of course,
Angular evolved quite a bit.

00:00:22.450 --> 00:00:26.320
And in this video, in this episode,
I wanna talk a bit about

00:00:26.400 --> 00:00:30.300
Angular's past, where we're coming from,
where we are today, and of

00:00:30.340 --> 00:00:34.240
course, also where we're going
and what the future has on hold for

00:00:34.280 --> 00:00:37.700
for Angular developers,
if it's still a good idea to learn it,

00:00:37.740 --> 00:00:41.540
course, now also with AI, and yeah.
Let's dive in.

00:00:41.580 --> 00:00:45.480
So Angular, Angular 2 specifically, was

00:00:45.560 --> 00:00:48.500
announced back in 2014, developed in

00:00:48.540 --> 00:00:52.480
2015, and back then it was pretty

00:00:52.500 --> 00:00:56.080
controversial because it
was totally different compared to Angular

00:00:56.400 --> 00:00:59.980
1, AngularJS, which itself was one of the

00:01:00.060 --> 00:01:03.980
first major frameworks we had back then,
which essentially were

00:01:04.040 --> 00:01:07.320
created to help us get rid of jQuery or

00:01:07.720 --> 00:01:11.220
maybe, to put it in other terms,
to be able to build more

00:01:11.500 --> 00:01:14.960
capable, uh, web-first applications,

00:01:15.040 --> 00:01:19.000
interactive web applications you could
say, because it made

00:01:19.280 --> 00:01:23.180
building client-side rendered
and controlled applications easier,

00:01:23.240 --> 00:01:26.980
Angular 1. And then Angular 2
was announced and it was totally

00:01:27.020 --> 00:01:30.700
different. And in 2016, the first

00:01:30.710 --> 00:01:34.590
stable version of Angular was released,
Angular 2 was released, I

00:01:34.640 --> 00:01:38.470
mean. And, uh, as I mentioned,
in February 2016,

00:01:38.540 --> 00:01:42.260
I released the first version of my course,
back then for the beta of

00:01:42.340 --> 00:01:46.260
Angular 2, and I can tell you, there
were a lot of changes still in that beta

00:01:46.340 --> 00:01:49.420
phase and still in the release candidate
phase even.

00:01:49.520 --> 00:01:53.120
I updated the course many,
many times back then already

00:01:53.620 --> 00:01:57.550
but then we had Angular 2.
And the Angular back

00:01:57.620 --> 00:02:01.020
then, if you look at modern Angular code,
looked quite

00:02:01.040 --> 00:02:03.980
different. You had this concept of

00:02:04.180 --> 00:02:07.820
NgModules, of Angular modules,
where you had these

00:02:07.880 --> 00:02:11.620
classes and you had to add this NgModule,
uh,

00:02:11.740 --> 00:02:15.600
decorator and explicitly declare all the
components you

00:02:15.680 --> 00:02:19.580
were about to use.
And then you had those components,

00:02:19.620 --> 00:02:23.420
of course,
and you had your component classes, you

00:02:23.480 --> 00:02:27.140
had constructor-based dependency injection
if you had something to

00:02:27.180 --> 00:02:30.860
inject. It was, to some degree, of course,
very

00:02:31.000 --> 00:02:33.420
similar to how a component looks today.

00:02:33.440 --> 00:02:37.220
It's still a class. But then again, i-
it was very

00:02:37.340 --> 00:02:40.470
different. And especially NgModules
are something

00:02:40.540 --> 00:02:44.500
you might not really know anymore,
depending on when you

00:02:44.580 --> 00:02:48.440
started your Angular journey
and depending on in

00:02:48.480 --> 00:02:51.000
Angular version you were working.

00:02:51.040 --> 00:02:55.020
Because there still are many companies
and projects out there that are stuck

00:02:55.040 --> 00:02:57.510
on older versions, of course. Now in

00:02:57.520 --> 00:03:01.240
2017, we had the missing version 3

00:03:01.280 --> 00:03:04.860
because Angular had this release

00:03:04.920 --> 00:03:08.820
schedule to this day that every six months

00:03:09.100 --> 00:03:13.020
a new major version of Angular would be
released and I know,

00:03:13.080 --> 00:03:16.720
I remember back then, uh,
a lot of people were not happy about that

00:03:16.800 --> 00:03:20.790
because it sounded like Angular would
break every six months.

00:03:20.860 --> 00:03:24.750
I recall lots of, many comments
and messages in my course about

00:03:24.760 --> 00:03:28.400
people complaining about Angular changing
all the time, but it never really

00:03:28.480 --> 00:03:32.400
changed all the time. They just had
that release schedule to

00:03:32.440 --> 00:03:36.240
give them an opportunity of introducing
big new

00:03:36.400 --> 00:03:40.240
features, but they always did
that in a very backwards compatible way,

00:03:40.300 --> 00:03:43.120
and well,
it's the missing version 3 here in

00:03:43.240 --> 00:03:47.210
2017, uh,
because actually initially there were

00:03:47.240 --> 00:03:51.180
some version mismatches between the
Angular core packages and the

00:03:51.280 --> 00:03:55.120
Angular router package, because Angular
is a framework that's split up in a

00:03:55.240 --> 00:03:58.940
lot of different packages,
and they skipped a version,

00:03:58.980 --> 00:04:02.820
version 3,
to bring them back to the same version

00:04:02.860 --> 00:04:06.560
Now then the next big jump probably

00:04:06.700 --> 00:04:10.180
was in 2020 with the

00:04:10.240 --> 00:04:14.060
introduction of the Ivy compiler,
and of course, between

00:04:14.140 --> 00:04:18.120
those years here, or in 2018 and so on,
the Angular

00:04:18.220 --> 00:04:21.940
team was heavy at work, uh,
working on that new compiler,

00:04:22.019 --> 00:04:25.600
along with many other small tweaks
and improvements.

00:04:25.620 --> 00:04:29.480
And the idea behind that compiler
was to really rewrite the

00:04:29.520 --> 00:04:33.040
internals of Angular
and how components are compiled and

00:04:33.100 --> 00:04:36.560
translated to actual instructions
that manipulate the

00:04:36.600 --> 00:04:40.460
DOM,
because the old compiler had some

00:04:40.500 --> 00:04:44.480
some problems,
led to unnecessarily large bundle sizes,

00:04:44.520 --> 00:04:48.000
so that's why they had this huge project
to

00:04:48.080 --> 00:04:51.500
rewrite that internal compiler. Now why
is that

00:04:51.540 --> 00:04:55.520
important? It is important because this

00:04:55.800 --> 00:04:59.420
phase could be referred to as the boring
phase.

00:04:59.460 --> 00:05:03.080
From 2017 to 2022, uh, to

00:05:03.360 --> 00:05:07.280
2020, not a lot changed. A lot

00:05:07.400 --> 00:05:11.160
changed internally and there
were minor tweaks, but the core

00:05:11.240 --> 00:05:15.040
feature set,
how you build Angular components

00:05:15.080 --> 00:05:18.060
didn't change a lot. Why is
that important?

00:05:18.110 --> 00:05:21.520
Because this was also the time
when there was lots of

00:05:21.580 --> 00:05:25.480
competition in the JavaScript framework
market, of course, if you wanna call

00:05:25.540 --> 00:05:29.140
it like this. We had the release of Vue.js

00:05:29.400 --> 00:05:33.100
2 in 2016. We had a

00:05:33.340 --> 00:05:37.280
lot of development in the React ecosystem
and the React world.

00:05:37.320 --> 00:05:40.990
I mean, in 2018, React Hooks
were introduced.

00:05:41.040 --> 00:05:44.620
So it felt like the rest of the JavaScript
ecosystem

00:05:44.700 --> 00:05:48.620
was evolving rapidly
and not everybody liked

00:05:48.630 --> 00:05:52.420
that, to be clear. Angular felt stagnant,
and that

00:05:52.480 --> 00:05:56.360
is maybe not as bad as it sounds. Um,
of course a

00:05:56.400 --> 00:06:00.220
lot of people valued
that stability because again, there were

00:06:00.240 --> 00:06:04.220
many complaints about everything changing
all the time in

00:06:04.260 --> 00:06:08.140
the JavaScript ecosystem,
which of course feels kind of like a joke

00:06:08.180 --> 00:06:11.720
look at today and all the AI-driven
evolution and the

00:06:11.760 --> 00:06:14.490
constant change with AI we see almost
every day.

00:06:14.500 --> 00:06:17.920
But yeah,
that was back then what people complained

00:06:18.712 --> 00:06:21.981
That was the boring phase. Now,
that boring phase

00:06:22.432 --> 00:06:26.322
stopped or came to an end around 2022 when

00:06:26.352 --> 00:06:29.692
with Angular 14,
standalone components were

00:06:29.752 --> 00:06:33.112
introduced in developer preview back then,
I think.

00:06:33.152 --> 00:06:36.572
And the idea here was
that all of a sudden you didn't

00:06:36.652 --> 00:06:39.452
need, um, Angular modules

00:06:39.592 --> 00:06:42.222
anymore. Instead, you could add this

00:06:42.512 --> 00:06:46.412
standalone flag to your component
and then you would be able to

00:06:46.472 --> 00:06:50.412
use that component in other components
without ng

00:06:50.611 --> 00:06:54.332
modules, so without this stuff.
You could still

00:06:54.532 --> 00:06:58.132
use ng modules.
You could use them together with

00:06:58.152 --> 00:07:01.261
You could mix and match as needed because
again, backwards

00:07:01.312 --> 00:07:05.012
compatibility and giving people an easy
migration path was

00:07:05.092 --> 00:07:09.032
always important to the Angular team,
but you didn't

00:07:09.152 --> 00:07:13.072
have to. So that
were standalone components and

00:07:13.112 --> 00:07:16.792
that was then rapidly followed up in 2023
with

00:07:16.872 --> 00:07:20.812
Angular 16 with Signals and many more

00:07:20.892 --> 00:07:24.292
features.
Many more features like a different way of

00:07:24.372 --> 00:07:28.292
rendering content conditionally with @if
instead of the

00:07:28.472 --> 00:07:32.322
ngIf directive. And also, there were

00:07:32.322 --> 00:07:35.452
first experiments being made into zoneless
Angular.

00:07:35.472 --> 00:07:39.092
And in case you don't know, uh, Angular,
when it was released,

00:07:39.132 --> 00:07:42.912
Angular 2, used a concept called ngZone or

00:07:42.972 --> 00:07:46.722
Zone.js,
which was essentially a library

00:07:46.752 --> 00:07:50.472
kinds of events that could occur on a
website like

00:07:50.492 --> 00:07:54.252
clicks and HTTP requests, uh, being

00:07:54.352 --> 00:07:58.132
sent and, and many other things.
And it would then basically run change

00:07:58.192 --> 00:08:02.072
detection to see if the DOM needs to be
updated in response to

00:08:02.132 --> 00:08:05.912
any of these events.
The advantage of this approach was

00:08:05.992 --> 00:08:09.532
updates felt magical. Unlike with React,
you didn't have to

00:08:09.592 --> 00:08:12.222
call setState or anything like that.

00:08:12.232 --> 00:08:15.732
But the disadvantage, of course, was
that you had this monkey

00:08:15.792 --> 00:08:19.632
patching where, uh,
a library would inject event listeners to

00:08:19.672 --> 00:08:23.572
kinds of events with all the overhead
that meant, with all the additional bundle

00:08:23.612 --> 00:08:27.381
size that meant, and therefore, it was

00:08:27.432 --> 00:08:31.201
also less efficient than React's
mechanism, for example.

00:08:31.272 --> 00:08:35.112
And zoneless, therefore,
was another big step forward which

00:08:35.212 --> 00:08:39.172
was enabled by Signals because the idea
behind Signals was that now all of a

00:08:39.272 --> 00:08:42.751
sudden you had an explicit way of telling
Angular

00:08:43.352 --> 00:08:46.952
that some state changed and it
was able to remember

00:08:47.032 --> 00:08:50.792
where that state in the DOM
was being used and it was then able to

00:08:50.852 --> 00:08:53.962
update just that part of the DOM. So that

00:08:53.992 --> 00:08:57.832
fine-grained reactivity
was introduced to Angular in

00:08:58.032 --> 00:09:01.872
2023. And therefore, that is

00:09:01.932 --> 00:09:05.432
something that was and still
is often called the Angular

00:09:05.572 --> 00:09:09.532
Renaissance. After the boring phase and

00:09:09.672 --> 00:09:13.662
after the kind of chaotic initial days
with all

00:09:13.692 --> 00:09:16.792
those breaking changes compared to Angular
1,

00:09:16.912 --> 00:09:20.512
Angular saw lots of love from the
community

00:09:20.612 --> 00:09:23.732
again because they were making big

00:09:23.912 --> 00:09:26.852
steps into a future that made Angular

00:09:27.052 --> 00:09:31.022
leaner, easier to use to some degree
and brought it

00:09:31.092 --> 00:09:34.761
more in line, uh,
with what people saw in some of the other

00:09:34.772 --> 00:09:38.532
frameworks out there. Signals,
for example, were made popular

00:09:38.552 --> 00:09:42.462
by SolidJS but were actually, I think...

00:09:42.512 --> 00:09:45.952
Uh,
one of the first major frameworks to use

00:09:45.992 --> 00:09:49.472
They just didn't call it Signals,
but Refs.

00:09:49.572 --> 00:09:53.292
Anyways, that was, uh, where Angular

00:09:53.302 --> 00:09:56.852
was heading. And now for 2026

00:09:56.932 --> 00:10:00.662
and the future, uh, we'll, of course,
see more development

00:10:00.672 --> 00:10:04.462
there. We'll see Signal Forms.
The Angular team

00:10:04.532 --> 00:10:08.432
also, of course,
is embracing AI with an MCP server

00:10:08.472 --> 00:10:11.792
that's built into the CLI to make AI power

00:10:11.952 --> 00:10:15.732
development on Angular apps easier,
to make AI aware of all

00:10:15.752 --> 00:10:19.332
those Angular features. And therefore,
it's a story

00:10:19.732 --> 00:10:23.352
of a framework that has actually been
pretty

00:10:23.472 --> 00:10:27.032
stable and backwards compatible throughout
its entire

00:10:27.092 --> 00:10:30.652
lifetime despite reinventing itself at

00:10:30.692 --> 00:10:34.511
least once,
maybe even multiple times depending on how

00:10:34.552 --> 00:10:38.271
it. It's been super stable
and backwards compatible, uh,

00:10:38.432 --> 00:10:42.212
and I think the Angular team-
team did a great job there.

00:10:42.222 --> 00:10:46.002
And they were able to really, I think,
change the image, uh,

00:10:46.132 --> 00:10:49.892
of Angular at least a bit from a framework
that felt pretty

00:10:50.052 --> 00:10:53.752
heavy and maybe hard to learn to a more

00:10:53.912 --> 00:10:57.771
modern framework Now one thing Angular has
always been, by the way,

00:10:57.812 --> 00:11:01.692
is a batteries included framework where
you would

00:11:01.752 --> 00:11:05.172
have things like form handling, routing,
HTTP

00:11:05.252 --> 00:11:09.072
requests, dependency injection, uh,
state management

00:11:09.112 --> 00:11:12.312
across components. You had
that all built into the framework.

00:11:12.352 --> 00:11:16.332
You didn't need to reach for third-party
libraries here unlike

00:11:16.372 --> 00:11:20.212
with React where you had to bring in a
third-party router, you

00:11:20.292 --> 00:11:24.092
had to bring in a third-party state
management library and so on.

00:11:24.132 --> 00:11:27.792
So that, of course,
is also something many companies value.

00:11:27.832 --> 00:11:31.312
Therefore, Angular has seen steady growth

00:11:31.692 --> 00:11:35.292
over all those last 10 years
if you take a look at

00:11:35.332 --> 00:11:39.232
its growth curve, but of course,
part of the truth

00:11:39.392 --> 00:11:42.972
is also that React has seen

00:11:43.032 --> 00:11:46.382
much more growth. I mean,
if you add the React curve

00:11:46.492 --> 00:11:50.052
here, the Angular one is barely

00:11:50.092 --> 00:11:53.072
visible. And especially since, uh, early

00:11:53.192 --> 00:11:56.472
2025, React took off and we all know why,
of

00:11:56.512 --> 00:12:00.492
course. That is because of AI. Because AI,
and I've

00:12:00.512 --> 00:12:04.072
said it many times before in other videos,
has one clear favorite and that is

00:12:04.672 --> 00:12:08.572
React with Next.js and Tailwind and

00:12:08.612 --> 00:12:12.512
not Angular. Does that mean though
that Angular is dead

00:12:12.572 --> 00:12:15.112
or that you should not learn Angular
anymore?

00:12:15.132 --> 00:12:18.872
And what does the future of Angular in
general look like with

00:12:19.271 --> 00:12:23.141
AI being thereWell, Angular to this

00:12:23.232 --> 00:12:27.122
day is still being used by many big
enterprises because of-

00:12:27.151 --> 00:12:30.791
especially because of all that stability,
that constant backwards

00:12:30.812 --> 00:12:34.492
compatibility that has not just been
talked

00:12:34.551 --> 00:12:37.671
about, but that has been proven.
Because of the

00:12:37.712 --> 00:12:41.512
batteries-included approach, Angular
is popular in

00:12:41.572 --> 00:12:45.192
many big companies. Of course, React,
just to be very clear,

00:12:45.271 --> 00:12:48.771
is popular in many big companies as well,
but

00:12:48.832 --> 00:12:52.572
the Angular download numbers don't
necessarily

00:12:52.632 --> 00:12:56.551
reflect the actual usage or popularity

00:12:56.651 --> 00:13:00.641
Angular has,
especially amongst enterprises accurately

00:13:00.732 --> 00:13:03.932
and I can tell you, uh, from
that course here, this

00:13:03.972 --> 00:13:07.932
course has 850,000 learners and

00:13:07.992 --> 00:13:11.972
that puts it not far behind my React
course on

00:13:12.092 --> 00:13:15.752
Udemy. Now, of course, there also
are more React courses on

00:13:15.832 --> 00:13:19.472
Udemy or-
or more bigger React courses on Udemy than

00:13:19.551 --> 00:13:23.271
are Angular courses, but nonetheless,
my experience

00:13:23.332 --> 00:13:27.012
has not been the one that you could, uh,

00:13:27.051 --> 00:13:30.992
derive from just these charts.
I have always seen

00:13:31.031 --> 00:13:34.791
that especially business customers
are learning Angular

00:13:34.992 --> 00:13:38.952
a lot too and that, of course,
therefore makes it still to

00:13:38.992 --> 00:13:42.712
this day a great choice for building web

00:13:42.752 --> 00:13:46.712
applications, modern web applications,
and it is very modern

00:13:46.722 --> 00:13:50.492
thanks to the Angular renaissance
and all the features that are still being

00:13:50.531 --> 00:13:54.311
planned. Of course,
the thing to consider is

00:13:54.551 --> 00:13:58.051
AI and AI is changing, of course,

00:13:58.151 --> 00:14:01.112
how we build programs, how we write code.

00:14:01.151 --> 00:14:04.651
We write less code.
I write less code at least.

00:14:04.692 --> 00:14:08.452
I use tools like Cloud Code
or Cursor for which I

00:14:08.472 --> 00:14:11.531
also have courses by the way.
They're all linked below the video

00:14:11.592 --> 00:14:15.252
join them. We write code,
we build programs

00:14:15.291 --> 00:14:18.752
differently, but, of course,
our technology choices still

00:14:19.112 --> 00:14:22.612
matter.
We still want to use technologies that

00:14:22.651 --> 00:14:26.551
maintained, that get security updates,
that get some new

00:14:26.632 --> 00:14:30.631
features that make them more efficient
or that, uh, lead

00:14:30.692 --> 00:14:34.352
to better performance or
that enable new use

00:14:34.361 --> 00:14:37.872
cases that maybe then don't require third
party libraries anymore.

00:14:37.911 --> 00:14:41.821
We still want to use technologies like
this and when it comes to that,

00:14:42.012 --> 00:14:45.992
Angular, of course, still is a decent,
an excellent choice,

00:14:46.132 --> 00:14:48.952
just like React is, to be very clear here.

00:14:48.972 --> 00:14:52.651
And of course, before I get the comments,
yes, Vue and

00:14:53.151 --> 00:14:57.031
Svelte, they're all amazing too.
This video, as you maybe noticed by

00:14:57.051 --> 00:15:00.872
looking at the video title, uh,
and thumbnail, is about Angular

00:15:00.972 --> 00:15:04.762
though. So yes, it still
is a great choice and yes, AI knows

00:15:04.832 --> 00:15:08.512
how to write Angular code, especially
if you give it the right context, which

00:15:08.571 --> 00:15:12.212
you always have to do no matter what
you're building with which

00:15:12.222 --> 00:15:15.632
technology. And therefore,
I think Angular is well

00:15:15.672 --> 00:15:18.832
positioned for this AI part future.

00:15:18.872 --> 00:15:22.661
If you believe that in three years
or so nobody's going to write

00:15:22.712 --> 00:15:26.452
any code anymore anyways
and therefore technology choices don't

00:15:26.492 --> 00:15:30.462
matter anymore, things will be different,
of course, for you.

00:15:30.531 --> 00:15:34.271
That is not my belief though.
From what I see, from my day-to-day

00:15:34.391 --> 00:15:38.031
usage with AI where I'm heavily using it
and where most of my code is

00:15:38.092 --> 00:15:41.672
generated by AI,
I can tell you controlling it,

00:15:41.771 --> 00:15:45.291
steering it, making choices,
choosing technologies,

00:15:45.391 --> 00:15:49.012
choosing, uh, software architectures
is more important than

00:15:49.092 --> 00:15:52.531
ever and yeah, Angular
is still a great choice

00:15:52.571 --> 00:15:56.352
there.
So that was my short history on Angular,

00:15:56.372 --> 00:15:59.891
will always have a special place in my
heart because as I

00:15:59.911 --> 00:16:03.551
mentioned,
this was the first major course at

00:16:03.592 --> 00:16:07.571
least that I released on Udemy
and it has changed a lot for

00:16:07.612 --> 00:16:10.862
me. It allowed me to create courses for a

00:16:11.012 --> 00:16:14.521
living. It has changed the lives
and careers of countless

00:16:14.612 --> 00:16:17.672
people. I got so many awesome messages
and feedback and

00:16:17.712 --> 00:16:21.372
therefore, yeah, Angular always
was amazing and it's

00:16:21.432 --> 00:16:23.132
especially amazing for me