WEBVTT

00:00:00.000 --> 00:00:03.285
- As a professional web developer,

00:00:03.285 --> 00:00:07.104
I do work a lot with React,

00:00:07.104 --> 00:00:11.957
Angular, Vue, and similar
libraries and frameworks,

00:00:11.957 --> 00:00:15.710
especially since I do a lot
of front-end web development.

00:00:15.710 --> 00:00:20.230
And of course, I also got
some bestselling courses

00:00:20.230 --> 00:00:22.481
on those libraries and frameworks.

00:00:22.481 --> 00:00:26.184
And therefore, it's only
natural that I often get asked

00:00:26.184 --> 00:00:30.887
what my personal favorite
is and which library

00:00:30.887 --> 00:00:35.773
or framework I would recommend
to learn or to focus on,

00:00:35.773 --> 00:00:38.892
for example, now that a new year started.

00:00:38.892 --> 00:00:41.511
And therefore, over the next minutes,

00:00:41.511 --> 00:00:45.647
I wanna give you an idea
of what my favorite is

00:00:45.647 --> 00:00:49.366
and why that's the case, and I'll explain

00:00:49.366 --> 00:00:53.502
why it of course depends,
as it always does,

00:00:53.502 --> 00:00:57.655
which framework or library
you should focus on,

00:00:57.655 --> 00:01:01.390
but I'll also explain what it depends on.

00:01:01.390 --> 00:01:05.927
And therefore, I'll explore
the different philosophies

00:01:05.927 --> 00:01:08.629
behind those different frameworks.

00:01:08.629 --> 00:01:12.648
I'll explain who owns
and runs those frameworks

00:01:12.648 --> 00:01:15.650
and libraries and what that means for you

00:01:15.650 --> 00:01:19.336
and why that should influence your choice,

00:01:19.336 --> 00:01:22.555
which library or framework
you are going to use.

00:01:22.555 --> 00:01:25.573
And I'll also take a
look at the popularity,

00:01:25.573 --> 00:01:28.725
the numbers, how often
those libraries get used.

00:01:28.725 --> 00:01:32.545
I'll of course also give you an insight

00:01:32.545 --> 00:01:35.330
into how performant those frameworks

00:01:35.330 --> 00:01:38.482
and libraries are and if that matters.

00:01:38.482 --> 00:01:42.051
And I'll of course also
explore how easy or difficult

00:01:42.051 --> 00:01:45.520
those different libraries
are to learn and to master

00:01:45.520 --> 00:01:49.573
and to become better at
before I then, as promised,

00:01:49.573 --> 00:01:53.392
also let you know what
my personal favorite is.

00:01:53.392 --> 00:01:57.561
Now, let's start with the
different philosophies

00:01:57.561 --> 00:01:59.596
because that's really important.

00:01:59.596 --> 00:02:04.483
We got all these different
libraries and frameworks,

00:02:04.483 --> 00:02:08.785
but they don't all have
exactly the same philosophy,

00:02:08.785 --> 00:02:12.821
the same way of working,
and the same approach

00:02:12.821 --> 00:02:17.274
towards the idea of giving
you a tool that you can use

00:02:17.274 --> 00:02:21.911
to build web applications or
front-end web applications.

00:02:21.911 --> 00:02:25.330
For example, React, which arguably

00:02:25.330 --> 00:02:29.299
is the most popular library,
and I'll get back to that,

00:02:29.299 --> 00:02:33.635
React has the approach of being a library

00:02:33.635 --> 00:02:37.488
that's focused on managing the UI,

00:02:37.488 --> 00:02:41.207
updating the UI based on your code.

00:02:41.207 --> 00:02:44.109
And that sounds pretty
trivial, and it sounds

00:02:44.109 --> 00:02:48.012
like what such a front-end
library should do,

00:02:48.012 --> 00:02:50.680
and that's probably why React does it,

00:02:50.680 --> 00:02:52.665
but as you will see, for example,

00:02:52.665 --> 00:02:56.901
Angular does way more and
has more built-in features

00:02:56.901 --> 00:02:59.419
that can come in handy.

00:02:59.419 --> 00:03:00.970
React, on the other hand,

00:03:00.970 --> 00:03:05.173
in its core, is really just
about giving you the tools

00:03:05.173 --> 00:03:10.176
you need to derive state,
derive changing states

00:03:10.310 --> 00:03:14.029
and update the UI
accordingly so that you can,

00:03:14.029 --> 00:03:17.715
for example, listen to
a click on a button,

00:03:17.715 --> 00:03:22.101
then change some internal
data and then reflect

00:03:22.101 --> 00:03:24.636
that changed data on the screen.

00:03:24.636 --> 00:03:28.939
Now it turns out though, that in reality,

00:03:28.939 --> 00:03:33.008
most front-end web
applications you are building

00:03:33.008 --> 00:03:34.926
need a bit more than that.

00:03:34.926 --> 00:03:37.595
For example, they might need routing.

00:03:37.595 --> 00:03:42.598
So the capability of managing
different URL paths

00:03:43.299 --> 00:03:47.318
and displaying different
pages for different paths.

00:03:47.318 --> 00:03:49.636
Now, when I say pages,

00:03:49.636 --> 00:03:51.788
I, of course, here in the context

00:03:51.788 --> 00:03:55.457
of those front-end JavaScript libraries,

00:03:55.457 --> 00:03:58.959
mean that we're technically
still on the same page.

00:03:58.959 --> 00:04:02.111
We're still on the same HTML file

00:04:02.111 --> 00:04:05.380
that was originally
downloaded from the server,

00:04:05.380 --> 00:04:10.217
but the front-end JavaScript
changes what's visible

00:04:10.217 --> 00:04:11.751
in that file, so to say.

00:04:11.751 --> 00:04:13.752
So what's visible on the page.

00:04:13.752 --> 00:04:16.070
That's how single-page applications work.

00:04:16.070 --> 00:04:19.189
And even though they're called
single-page applications,

00:04:19.189 --> 00:04:22.658
because we have just this
one single HTML file,

00:04:22.658 --> 00:04:24.826
which is downloaded initially,

00:04:24.826 --> 00:04:28.696
those applications still
typically, very often,

00:04:28.696 --> 00:04:32.381
need to display different screens,

00:04:32.381 --> 00:04:35.350
different pages if you
wanna call it like this,

00:04:35.350 --> 00:04:37.235
so that we can, for example,

00:04:37.235 --> 00:04:41.054
view a login screen, and
once we are logged in,

00:04:41.054 --> 00:04:43.756
we might wanna move on
to a dashboard screen.

00:04:43.756 --> 00:04:47.175
And it would all be handled
by the same JavaScript code

00:04:47.175 --> 00:04:50.110
that's powered by React, for example.

00:04:50.110 --> 00:04:51.461
Now, React, however,

00:04:51.461 --> 00:04:56.464
doesn't have any built-in
mechanism that would watch the URL

00:04:57.165 --> 00:05:02.051
and would navigate you
from /login to /dashboard

00:05:02.051 --> 00:05:04.519
and display something else on the screen.

00:05:04.519 --> 00:05:07.905
You would have to build such
a functionality on your own,

00:05:07.905 --> 00:05:11.924
or what you would typically
do, you would reach out

00:05:11.924 --> 00:05:13.992
for a third-party library.

00:05:13.992 --> 00:05:16.060
For example, for React Router,

00:05:16.060 --> 00:05:20.230
which is a super popular
routing library for React.

00:05:20.230 --> 00:05:23.265
But that's the philosophy of React.

00:05:23.265 --> 00:05:26.384
You have just the basics built-in,

00:05:26.384 --> 00:05:30.170
and you then need extra
third-party libraries,

00:05:30.170 --> 00:05:33.222
which are not maintained by the React team

00:05:33.222 --> 00:05:35.423
but instead, by the React community

00:05:35.423 --> 00:05:38.976
to solve certain specific problems.

00:05:38.976 --> 00:05:42.845
And routing is a pretty common problem,

00:05:42.845 --> 00:05:45.830
and it has a very well-maintained library

00:05:45.830 --> 00:05:47.448
that solves that problem,

00:05:47.448 --> 00:05:49.566
but of course, there are multiple problems

00:05:49.566 --> 00:05:50.984
you might wanna solve.

00:05:50.984 --> 00:05:54.219
Advanced animations, form handling,

00:05:54.219 --> 00:05:56.171
advanced state management,

00:05:56.171 --> 00:05:58.872
and a broad variety of other things.

00:05:58.872 --> 00:06:02.108
And for all these different
problems, when using React,

00:06:02.108 --> 00:06:05.227
you need an extra third-party library.

00:06:05.227 --> 00:06:07.845
And that, for example, is different

00:06:07.845 --> 00:06:10.664
when you are working with Angular.

00:06:10.664 --> 00:06:14.416
Angular, unlike React,
is not just a library,

00:06:14.416 --> 00:06:18.369
which focuses on the bare
minimum, but instead,

00:06:18.369 --> 00:06:22.205
Angular actually is a framework that comes

00:06:22.205 --> 00:06:25.057
with batteries included, you could say.

00:06:25.057 --> 00:06:28.659
So it comes with many crucial features,

00:06:28.659 --> 00:06:33.229
many crucial solutions to
common problems built-in.

00:06:33.229 --> 00:06:36.881
For example, Angular has a
built-in routing package,

00:06:36.881 --> 00:06:40.667
which is developed and
maintained by the Angular team.

00:06:40.667 --> 00:06:44.536
So the same team that's
maintaining and developing

00:06:44.536 --> 00:06:47.171
the Angular core framework itself,

00:06:47.171 --> 00:06:49.573
the core library, if you
wanna call it like this.

00:06:49.573 --> 00:06:52.608
And there are many other
packages that are developed

00:06:52.608 --> 00:06:54.826
and maintained by the Angular team.

00:06:54.826 --> 00:06:57.411
For example, you have a
package for animations,

00:06:57.411 --> 00:07:01.931
for handling forms and
validating forms, and so on.

00:07:01.931 --> 00:07:04.850
And that's simply a different approach,

00:07:04.850 --> 00:07:07.118
a different philosophy.

00:07:07.118 --> 00:07:11.738
Now Vue, for example, is
a bit between those two,

00:07:11.738 --> 00:07:12.705
you could say.

00:07:12.705 --> 00:07:15.424
In its core, Vue is like React

00:07:15.424 --> 00:07:19.610
and focuses on just updating the UI.

00:07:19.610 --> 00:07:24.596
But Vue then has a team
of core maintainers

00:07:24.980 --> 00:07:29.500
where some of those team members
are then also responsible

00:07:29.500 --> 00:07:33.769
for some important third-party packages,

00:07:33.769 --> 00:07:38.255
which are only kind of
third party, I would guess,

00:07:38.255 --> 00:07:40.390
because they are, in the end,

00:07:40.390 --> 00:07:42.825
developed by those Vue core members

00:07:42.825 --> 00:07:46.177
and maintained by those members.

00:07:46.177 --> 00:07:49.813
And therefore, Vue does not
just have that core framework,

00:07:49.813 --> 00:07:53.916
but it also has some
crucial extra packages

00:07:53.916 --> 00:07:56.801
like a routing package that are maintained

00:07:56.801 --> 00:07:58.669
by some of the same people

00:07:58.669 --> 00:08:01.221
that are working on the core framework.

00:08:01.221 --> 00:08:05.924
Now, for other libraries
like Svelte or SolidJS,

00:08:05.924 --> 00:08:09.009
things are kind of similar, you could say.

00:08:09.009 --> 00:08:12.161
There, it's also some core members,

00:08:12.161 --> 00:08:17.165
some core members of the
Svelte or SolidJS teams,

00:08:17.498 --> 00:08:20.750
if you wanna call it like
this, that are also working

00:08:20.750 --> 00:08:24.553
on crucial third-party
libraries or extra frameworks

00:08:24.553 --> 00:08:28.639
that are building up on Svelte and SolidJS

00:08:28.639 --> 00:08:30.974
to offer features like routing.

00:08:30.974 --> 00:08:35.360
And that's actually an important topic.

00:08:35.360 --> 00:08:40.097
Frameworks building up
on those base libraries

00:08:40.097 --> 00:08:43.482
and frameworks, which
might sound weird at first.

00:08:43.482 --> 00:08:45.801
Why would we have a framework

00:08:45.801 --> 00:08:49.186
that builds up on React, for example?

00:08:49.186 --> 00:08:51.788
React itself is already a library,

00:08:51.788 --> 00:08:56.408
so why do we have some extra
framework that builds up on it?

00:08:56.408 --> 00:08:58.776
Well, we do have such frameworks,

00:08:58.776 --> 00:09:02.512
for example, Next.js but also Remix,

00:09:02.512 --> 00:09:05.714
because remember, React itself

00:09:05.714 --> 00:09:10.467
is just that basic thing
that handles UI updates.

00:09:11.451 --> 00:09:14.620
Now, recently, over the last one

00:09:14.620 --> 00:09:18.489
and two years, we've seen a huge trend

00:09:18.489 --> 00:09:21.791
where we seem to be moving away

00:09:21.791 --> 00:09:25.811
from building decoupled
front-end applications,

00:09:25.811 --> 00:09:29.263
single-page applications
with React or Angular

00:09:29.263 --> 00:09:32.298
and so on, and extra back-ends,

00:09:32.298 --> 00:09:34.933
extra REST APIs, for example.

00:09:34.933 --> 00:09:38.469
We seem to be moving away from that way

00:09:38.469 --> 00:09:40.270
of building web applications

00:09:40.270 --> 00:09:43.489
back to building full-stack applications.

00:09:43.489 --> 00:09:47.058
So where you have one
project where front-end

00:09:47.058 --> 00:09:50.460
and back-end work together
seamlessly and blend

00:09:50.460 --> 00:09:54.480
into each other, where the
server side pre-renders

00:09:54.480 --> 00:09:59.300
the front-end pages on the fly
on the server, for example,

00:09:59.300 --> 00:10:03.369
where the data for those
pages is fetched directly

00:10:03.369 --> 00:10:06.137
on the server and
rendered into those pages

00:10:06.137 --> 00:10:08.105
on the server, and so on.

00:10:08.105 --> 00:10:10.991
We're seeing a trend
where we're moving more

00:10:10.991 --> 00:10:13.926
towards that world again, which I guess

00:10:13.926 --> 00:10:16.461
is the world we're all coming from,

00:10:16.461 --> 00:10:20.047
back from our early PHP days and so on.

00:10:20.047 --> 00:10:24.400
But that's a topic for a
different video and talk.

00:10:24.400 --> 00:10:26.768
Anyways, we have that trend,

00:10:26.768 --> 00:10:30.337
and we have, therefore,
frameworks like Next.js

00:10:30.337 --> 00:10:34.490
or Remix for React, which
simplify the process

00:10:34.490 --> 00:10:37.058
of building such full-stack applications.

00:10:37.058 --> 00:10:40.427
So which allow you to build
full-stack applications

00:10:40.427 --> 00:10:45.430
with React by essentially
wrapping React, that core library,

00:10:45.464 --> 00:10:49.250
and by then giving you extra
features that allow you

00:10:49.250 --> 00:10:52.785
to set up routes that are
handled on the server,

00:10:52.785 --> 00:10:55.937
extra features that help
you with data fetching

00:10:55.937 --> 00:10:58.456
on the server, and so on.

00:10:58.456 --> 00:11:02.075
And Next.js and Remix are some really big,

00:11:02.075 --> 00:11:05.144
popular JavaScript frameworks.

00:11:05.144 --> 00:11:09.130
They are both for React,
and they're both key drivers

00:11:09.130 --> 00:11:11.831
of that trend, you could say.

00:11:11.831 --> 00:11:13.699
And I'm emphasizing this here

00:11:13.699 --> 00:11:18.319
because this also is an
important consideration to make

00:11:18.319 --> 00:11:21.171
when choosing a library or framework.

00:11:21.171 --> 00:11:23.856
If you wanna build such
a full-stack application,

00:11:23.856 --> 00:11:27.575
if you wanna follow that
trend, which has its merits,

00:11:27.575 --> 00:11:29.977
you might wanna pick a library

00:11:29.977 --> 00:11:33.329
that has some decent meta frameworks,

00:11:33.329 --> 00:11:35.414
as they're also sometimes called,

00:11:35.414 --> 00:11:38.649
that allow you to build
such full-stack applications

00:11:38.649 --> 00:11:40.517
in a simple and easy way.

00:11:40.517 --> 00:11:45.520
And for example, Angular
here only has Analog.js.

00:11:45.737 --> 00:11:50.741
And I'm saying only because
Analog.js is an amazing project,

00:11:52.158 --> 00:11:55.127
but it's also less mature,

00:11:55.127 --> 00:11:59.446
less feature-rich than
Next.js, for example,

00:11:59.446 --> 00:12:02.715
which makes sense because Analog.js

00:12:02.715 --> 00:12:05.867
is essentially developed by one person,

00:12:05.867 --> 00:12:09.587
whereas Next.js is
developed by a huge team

00:12:09.587 --> 00:12:12.755
working at Vercel, which
is a hosting provider.

00:12:12.755 --> 00:12:16.191
And therefore, since
we have only Analog.js,

00:12:16.191 --> 00:12:18.676
which is a bit less capable than Next.js,

00:12:18.676 --> 00:12:20.744
for example, if you wanna build

00:12:20.744 --> 00:12:24.496
such seamlessly integrated
full-stack applications

00:12:24.496 --> 00:12:27.048
with Angular instead of React,

00:12:27.048 --> 00:12:29.466
that could prove to be a bit trickier,

00:12:29.466 --> 00:12:32.202
and that might be a
reason for picking React.

00:12:32.202 --> 00:12:34.570
Now, for Vue, for example,

00:12:34.570 --> 00:12:35.954
things are different.

00:12:35.954 --> 00:12:39.523
There, we have another meta
framework built for Vue,

00:12:39.523 --> 00:12:41.091
which is called Nuxt,

00:12:41.091 --> 00:12:44.143
which is essentially the Next.js of Vue.

00:12:44.143 --> 00:12:46.394
I guess you see the similarities.

00:12:46.394 --> 00:12:48.679
Nuxt, Next. Yeah.

00:12:48.679 --> 00:12:51.815
It's a framework that
was developed for Vue

00:12:51.815 --> 00:12:53.716
multiple years ago already.

00:12:53.716 --> 00:12:55.968
It's developed by a big team.

00:12:55.968 --> 00:12:59.770
I think they even have some
venture capital funding,

00:12:59.770 --> 00:13:02.438
and they are building that meta framework,

00:13:02.438 --> 00:13:05.857
which allows you to build
full-stack applications

00:13:05.857 --> 00:13:07.992
for Vue, or with Vue.

00:13:07.992 --> 00:13:10.577
And that of course means
that if you wanna build

00:13:10.577 --> 00:13:12.345
such full-stack applications,

00:13:12.345 --> 00:13:15.114
Vue can be an attractive choice.

00:13:15.998 --> 00:13:21.001
Now, what about smaller
libraries like Svelte or SolidJS?

00:13:21.635 --> 00:13:24.170
And by the way, I know
that there are others,

00:13:24.170 --> 00:13:26.388
but I have to stop somewhere.

00:13:26.388 --> 00:13:29.256
Well, those smaller libraries

00:13:29.256 --> 00:13:31.308
also have such meta frameworks,

00:13:31.308 --> 00:13:35.294
which are maintained by the
developers and by the teams

00:13:35.294 --> 00:13:38.646
that are working on the
main libraries as well.

00:13:38.646 --> 00:13:42.649
Svelte has SvelteKit, which
is developed by the same team

00:13:42.649 --> 00:13:47.052
that develops Svelte, and
SolidJS has SolidStart,

00:13:47.952 --> 00:13:50.421
which is also such a full-stack framework

00:13:50.421 --> 00:13:53.022
that's developed by the
same team and person

00:13:53.022 --> 00:13:56.324
that works on the main library.

00:13:56.324 --> 00:13:59.977
So there, we also have
those full-stack frameworks.

00:13:59.977 --> 00:14:03.496
And that, therefore, gives us an idea

00:14:03.496 --> 00:14:06.731
of the different philosophies
of those libraries

00:14:06.731 --> 00:14:09.650
and frameworks and how
you can work with them.

00:14:09.650 --> 00:14:12.135
Now before we take a
look at their popularity,

00:14:12.135 --> 00:14:15.104
which might also matter
for various reasons,

00:14:15.104 --> 00:14:18.606
let's take a brief look
at who owns and runs

00:14:18.606 --> 00:14:21.641
and develops those libraries because that,

00:14:21.641 --> 00:14:25.827
of course, matters since
when you're choosing

00:14:25.827 --> 00:14:28.746
a technology, you wanna be sure

00:14:28.746 --> 00:14:32.532
that it will still be
around in a couple of years.

00:14:32.532 --> 00:14:35.567
You don't wanna rewrite
your entire application

00:14:35.567 --> 00:14:40.571
in two or three years just
because the technology,

00:14:40.571 --> 00:14:45.574
the library or framework you
chose today is outdated then.

00:14:47.108 --> 00:14:49.593
And here, to start with React again,

00:14:49.593 --> 00:14:53.496
that was originally developed by Facebook,

00:14:53.496 --> 00:14:56.898
and it's still owned and
maintained by Facebook.

00:14:56.898 --> 00:15:01.885
But recently, a part of
the team working on React

00:15:01.968 --> 00:15:06.305
has actually moved to a
different company, to Vercel,

00:15:06.305 --> 00:15:09.040
which is that hosting
provider that also developed

00:15:09.040 --> 00:15:11.408
the Next.js framework.

00:15:11.408 --> 00:15:16.061
And we can see the impact
of this because recently,

00:15:16.061 --> 00:15:20.347
the focus seems to be
on working on Next.js

00:15:20.347 --> 00:15:24.050
and making sure that React
works well together with it,

00:15:24.050 --> 00:15:27.886
but I did create a separate
video on the current state

00:15:27.886 --> 00:15:31.238
of React on my Academind YouTube channel

00:15:31.238 --> 00:15:33.673
if you wanna learn more about that.

00:15:33.673 --> 00:15:37.375
The main takeaway though,
is that React is maintained

00:15:37.375 --> 00:15:41.828
by teams that are
employed at big companies,

00:15:41.828 --> 00:15:43.429
at Facebook, for example,

00:15:43.429 --> 00:15:47.415
and that those companies
are using React internally.

00:15:47.415 --> 00:15:50.768
Therefore, it's pretty much guaranteed

00:15:50.768 --> 00:15:53.586
that React will not just be around today,

00:15:53.586 --> 00:15:55.671
but also in the future.

00:15:55.671 --> 00:15:58.356
Now it's pretty much the same for Angular

00:15:58.356 --> 00:16:03.226
because Angular is and was
developed by a team at Google,

00:16:03.226 --> 00:16:06.228
and it's getting used by Google in dozens,

00:16:06.228 --> 00:16:08.896
or, I guess, hundreds of internal

00:16:08.896 --> 00:16:12.148
and publicly available applications.

00:16:12.148 --> 00:16:15.517
If you're using a Google
service on the internet,

00:16:15.517 --> 00:16:19.420
chances are pretty decent,
that it's powered by Angular.

00:16:19.420 --> 00:16:22.205
And therefore here, it's the same.

00:16:22.205 --> 00:16:26.558
There is a pretty much a
guarantee that Angular,

00:16:26.558 --> 00:16:31.128
despite Google's tendencies
to kill its projects,

00:16:31.128 --> 00:16:33.946
will still be around in a couple of years

00:16:33.946 --> 00:16:37.065
because they're using it a lot internally.

00:16:37.065 --> 00:16:40.751
Now for Vue and SolidJS,

00:16:40.751 --> 00:16:45.621
it's a bit different because
both of these libraries

00:16:45.621 --> 00:16:49.457
and frameworks are indeed
developed by the community,

00:16:49.457 --> 00:16:51.575
if you wanna call it like this.

00:16:51.575 --> 00:16:56.578
Vue was originally developed
by one person, by Evan You,

00:16:56.595 --> 00:17:00.347
but it now is actually
maintained by a huge team

00:17:00.347 --> 00:17:05.351
of core Vue maintainers, if
you wanna call it like this.

00:17:05.467 --> 00:17:08.636
And therefore, it has a pretty stable base

00:17:08.636 --> 00:17:11.238
of developers working on it.

00:17:11.238 --> 00:17:13.156
Nonetheless, it's not a company,

00:17:13.156 --> 00:17:16.358
but instead, the community
that's maintaining Vue.

00:17:16.358 --> 00:17:19.627
And you can judge on yourself
if that makes you feel better

00:17:19.627 --> 00:17:24.130
or worse, or if that gives
you more or less security

00:17:24.130 --> 00:17:27.499
that Vue will still be
around in a couple of years.

00:17:27.499 --> 00:17:30.618
Personally, I'm pretty sure it will be.

00:17:30.618 --> 00:17:34.754
Now SolidJS is not
entirely a one-man show.

00:17:34.754 --> 00:17:36.938
It does have a lot of contributors,

00:17:36.938 --> 00:17:38.589
a lot of people working on it.

00:17:38.589 --> 00:17:41.024
There is a team behind it, you could say,

00:17:41.024 --> 00:17:45.227
but to me, it feels like SolidJS

00:17:45.227 --> 00:17:49.580
has less people working
on it than Vue does.

00:17:49.580 --> 00:17:52.549
For example, it's a smaller library.

00:17:52.549 --> 00:17:56.285
And for Svelte, there,
it's important to note

00:17:56.285 --> 00:18:00.371
that one person who
originally built Svelte

00:18:00.371 --> 00:18:03.706
is now supported by many core members

00:18:03.706 --> 00:18:07.542
just as it's the case for
Vue, and that one person,

00:18:07.542 --> 00:18:11.528
Rich Harris, is now
also employed at Vercel.

00:18:11.528 --> 00:18:15.164
So you could say Svelte
has kind of a company

00:18:15.164 --> 00:18:16.715
backing behind it.

00:18:16.715 --> 00:18:19.817
Not as strong as Next.js and React,

00:18:19.817 --> 00:18:22.419
but some company backing.

00:18:22.419 --> 00:18:26.288
And that is an overview
of who owns and runs

00:18:26.288 --> 00:18:29.173
those different libraries and frameworks.

00:18:29.173 --> 00:18:32.192
With that, let's finally leave that behind

00:18:32.192 --> 00:18:36.095
and take a look at how
popular those frameworks

00:18:36.095 --> 00:18:38.930
and libraries are because
that can, of course,

00:18:38.930 --> 00:18:42.766
also be an important decision criteria

00:18:42.766 --> 00:18:46.935
since you might prefer to
work with a library a lot

00:18:46.935 --> 00:18:48.936
of other developers are using as well,

00:18:48.936 --> 00:18:51.305
since it will be easier
to find freelancers

00:18:51.305 --> 00:18:54.007
for popular libraries, since the ecosystem

00:18:54.007 --> 00:18:57.826
might be more active, since
you might find more tutorials

00:18:57.826 --> 00:19:02.079
and courses and solutions
for problems, and so on.

00:19:02.079 --> 00:19:05.564
And here, it's probably
fair to say that React

00:19:05.564 --> 00:19:10.568
is the most popular
front-end JavaScript library.

00:19:10.985 --> 00:19:13.570
At the point of time
where I'm recording this,

00:19:13.570 --> 00:19:17.322
it has more than 200,000 GitHub Stars.

00:19:17.322 --> 00:19:22.325
It has around 22 million
weekly downloads on npm.

00:19:22.759 --> 00:19:24.727
So the React package is downloaded

00:19:24.727 --> 00:19:28.930
around 22 million times every week.

00:19:28.930 --> 00:19:32.832
And I looked up some
job postings on Indeed,

00:19:32.832 --> 00:19:34.484
but also LinkedIn Jobs.

00:19:34.484 --> 00:19:37.786
And there, you were able to find thousands

00:19:37.786 --> 00:19:41.205
of job postings looking
for React developers.

00:19:41.205 --> 00:19:44.257
On Indeed, for example,
when I recorded this,

00:19:44.257 --> 00:19:48.460
I found around 11,000
job postings for React,

00:19:48.460 --> 00:19:52.095
and I found even more
job postings on LinkedIn.

00:19:52.095 --> 00:19:53.229
Now, Angular

00:19:53.229 --> 00:19:58.066
is probably the second most
popular framework here,

00:19:58.066 --> 00:20:01.418
though it of course always
depends on how you measure it.

00:20:01.418 --> 00:20:06.038
But Angular has over 90,000 GitHub Stars.

00:20:06.038 --> 00:20:11.041
So way less than the 200,000
React has, but still.

00:20:11.358 --> 00:20:16.345
It has 3.2 million weekly npm downloads.

00:20:16.512 --> 00:20:19.931
So also way less than React.

00:20:19.931 --> 00:20:21.848
Though, at least to my knowledge,

00:20:21.848 --> 00:20:25.151
one reason for that also is that Angular

00:20:25.151 --> 00:20:30.154
is quite popular amongst huge enterprises,

00:20:30.671 --> 00:20:35.508
and they sometimes have their
own dependency registries,

00:20:35.508 --> 00:20:37.776
some internal dependency registries

00:20:37.776 --> 00:20:39.494
where it might be served from.

00:20:39.494 --> 00:20:41.828
But still, it's definitely fair to say

00:20:41.828 --> 00:20:44.530
that it has less downloads than React.

00:20:44.530 --> 00:20:48.516
And at least on Indeed,
I also found less jobs

00:20:48.516 --> 00:20:50.768
for Angular than for React.

00:20:50.768 --> 00:20:54.520
I found around 6,000 job postings there

00:20:54.520 --> 00:20:57.139
compared to the 11,000 of React.

00:20:57.139 --> 00:20:58.957
But on LinkedIn, on the other hand,

00:20:58.957 --> 00:21:01.542
I found more job postings for Angular.

00:21:01.542 --> 00:21:04.210
So overall, it's definitely fair to say

00:21:04.210 --> 00:21:06.829
that it's pretty popular,
and that especially

00:21:06.829 --> 00:21:11.065
if you're looking to find
a job for the framework

00:21:11.065 --> 00:21:16.068
you're using, angular has
lots of available jobs.

00:21:16.752 --> 00:21:21.438
Now, Vue then is a bit smaller
than React and Angular,

00:21:21.438 --> 00:21:25.808
though not necessarily at all
the metrics you could look at.

00:21:25.808 --> 00:21:29.710
Now, the Vue 3, which is
the latest Vue version,

00:21:29.710 --> 00:21:33.947
GitHub repository has
around 40,000 GitHub Stars.

00:21:33.947 --> 00:21:37.749
So less than Angular and
of course, less than React.

00:21:37.749 --> 00:21:42.752
But Vue had over 4 million
weekly npm downloads.

00:21:42.786 --> 00:21:45.438
So actually more than Angular.

00:21:45.438 --> 00:21:49.190
However, it definitely
had less job postings.

00:21:49.190 --> 00:21:51.075
For example, on Indeed,

00:21:51.075 --> 00:21:55.661
I found around 1,400 jobs
when I created this year.

00:21:55.661 --> 00:21:59.414
And that's less than the
6,000 or 11,000 I found

00:21:59.414 --> 00:22:01.265
for Angular and React.

00:22:01.265 --> 00:22:04.367
It also had less jobs
on LinkedIn, by the way.

00:22:04.367 --> 00:22:07.903
Nonetheless, Vue is definitely
a popular framework.

00:22:07.903 --> 00:22:09.620
And if you're looking to find a job,

00:22:09.620 --> 00:22:14.607
there still is a decent amount
of job postings for Vue.js.

00:22:14.841 --> 00:22:19.544
And these things change a
bit for Svelte and SolidJS.

00:22:19.544 --> 00:22:23.530
They are still popular if you
take a look at GitHub Stars.

00:22:23.530 --> 00:22:27.999
For example, Svelte has
over 70,000 GitHub Stars.

00:22:27.999 --> 00:22:30.818
SolidJS has around 30,000.

00:22:30.818 --> 00:22:32.836
So they are popular there.

00:22:32.836 --> 00:22:35.438
But for example, regarding npm downloads,

00:22:35.438 --> 00:22:39.824
we're looking at less than
1 million weekly downloads

00:22:39.824 --> 00:22:42.159
for both those packages.

00:22:42.159 --> 00:22:47.162
Svelte has 0.8 million, and
SolidJS has 0.2 million.

00:22:49.063 --> 00:22:52.149
So 200,000 weekly downloads,

00:22:52.149 --> 00:22:55.351
which is way less than
the other frameworks had.

00:22:55.351 --> 00:22:58.119
And the same is true for job postings.

00:22:58.119 --> 00:23:01.205
There, I was only able to
find a couple of dozen,

00:23:01.205 --> 00:23:04.007
maybe hundreds, of job postings,

00:23:04.007 --> 00:23:06.642
but not the thousands of jobs you found

00:23:06.642 --> 00:23:08.326
for the other frameworks.

00:23:08.326 --> 00:23:10.695
And that's therefore the popularity

00:23:10.695 --> 00:23:13.747
of those frameworks and libraries.

00:23:13.747 --> 00:23:16.849
Now, another important decision factor,

00:23:16.849 --> 00:23:18.767
of course, is performance,

00:23:18.767 --> 00:23:21.252
because you wanna choose a technology

00:23:21.252 --> 00:23:24.937
that allows you to build
applications that perform well,

00:23:24.937 --> 00:23:27.256
that deliver great performance

00:23:27.256 --> 00:23:29.857
to your website visitors, for example.

00:23:29.857 --> 00:23:34.177
And here, the easy answer
is all these libraries

00:23:34.177 --> 00:23:36.995
and frameworks are extremely performant.

00:23:36.995 --> 00:23:41.448
You will always be able to
find specific niche cases

00:23:41.448 --> 00:23:44.267
or scenarios or optimization

00:23:44.267 --> 00:23:47.869
that make one framework stand out,

00:23:47.869 --> 00:23:50.288
but the main takeaway really

00:23:50.288 --> 00:23:53.323
is that they all got great performance.

00:23:53.323 --> 00:23:57.109
You find a link to a website
that runs some benchmarks

00:23:57.109 --> 00:24:00.261
across those frameworks, in the show notes

00:24:00.261 --> 00:24:01.595
or below the video.

00:24:01.595 --> 00:24:04.297
But in the end, it really is the case

00:24:04.297 --> 00:24:07.549
that you got great performance
for all those frameworks

00:24:07.549 --> 00:24:08.983
and libraries, and therefore,

00:24:08.983 --> 00:24:13.987
performance likely will not
be the most important factor

00:24:14.320 --> 00:24:18.673
when deciding for one of
those libraries or frameworks.

00:24:18.673 --> 00:24:23.026
Though it of course can
be in certain situations.

00:24:23.026 --> 00:24:29.564
Now, what might matter though,
is the way you write code

00:24:29.564 --> 00:24:31.265
and if you like the syntax

00:24:31.265 --> 00:24:34.667
and the the way of solving problems

00:24:34.667 --> 00:24:36.669
with those different libraries

00:24:36.669 --> 00:24:40.771
because they of course all
have their very own syntax

00:24:40.771 --> 00:24:44.691
and their very own way of writing code

00:24:44.691 --> 00:24:47.442
that you need to adapt if you're working

00:24:47.442 --> 00:24:50.294
with one of those libraries or frameworks.

00:24:50.294 --> 00:24:55.181
They all share the idea of
composing your user interface

00:24:55.181 --> 00:24:59.350
from components, from
reusable building blocks

00:24:59.350 --> 00:25:02.186
that contain the markup
that should be rendered

00:25:02.186 --> 00:25:05.805
and the logic that
might alter that markup.

00:25:05.805 --> 00:25:08.373
But the way you then
write those components

00:25:08.373 --> 00:25:10.992
and the way you manage your state

00:25:10.992 --> 00:25:14.894
that leads to UI updates, that differs.

00:25:14.894 --> 00:25:16.695
With React, for example,

00:25:16.695 --> 00:25:21.699
you write JavaScript functions,
and you use a feature

00:25:21.732 --> 00:25:26.435
called React Hooks to manage
some data in those functions,

00:25:26.435 --> 00:25:29.571
which will re-execute those
functions automatically

00:25:29.571 --> 00:25:32.389
when that data changes and so on.

00:25:32.389 --> 00:25:34.207
With Angular, on the other hand,

00:25:34.207 --> 00:25:38.810
you're working with classes,
and you work with decorators

00:25:38.810 --> 00:25:42.496
and extra template files, and it tends

00:25:42.496 --> 00:25:47.466
to require a bit more
boilerplate code than React,

00:25:47.466 --> 00:25:49.034
for example.

00:25:49.034 --> 00:25:52.369
In Vue, you have separate files,

00:25:52.369 --> 00:25:54.971
a separate file format, you could say,

00:25:54.971 --> 00:25:58.240
where you put your
components, their markup,

00:25:58.240 --> 00:26:01.475
their logic, and their
styling into those files,

00:26:01.475 --> 00:26:06.245
and you therefore then write
neither functions nor classes,

00:26:06.245 --> 00:26:09.697
but instead, you use this
separate file format.

00:26:09.764 --> 00:26:12.866
And in the end, it therefore comes down

00:26:12.866 --> 00:26:17.869
to personal preference, which
approach you like the most.

00:26:18.320 --> 00:26:21.539
You should really just
give all those libraries

00:26:21.539 --> 00:26:23.156
and frameworks a try.

00:26:23.156 --> 00:26:24.991
And with that, I don't mean

00:26:24.991 --> 00:26:28.944
that you should spend
multiple hours or even days

00:26:28.944 --> 00:26:32.179
on learning those different frameworks,

00:26:32.179 --> 00:26:35.331
but instead, just go through
their quick start guides

00:26:35.331 --> 00:26:39.000
on their websites, look up
some tutorials on YouTube

00:26:39.000 --> 00:26:43.737
and get an idea of how
you generally write code

00:26:43.737 --> 00:26:47.039
when working with those
libraries and frameworks.

00:26:47.039 --> 00:26:50.875
And then decide which
approach you like the most

00:26:50.875 --> 00:26:54.827
because there really is
no right or wrong here.

00:26:54.827 --> 00:26:59.481
You will read a lot of
strong opinions on X,

00:26:59.481 --> 00:27:03.166
Twitter in the past, and
in the internet in general.

00:27:03.166 --> 00:27:05.501
But let's be honest, strong opinions,

00:27:05.501 --> 00:27:08.270
we always have them in
the developer space.

00:27:08.270 --> 00:27:10.188
We especially have them on X,

00:27:10.188 --> 00:27:13.306
and often it's best to
just not care about them.

00:27:13.306 --> 00:27:15.558
So make your own choice there

00:27:15.558 --> 00:27:17.626
and find out what you like the most.

00:27:17.626 --> 00:27:20.211
Now, what I can say though,

00:27:20.211 --> 00:27:24.898
is how easy or difficult
it is for my experience

00:27:24.898 --> 00:27:28.016
to learn these different
libraries and frameworks.

00:27:28.016 --> 00:27:29.751
Because even though it comes down

00:27:29.751 --> 00:27:34.754
to your personal preferences,
whether you like the way

00:27:34.821 --> 00:27:38.206
of writing code in a given
library or framework,

00:27:38.206 --> 00:27:40.792
I can see from all the courses I created

00:27:40.792 --> 00:27:44.244
that they do have
different difficulty levels

00:27:44.244 --> 00:27:46.996
when it comes to learning
and mastering them.

00:27:46.996 --> 00:27:51.682
For example, Vue is a
framework that's pretty easy

00:27:51.682 --> 00:27:53.066
to get started with.

00:27:53.066 --> 00:27:55.618
It has a syntax and an approach

00:27:55.618 --> 00:27:57.920
that's not too difficult to understand.

00:27:57.920 --> 00:28:00.922
It doesn't require a
lot of boilerplate code,

00:28:00.922 --> 00:28:04.157
and it doesn't have too many pitfalls

00:28:04.157 --> 00:28:09.060
where you can write wrong code
that won't work as intended.

00:28:09.060 --> 00:28:10.278
You can of course do that,

00:28:10.278 --> 00:28:14.214
but it doesn't have too
many of those pitfalls.

00:28:14.214 --> 00:28:15.782
Angular, on the other hand,

00:28:15.782 --> 00:28:18.767
is relatively challenging to learn,

00:28:18.767 --> 00:28:21.452
though that has gotten a bit easier

00:28:21.452 --> 00:28:25.405
in recent years or months, you could say,

00:28:25.405 --> 00:28:29.491
because Angular actually
is innovating rapidly

00:28:29.491 --> 00:28:33.894
and is introducing new
alternative features,

00:28:33.894 --> 00:28:38.397
which make it a bit easier
to get started with Angular

00:28:38.397 --> 00:28:41.432
since less boilerplate code is required.

00:28:41.432 --> 00:28:44.667
It still requires a
decent bit of extra code,

00:28:44.667 --> 00:28:48.503
but it's gotten easier
over the years, I'd say.

00:28:48.503 --> 00:28:51.856
That being said, not all Angular projects

00:28:51.856 --> 00:28:54.107
are using those latest features.

00:28:54.107 --> 00:28:57.626
So chances are that when
you're learning Angular,

00:28:57.626 --> 00:29:00.545
you'll have to learn the more complex way

00:29:00.545 --> 00:29:03.480
of building Angular apps at some point,

00:29:03.480 --> 00:29:07.700
at least if you're looking
to find a job with Angular,

00:29:07.700 --> 00:29:10.168
because chances are high that there,

00:29:10.168 --> 00:29:14.154
you're not going to use
all those latest features.

00:29:14.154 --> 00:29:17.389
React, for example, is a bit easier

00:29:17.389 --> 00:29:19.374
to get started with, I'd say,

00:29:19.374 --> 00:29:23.543
because initially, it has
a simpler mental model

00:29:23.543 --> 00:29:27.179
and doesn't require as
much boilerplate code,

00:29:27.179 --> 00:29:30.865
but React has quite a few pitfalls.

00:29:30.865 --> 00:29:34.284
It's relatively easy if you're
getting started with React

00:29:34.284 --> 00:29:37.619
to write code that
doesn't work as intended

00:29:37.619 --> 00:29:40.688
in certain situations,
and it can then be hard

00:29:40.688 --> 00:29:44.157
to figure out why that's the case.

00:29:44.157 --> 00:29:46.942
It's also relatively easy
to run into some errors,

00:29:46.942 --> 00:29:50.128
which can be hard to understand initially.

00:29:50.128 --> 00:29:52.946
So React is maybe a bit easier

00:29:52.946 --> 00:29:57.566
to learn initially than
Angular, for example.

00:29:57.566 --> 00:30:00.001
But when it comes to mastering React

00:30:00.001 --> 00:30:03.837
and writing good React
code, I personally would say

00:30:03.837 --> 00:30:07.189
it's at least as challenging as Angular,

00:30:07.189 --> 00:30:08.907
which also is challenging there.

00:30:08.907 --> 00:30:12.359
But they're pretty equal there, I'd say.

00:30:12.359 --> 00:30:16.379
And for Svelte and SolidJS,
they're somewhere in between.

00:30:16.379 --> 00:30:19.664
In my personal experience,
they're not as easy to grasp

00:30:19.664 --> 00:30:22.916
and work with as Vue might be,

00:30:22.916 --> 00:30:25.668
but they're also not
as tricky or difficult

00:30:25.668 --> 00:30:29.037
as React or Angular can be.

00:30:29.037 --> 00:30:31.789
But again, here also, my recommendation

00:30:31.789 --> 00:30:34.291
is that you simply get started with them,

00:30:34.291 --> 00:30:36.776
that you go through
those quick start guides,

00:30:36.776 --> 00:30:40.111
that you maybe take a course
like one of my courses

00:30:40.111 --> 00:30:44.097
or any other course, and you
therefore then get a feeling

00:30:44.097 --> 00:30:47.550
for yourself how easy it is for you

00:30:47.550 --> 00:30:51.419
to get started with a
certain library or framework.

00:30:51.419 --> 00:30:54.504
Because even though I can
see some general trends,

00:30:54.504 --> 00:30:58.190
it of course always depends
on which prior experience

00:30:58.190 --> 00:31:01.309
you have and with which
average technologies

00:31:01.309 --> 00:31:03.210
you might have worked in the past.

00:31:03.210 --> 00:31:07.846
And that's there for this
pretty extensive overview

00:31:07.846 --> 00:31:10.915
of those different
frameworks and libraries.

00:31:10.915 --> 00:31:14.234
My thoughts on those
frameworks and libraries,

00:31:14.234 --> 00:31:16.219
which hopefully were helpful.

00:31:16.219 --> 00:31:18.737
And therefore, to conclude this here,

00:31:18.737 --> 00:31:22.756
I just wanna share what
my personal favorite is.

00:31:22.756 --> 00:31:26.576
And I would say that this
would probably be React

00:31:26.576 --> 00:31:29.778
but not because I like the way

00:31:29.778 --> 00:31:32.963
you write React code the most.

00:31:32.963 --> 00:31:34.614
I actually don't do that.

00:31:34.614 --> 00:31:39.167
It's okay, but I'm not a fan
of all the advanced things

00:31:39.167 --> 00:31:41.986
you need to know about
React and JavaScript

00:31:41.986 --> 00:31:44.387
in order to write good code.

00:31:44.387 --> 00:31:47.273
But instead, I tend to choose React

00:31:47.273 --> 00:31:49.558
for most of my new projects

00:31:49.558 --> 00:31:52.309
simply because of its popularity,

00:31:52.309 --> 00:31:55.245
because there is this vibrant ecosystem

00:31:55.245 --> 00:31:59.914
that you can use to find
solutions for specific problems

00:31:59.914 --> 00:32:03.050
you might be facing
when working with React

00:32:03.050 --> 00:32:06.502
and because we have those
full-stack libraries

00:32:06.502 --> 00:32:10.355
like Next.js and Remix,
which are relatively mature,

00:32:10.355 --> 00:32:13.607
and which simplify the process of building

00:32:13.607 --> 00:32:15.442
such full-stack applications,

00:32:15.442 --> 00:32:18.510
which I tend to do a lot as of late.

00:32:18.510 --> 00:32:21.145
But that's the reason why for me.

00:32:21.145 --> 00:32:24.481
If you would force me to
pick one, it would be React.

00:32:24.481 --> 00:32:27.266
But I do honestly like all of them,

00:32:27.266 --> 00:32:30.568
and I do enjoy every
project where I got a chance

00:32:30.568 --> 00:32:34.337
of working with Angular
or Vue, for example.