WEBVTT

00:00:00.000 --> 00:00:02.580
If you are a front-end JavaScript

00:00:02.580 --> 00:00:07.040
developer, you got plenty of options and

00:00:07.040 --> 00:00:07.920
alternatives.

00:00:08.400 --> 00:00:10.720
You got plenty of libraries and

00:00:10.720 --> 00:00:12.320
frameworks to choose from.

00:00:12.600 --> 00:00:15.400
You got React, Angular, and Vue to

00:00:15.400 --> 00:00:18.760
name the biggest, most popular ones.

00:00:19.020 --> 00:00:20.960
But you also got very popular

00:00:20.960 --> 00:00:24.640
alternatives like Svelte, or SolidJS, or

00:00:24.640 --> 00:00:25.400
Quik.

00:00:25.960 --> 00:00:27.920
And then you got other libraries like

00:00:27.920 --> 00:00:31.320
HTMX, where you wouldn't write a lot of

00:00:31.320 --> 00:00:33.820
JavaScript code, but which still uses

00:00:33.820 --> 00:00:35.100
JavaScript under the hood.

00:00:35.400 --> 00:00:38.960
So you got plenty of options if you want

00:00:38.960 --> 00:00:42.260
to build complex web user interfaces

00:00:42.260 --> 00:00:43.740
with help of JavaScript.

00:00:44.660 --> 00:00:47.240
And of course, it's easy to feel

00:00:47.240 --> 00:00:50.740
overwhelmed with all those options and

00:00:50.740 --> 00:00:51.660
alternatives.

00:00:52.060 --> 00:00:54.940
And the question is, how do you decide

00:00:54.940 --> 00:00:58.580
which of those frameworks or libraries

00:00:58.580 --> 00:01:00.500
you should learn and use?

00:01:00.760 --> 00:01:03.740
Do we have too many of those?

00:01:04.000 --> 00:01:08.660
Because I recall that when I released my

00:01:08.660 --> 00:01:13.500
Svelte course in 2019, so that is a couple

00:01:13.500 --> 00:01:16.680
of years ago, but still, when I released

00:01:16.680 --> 00:01:19.380
that course, I was quite positive

00:01:19.700 --> 00:01:20.740
regarding Svelte.

00:01:20.960 --> 00:01:22.740
And that course, it's a good course.

00:01:22.860 --> 00:01:23.780
It teaches Svelte.

00:01:23.940 --> 00:01:28.880
And Svelte is a really nice library, if you

00:01:28.880 --> 00:01:29.860
want to call it like this.

00:01:31.020 --> 00:01:33.460
So I was really happy with that course.

00:01:33.560 --> 00:01:37.560
And I was surprised that quite a decent

00:01:37.560 --> 00:01:40.340
chunk of all the feedback I got on that

00:01:40.340 --> 00:01:43.080
release was not about the course or

00:01:43.080 --> 00:01:44.380
about Svelte.

00:01:44.980 --> 00:01:49.040
It was about the fact that it's yet another

00:01:49.040 --> 00:01:52.060
course on yet another front-end

00:01:52.060 --> 00:01:55.060
JavaScript library or framework.

00:01:55.340 --> 00:01:59.220
And a decent chunk of my students or of

00:01:59.220 --> 00:02:02.900
the people who left feedback and left

00:02:02.900 --> 00:02:05.020
comments seemed to feel

00:02:05.020 --> 00:02:05.640
overwhelmed.

00:02:05.820 --> 00:02:08.940
And I would say annoyed by the fact that

00:02:08.940 --> 00:02:12.260
there is yet another JavaScript

00:02:12.260 --> 00:02:14.500
framework and library to learn.

00:02:15.220 --> 00:02:17.540
And I would say that's already the first

00:02:17.540 --> 00:02:17.960
problem.

00:02:18.120 --> 00:02:21.260
Also a problem on my part and maybe

00:02:21.260 --> 00:02:24.120
from the entire JavaScript ecosystem,

00:02:24.340 --> 00:02:26.620
but of course you don't have to learn it

00:02:26.620 --> 00:02:26.860
all.

00:02:27.040 --> 00:02:29.640
So if you feel like you have to learn it all,

00:02:29.800 --> 00:02:31.420
that's not the case.

00:02:31.740 --> 00:02:36.060
And people like me who create courses

00:02:36.060 --> 00:02:38.220
and content on all these different

00:02:38.160 --> 00:02:41.020
technologies can definitely give you the

00:02:41.020 --> 00:02:43.800
feeling that you need to learn all these

00:02:43.800 --> 00:02:44.440
things.

00:02:45.060 --> 00:02:49.260
But just because I like learning all these

00:02:49.260 --> 00:02:51.360
things and like working with all these

00:02:51.360 --> 00:02:54.240
things, and just because I create content

00:02:54.240 --> 00:02:56.800
on many of these libraries and

00:02:56.800 --> 00:02:59.600
frameworks to help people learn it, does

00:02:59.600 --> 00:03:02.220
not mean that you need to learn all

00:03:02.220 --> 00:03:03.900
these libraries and frameworks.

00:03:04.380 --> 00:03:06.980
And just because all these options exist

00:03:06.980 --> 00:03:10.440
and new frameworks and libraries keep

00:03:10.440 --> 00:03:13.040
popping up, does not mean that you

00:03:13.040 --> 00:03:15.580
have to learn or use them all.

00:03:16.000 --> 00:03:18.840
But I understand that it can sometimes

00:03:18.840 --> 00:03:22.440
feel as if you do have to do that.

00:03:22.660 --> 00:03:24.800
Because why do we have all these

00:03:24.800 --> 00:03:25.940
options to begin with?

00:03:26.400 --> 00:03:28.880
Why don't we just have one or two

00:03:28.960 --> 00:03:30.400
libraries or frameworks?

00:03:31.080 --> 00:03:35.160
Because to some extent that is the case,

00:03:35.540 --> 00:03:39.600
or is a bit more the case you could say, in

00:03:39.600 --> 00:03:42.500
backend web development I would

00:03:42.500 --> 00:03:42.960
argue.

00:03:43.440 --> 00:03:46.160
If you're using JavaScript for backend

00:03:46.160 --> 00:03:48.560
web development, you of course have a

00:03:48.560 --> 00:03:50.700
lot of frameworks and libraries you can

00:03:50.700 --> 00:03:51.360
use there.

00:03:51.740 --> 00:03:56.400
But the most used library still is

00:03:56.400 --> 00:03:59.980
Express.js, if you're working with Node.js.

00:04:00.500 --> 00:04:04.460
It gets millions of weekly downloads.

00:04:04.620 --> 00:04:07.480
It's super popular, even though it

00:04:07.480 --> 00:04:11.640
definitely has its issues and it's not under

00:04:11.640 --> 00:04:13.200
super active development.

00:04:13.600 --> 00:04:15.220
But maybe that's also the reason.

00:04:15.340 --> 00:04:18.100
It's very stable and people know it and

00:04:18.100 --> 00:04:20.220
therefore it's getting used by many

00:04:20.220 --> 00:04:21.959
projects and companies.

00:04:22.780 --> 00:04:25.160
And hence if you're working as a

00:04:25.160 --> 00:04:28.680
backend JavaScript developer, there's

00:04:28.680 --> 00:04:31.840
almost no way around Express.js.

00:04:32.260 --> 00:04:36.220
Of course you can learn one of the more

00:04:36.220 --> 00:04:38.860
modern alternatives and that might

00:04:38.860 --> 00:04:40.140
make a lot of sense.

00:04:40.640 --> 00:04:43.340
But if you want to land a job as a

00:04:43.340 --> 00:04:46.820
backend JavaScript developer, you very

00:04:46.820 --> 00:04:49.420
likely need to know Express.js.

00:04:50.200 --> 00:04:53.400
And it's kind of similar to some extent I

00:04:53.400 --> 00:04:56.780
would say, if you're working with PHP for

00:04:56.780 --> 00:04:57.300
example.

00:04:57.520 --> 00:05:00.580
Of course there are multiple libraries and

00:05:00.580 --> 00:05:02.620
frameworks to choose from there as well.

00:05:02.920 --> 00:05:06.620
But let's be honest, the clear winner in

00:05:06.620 --> 00:05:09.380
the PHP world is Laravel.

00:05:09.620 --> 00:05:13.180
If you want to work as a backend PHP

00:05:13.180 --> 00:05:16.880
developer, and now that I say it, I guess

00:05:16.880 --> 00:05:18.980
there are no frontend PHP developers.

00:05:19.180 --> 00:05:22.220
At least you don't use PHP for frontend

00:05:22.220 --> 00:05:22.760
code.

00:05:23.160 --> 00:05:25.380
But anyways, if you want to work as a

00:05:25.380 --> 00:05:28.500
PHP developer, you very likely need to

00:05:28.500 --> 00:05:29.340
know Laravel.

00:05:29.540 --> 00:05:32.420
It is the PHP framework.

00:05:32.720 --> 00:05:35.920
You could even argue that it made PHP

00:05:35.920 --> 00:05:39.820
popular again, if it ever was not popular.

00:05:40.240 --> 00:05:42.340
And that's also a topic for a different

00:05:42.340 --> 00:05:42.680
video.

00:05:43.040 --> 00:05:46.480
But Laravel is super important for PHP

00:05:46.480 --> 00:05:49.020
and therefore there as well.

00:05:49.180 --> 00:05:52.580
We don't have like five or six almost

00:05:52.580 --> 00:05:56.040
equally popular options as it seems to be

00:05:56.000 --> 00:05:58.420
in the frontend JavaScript world though.

00:05:59.080 --> 00:06:01.320
And of course there you could also argue

00:06:01.320 --> 00:06:04.720
that React is the most popular frontend

00:06:04.720 --> 00:06:06.060
JavaScript library.

00:06:06.300 --> 00:06:09.020
And then Angular is also pretty popular,

00:06:09.180 --> 00:06:12.560
especially also amongst enterprises and

00:06:12.560 --> 00:06:14.660
big companies as it seems.

00:06:14.940 --> 00:06:17.780
But you could argue that it's these two

00:06:17.780 --> 00:06:18.460
mostly.

00:06:18.640 --> 00:06:21.000
And if you just learn React and nothing

00:06:21.000 --> 00:06:23.600
else, you'll probably also be fine.

00:06:23.780 --> 00:06:27.420
And I tend to agree that probably is the

00:06:27.420 --> 00:06:27.680
case.

00:06:27.840 --> 00:06:30.140
But nonetheless, we have more options

00:06:30.140 --> 00:06:34.400
there and somehow every new option

00:06:34.400 --> 00:06:37.000
that appears, every new framework or

00:06:37.000 --> 00:06:39.560
library that appears in the frontend

00:06:39.560 --> 00:06:42.620
JavaScript world gets more attention

00:06:42.620 --> 00:06:45.960
than it seems to be the case for backend

00:06:45.960 --> 00:06:46.920
projects.

00:06:47.400 --> 00:06:52.480
And I'm not 100% sure why exactly that's

00:06:52.480 --> 00:06:54.320
the case and why that's happening.

00:06:54.500 --> 00:06:57.100
And I'm super interested in hearing your

00:06:57.100 --> 00:06:59.460
opinion and perspective on that.

00:06:59.560 --> 00:07:03.100
But I think that maybe we give more

00:07:03.100 --> 00:07:06.200
attention to every new frontend

00:07:06.200 --> 00:07:08.240
JavaScript framework or library that

00:07:08.240 --> 00:07:13.420
appears because a, there might be more

00:07:13.420 --> 00:07:16.040
frontend JavaScript developers than

00:07:16.040 --> 00:07:17.900
backend JavaScript developers.

00:07:18.060 --> 00:07:19.220
I'm not sure about that.

00:07:19.300 --> 00:07:20.680
I don't have any official numbers.

00:07:20.820 --> 00:07:22.980
It's just something that could be the

00:07:22.980 --> 00:07:23.360
case.

00:07:23.740 --> 00:07:27.100
And in addition, maybe frontend

00:07:27.100 --> 00:07:30.320
JavaScript development still has more

00:07:30.320 --> 00:07:34.440
unsolved problems or more problems

00:07:34.440 --> 00:07:37.580
that can be solved now that were harder

00:07:37.580 --> 00:07:39.240
to solve a couple of years ago.

00:07:39.420 --> 00:07:42.000
There may still be more progress

00:07:42.080 --> 00:07:45.180
regarding how certain problems could

00:07:45.180 --> 00:07:46.060
be tackled.

00:07:46.440 --> 00:07:49.060
It feels to me, and again, this is just a

00:07:49.060 --> 00:07:51.220
feeling, I could be wrong here, but it

00:07:51.220 --> 00:07:54.140
feels to me as if there's still a lot of

00:07:54.140 --> 00:07:56.740
innovation happening in the frontend

00:07:56.740 --> 00:07:58.280
JavaScript space.

00:07:59.060 --> 00:08:02.480
And that is not purely a positive thing

00:08:02.480 --> 00:08:04.520
because it also means that maybe there

00:08:04.520 --> 00:08:07.560
are more unsolved problems there than

00:08:07.560 --> 00:08:08.320
on the backend.

00:08:09.160 --> 00:08:13.580
It also feels like we move a bit in circles

00:08:13.580 --> 00:08:16.360
in the frontend JavaScript world.

00:08:16.620 --> 00:08:19.460
I mean, we're coming from a world

00:08:19.460 --> 00:08:23.080
where we built websites, web

00:08:23.080 --> 00:08:26.540
applications that worked such that we

00:08:26.540 --> 00:08:28.800
had some backend code that rendered

00:08:28.800 --> 00:08:31.720
an HTML page, an HTML document and

00:08:31.720 --> 00:08:33.140
sent that to the browser.

00:08:33.659 --> 00:08:36.240
And then maybe that document also

00:08:36.240 --> 00:08:39.039
loaded some script code to add some

00:08:39.039 --> 00:08:40.740
interactivity to that page.

00:08:41.360 --> 00:08:44.880
And then we had all those frameworks

00:08:44.880 --> 00:08:48.260
taking over the frontend and we started

00:08:48.260 --> 00:08:50.080
building single page applications

00:08:50.080 --> 00:08:52.700
because they also solve a problem.

00:08:53.040 --> 00:08:56.020
They allow us to build more interactive

00:08:56.020 --> 00:08:57.740
frontend applications.

00:08:58.060 --> 00:09:01.820
They allow us to give users a more

00:09:01.820 --> 00:09:06.740
interactive feeling with our websites.

00:09:06.880 --> 00:09:10.180
They can make websites feel like

00:09:10.180 --> 00:09:13.120
desktop or mobile applications, even.

00:09:13.420 --> 00:09:15.120
So they exist for a reason.

00:09:15.840 --> 00:09:19.620
But now we're moving back to a world

00:09:19.620 --> 00:09:22.140
where we also render a lot on the server.

00:09:22.360 --> 00:09:27.160
And currently there is this trend in

00:09:27.280 --> 00:09:30.080
frontend JavaScript development where

00:09:30.080 --> 00:09:33.720
we try to blend these two worlds, these

00:09:33.720 --> 00:09:35.720
two ends, the backend at the frontend,

00:09:35.880 --> 00:09:38.820
and where we try to get the best of both

00:09:38.820 --> 00:09:39.320
worlds.

00:09:39.580 --> 00:09:42.400
And I did talk about that in separate

00:09:42.400 --> 00:09:45.980
videos and episodes, so I'll not reiterate it

00:09:45.980 --> 00:09:50.580
here, but that seems to be the future we

00:09:50.580 --> 00:09:53.500
seem to be moving towards with

00:09:53.500 --> 00:09:54.800
frontend JavaScript.

00:09:55.600 --> 00:09:58.880
And maybe that's also why we see so

00:09:58.880 --> 00:10:02.580
many libraries and frameworks pop up

00:10:02.580 --> 00:10:07.260
because it's clear that we're not there

00:10:07.260 --> 00:10:07.860
yet.

00:10:08.060 --> 00:10:10.820
There are some problems and there

00:10:10.820 --> 00:10:13.740
were problems with the way we built

00:10:13.740 --> 00:10:16.080
frontends five years ago.

00:10:16.240 --> 00:10:19.000
So maybe that's why we see all that

00:10:19.000 --> 00:10:21.000
innovation and all those different

00:10:21.000 --> 00:10:23.280
libraries and frameworks pop up.

00:10:23.840 --> 00:10:25.440
Maybe that's the case.

00:10:25.600 --> 00:10:27.940
But what does that now mean for

00:10:27.940 --> 00:10:28.840
developers?

00:10:29.580 --> 00:10:32.320
Do you have to learn all these different

00:10:32.320 --> 00:10:32.840
options?

00:10:33.060 --> 00:10:36.180
How can you make sure that you don't

00:10:36.180 --> 00:10:38.820
feel overwhelmed by all these different

00:10:38.820 --> 00:10:39.360
options?

00:10:39.520 --> 00:10:43.640
And I can only say you don't have to

00:10:43.640 --> 00:10:44.620
learn them all.

00:10:45.020 --> 00:10:48.520
You can just stick with the option you

00:10:48.520 --> 00:10:51.800
personally like the most or with the

00:10:51.800 --> 00:10:54.380
framework or library you want to learn

00:10:54.380 --> 00:10:56.440
because it gives you the best

00:10:56.440 --> 00:10:58.700
perspectives on the job market or

00:10:58.700 --> 00:11:00.480
because you may be needed in your

00:11:00.480 --> 00:11:01.680
existing job.

00:11:01.840 --> 00:11:04.460
You can't just learn React or Angular or

00:11:04.460 --> 00:11:06.300
Vue and call it a day.

00:11:06.400 --> 00:11:07.900
You don't need to know them all.

00:11:08.560 --> 00:11:11.140
But I would recommend that you at

00:11:11.140 --> 00:11:14.040
least take a look at multiple options

00:11:14.240 --> 00:11:17.240
simply to find out which of those options

00:11:17.240 --> 00:11:21.440
you like the most and also to stay in the

00:11:21.440 --> 00:11:24.280
loop regarding the innovation that's

00:11:24.280 --> 00:11:26.720
happening in the frontend JavaScript

00:11:26.720 --> 00:11:27.320
world.

00:11:27.760 --> 00:11:30.720
That does not mean that you have to use

00:11:30.720 --> 00:11:33.640
all those latest features and concepts

00:11:33.640 --> 00:11:35.580
right when they come out.

00:11:35.680 --> 00:11:37.920
Indeed, I would recommend that you

00:11:37.920 --> 00:11:41.940
always wait a bit until you use some new

00:11:41.940 --> 00:11:45.120
library or framework or feature of a

00:11:45.120 --> 00:11:48.680
library or framework in a real app until

00:11:48.680 --> 00:11:50.780
it's polished and battle-tested.

00:11:51.200 --> 00:11:53.800
I would recommend that you don't start

00:11:53.800 --> 00:11:56.200
using all the latest libraries and features

00:11:56.200 --> 00:11:58.780
immediately in your production apps

00:11:58.780 --> 00:12:01.900
because that can lead to problems and

00:12:01.900 --> 00:12:05.260
we've seen that in multiple libraries and

00:12:05.260 --> 00:12:07.000
frameworks in the last years as well.

00:12:07.200 --> 00:12:10.860
It makes sense to wait and you don't

00:12:10.860 --> 00:12:13.380
have to learn everything at the point of

00:12:13.380 --> 00:12:15.920
time where it comes out but keeping an

00:12:15.920 --> 00:12:18.400
open mind and just staying informed

00:12:18.400 --> 00:12:20.100
about some general trends and

00:12:20.100 --> 00:12:23.360
developments I guess makes sense and

00:12:23.360 --> 00:12:25.900
at the same time this approach also

00:12:25.900 --> 00:12:28.620
ensures that you hopefully don't feel

00:12:28.620 --> 00:12:32.440
overwhelmed and that you can see all

00:12:32.440 --> 00:12:35.040
these different alternatives and options

00:12:35.040 --> 00:12:39.380
as something positive because it is that

00:12:39.380 --> 00:12:40.100
innovation.

00:12:40.420 --> 00:12:43.040
It is the appearance of all these different

00:12:43.040 --> 00:12:44.960
libraries and frameworks and features

00:12:44.960 --> 00:12:48.120
and the evolution of existing libraries

00:12:48.120 --> 00:12:51.840
and frameworks that drives the overall

00:12:51.840 --> 00:12:55.060
frontend JavaScript ecosystem forward

00:12:55.060 --> 00:12:58.880
and that ensures that we'll hopefully

00:12:58.880 --> 00:13:02.800
reach a point where we are at least very

00:13:02.800 --> 00:13:05.660
close to having the best of both worlds

00:13:05.660 --> 00:13:07.880
and where we maybe have a great way

00:13:07.880 --> 00:13:09.720
of merging backend and frontend

00:13:10.160 --> 00:13:12.480
because there is one big advantage

00:13:12.480 --> 00:13:16.840
JavaScript has over PHP for example and

00:13:16.840 --> 00:13:20.000
that is that it can run both on the server

00:13:20.000 --> 00:13:24.460
side and in the browser and that holds a

00:13:24.460 --> 00:13:28.420
lot of potential because that indeed can

00:13:28.420 --> 00:13:32.380
allow us to build web applications where

00:13:32.380 --> 00:13:34.860
backend and frontend are integrated

00:13:34.860 --> 00:13:38.160
seamlessly and where we therefore can

00:13:38.160 --> 00:13:41.300
give our website users a great user

00:13:41.300 --> 00:13:44.640
experience because ultimately that's the

00:13:44.640 --> 00:13:45.680
main goal.

00:13:46.220 --> 00:13:48.940
As a web developer no matter which

00:13:48.940 --> 00:13:51.740
technology you're using you have to

00:13:51.740 --> 00:13:53.780
build websites and web applications

00:13:53.780 --> 00:13:57.440
that give their users a great user

00:13:57.440 --> 00:14:02.260
experience and that do their job so that

00:14:02.260 --> 00:14:04.920
if you build an online shop it's an online

00:14:04.920 --> 00:14:06.200
shop that's easy to use.

00:14:06.540 --> 00:14:09.600
If you're building a complex web app like

00:14:09.600 --> 00:14:13.140
Google Sheets or something like that

00:14:13.140 --> 00:14:15.980
you build it such that it's easy to use that

00:14:15.980 --> 00:14:19.160
it's performant that it's intuitive that's

00:14:19.160 --> 00:14:22.060
your main job and all that innovation

00:14:22.060 --> 00:14:25.400
that's happening in the JavaScript world

00:14:25.400 --> 00:14:27.540
in the frontend JavaScript world

00:14:27.540 --> 00:14:31.720
hopefully helps with making that job a

00:14:31.720 --> 00:14:34.520
bit easier and a bit more pleasant but

00:14:34.520 --> 00:14:37.260
there is no reason to feel overwhelmed

00:14:37.260 --> 00:14:38.940
at least in my opinion.