WEBVTT

00:00:00.000 --> 00:00:04.100
Are meta frameworks like Next, Remix,

00:00:04.300 --> 00:00:08.760
AnalogJS or Nuxt, are those the future of

00:00:08.760 --> 00:00:09.540
web development?

00:00:10.000 --> 00:00:13.500
Should every web developer use those

00:00:13.500 --> 00:00:15.940
meta frameworks and learn how to build

00:00:15.940 --> 00:00:18.120
full stack applications with them?

00:00:18.780 --> 00:00:22.460
Well, I think if you are working with

00:00:22.460 --> 00:00:26.840
React or Angular or Vue, yes, you should

00:00:26.840 --> 00:00:29.240
definitely learn those meta frameworks

00:00:29.240 --> 00:00:33.100
because I believe they are the future of

00:00:33.100 --> 00:00:34.820
React and Angular and so on.

00:00:35.060 --> 00:00:37.900
Well, especially for React and I'll get back

00:00:37.900 --> 00:00:39.260
to that in a second.

00:00:39.960 --> 00:00:43.840
But I believe they are the future of those

00:00:43.840 --> 00:00:46.460
frontend libraries and frameworks

00:00:46.460 --> 00:00:48.840
because they solve an important

00:00:48.840 --> 00:00:49.460
problem.

00:00:50.180 --> 00:00:52.220
When we build a website, a web

00:00:52.220 --> 00:00:55.320
application, we typically don't just need

00:00:55.320 --> 00:00:58.080
a frontend, we also need a backend and

00:00:58.080 --> 00:01:00.460
that of course has always been the case

00:01:00.460 --> 00:01:04.360
and we were able to build websites and

00:01:04.360 --> 00:01:06.920
web applications that have both a

00:01:06.920 --> 00:01:09.480
frontend and a backend without those

00:01:09.480 --> 00:01:11.280
meta frameworks as well, right?

00:01:11.700 --> 00:01:15.180
I mean, you could simply build a

00:01:15.180 --> 00:01:17.840
frontend single page application, for

00:01:17.840 --> 00:01:21.380
example, with React and then connect

00:01:21.380 --> 00:01:24.540
it, so to say, to a backend that's built with

00:01:24.540 --> 00:01:25.280
Node and Express.

00:01:25.780 --> 00:01:27.600
So you could build such a backend API,

00:01:28.180 --> 00:01:30.720
typically a REST API, but could also be a

00:01:30.720 --> 00:01:34.920
GraphQL API and then you could send

00:01:34.920 --> 00:01:38.260
requests to that backend from inside the

00:01:38.260 --> 00:01:41.200
frontend application, for example, with

00:01:41.200 --> 00:01:44.040
help of React Query, which is a popular

00:01:44.040 --> 00:01:47.180
library for doing that, or simply by using

00:01:47.180 --> 00:01:49.680
the Fetch API inside of UseEffect, for

00:01:49.680 --> 00:01:52.440
example, or in Angular by using

00:01:52.480 --> 00:01:54.900
Angular's built-in HTTP client.

00:01:55.640 --> 00:01:58.200
And then you could fetch data from the

00:01:58.200 --> 00:02:01.060
backend or send data to that backend

00:02:01.060 --> 00:02:03.800
and update the frontend UI accordingly

00:02:03.800 --> 00:02:07.160
to, for example, show that data or if data

00:02:07.160 --> 00:02:09.460
was sent to show a success message.

00:02:09.940 --> 00:02:12.740
We don't need those meta frameworks

00:02:12.740 --> 00:02:14.280
like Next for that.

00:02:21.680 --> 00:02:16.020
That's absolutely not the case.

00:02:16.740 --> 00:02:20.180
But those meta frameworks like Next or

00:02:20.180 --> 00:02:23.320
Remix and so on can make building

00:02:23.320 --> 00:02:26.920
complex full-stack applications, so

00:02:26.920 --> 00:02:29.340
where you have both the frontend and

00:02:29.340 --> 00:02:32.260
the backend, simply a bit easier and

00:02:32.260 --> 00:02:34.020
solve certain problems.

00:02:34.220 --> 00:02:36.160
And that's their huge advantage.

00:02:36.720 --> 00:02:39.840
And they do make that easier and solve

00:02:39.840 --> 00:02:42.640
certain problems by giving you a

00:02:42.640 --> 00:02:46.240
seamless integration, by blending

00:02:46.240 --> 00:02:48.980
frontend and backend code with each

00:02:48.980 --> 00:02:50.160
other, so to say.

00:02:50.560 --> 00:02:53.260
That can also lead to new problems

00:02:53.260 --> 00:02:56.220
because as a developer, you should

00:02:56.220 --> 00:02:59.700
absolutely understand where exactly the

00:02:59.700 --> 00:03:01.720
border is between backend and

00:03:01.720 --> 00:03:03.640
frontend code so that you make sure

00:03:03.640 --> 00:03:06.360
that the wrong code doesn't end up on

00:03:06.240 --> 00:03:07.140
the wrong end.

00:03:07.620 --> 00:03:11.140
But mostly, it can help get rid of certain

00:03:11.140 --> 00:03:13.180
problems or simply make it a bit easier

00:03:13.180 --> 00:03:14.880
to write complex applications.

00:03:15.260 --> 00:03:17.140
Because, for example, when you're

00:03:17.140 --> 00:03:19.360
working with Next.js, but also with

00:03:19.360 --> 00:03:22.640
Remix and so on, you can effectively

00:03:22.640 --> 00:03:26.720
fetch data from right inside your React

00:03:26.720 --> 00:03:28.040
component, for example.

00:03:28.640 --> 00:03:31.460
Or with Remix, you would do it in a

00:03:31.460 --> 00:03:34.080
separate function which is placed close

00:03:34.080 --> 00:03:35.700
to your component typically, though.

00:03:36.040 --> 00:03:39.080
You could fetch data from there and

00:03:39.080 --> 00:03:43.160
then render your HTML code with help

00:03:43.160 --> 00:03:46.760
of React that's already including that

00:03:46.760 --> 00:03:47.460
fetched data.

00:03:47.600 --> 00:03:49.560
And all that would happen on the server

00:03:49.560 --> 00:03:52.100
and the advantage of that would be that

00:03:52.100 --> 00:03:56.020
the user, the client, receives the finished

00:03:56.020 --> 00:03:56.940
web page.

00:03:57.120 --> 00:04:00.060
So it gets back a response from the

00:04:00.060 --> 00:04:03.080
server that already contains all the

00:04:03.080 --> 00:04:06.120
markup with all the content that's

00:04:06.120 --> 00:04:09.080
needed for the page that was requested.

00:04:09.900 --> 00:04:12.360
And that, for example, is great for search

00:04:12.360 --> 00:04:14.740
engine optimization because those

00:04:14.740 --> 00:04:19.060
search engine crawlers then also see all

00:04:19.060 --> 00:04:21.360
the content and see the finished page.

00:04:21.839 --> 00:04:24.780
Whereas with traditional single page

00:04:24.780 --> 00:04:27.600
applications, that page that's coming

00:04:27.600 --> 00:04:30.340
back from a server would typically be

00:04:30.340 --> 00:04:33.500
empty and contain no content because

00:04:33.500 --> 00:04:36.400
that content would have been fetched

00:04:36.400 --> 00:04:38.900
from inside the browser with help of

00:04:38.900 --> 00:04:41.020
client-side JavaScript code.

00:04:41.880 --> 00:04:44.400
And whilst to the user that might not

00:04:44.400 --> 00:04:46.620
make that much of a difference because

00:04:46.620 --> 00:04:49.560
fetching that data often is pretty quick, it

00:04:49.560 --> 00:04:52.260
still can because they might temporarily

00:04:52.260 --> 00:04:55.200
see some loading spinner or some

00:04:55.200 --> 00:04:57.620
progress bar whilst they're waiting for

00:04:57.620 --> 00:04:57.980
the data.

00:04:58.100 --> 00:04:59.120
So it can be annoying.

00:04:59.400 --> 00:05:02.480
But what's even worse is that all those

00:05:02.480 --> 00:05:05.180
search engine crawlers would see an

00:05:05.180 --> 00:05:05.940
empty page.

00:05:06.400 --> 00:05:09.200
And that can really hurt your search

00:05:09.200 --> 00:05:12.820
rankings because to those crawlers, your

00:05:12.820 --> 00:05:14.760
page doesn't have any content.

00:05:15.080 --> 00:05:18.080
So that's one important problem that's,

00:05:18.220 --> 00:05:20.840
for example, solved by that seamless

00:05:20.840 --> 00:05:24.180
integration of frontend and backend and

00:05:24.180 --> 00:05:26.360
by blending that code and blending

00:05:26.360 --> 00:05:28.320
those two ends, so to say.

00:05:28.640 --> 00:05:31.320
Another thing that can get easier and

00:05:31.320 --> 00:05:34.080
possibly also more secure would be

00:05:34.080 --> 00:05:36.580
authentication because we can, of

00:05:36.580 --> 00:05:39.980
course, also authenticate users when

00:05:39.980 --> 00:05:42.480
building separated frontends and

00:05:42.480 --> 00:05:43.000
backends.

00:05:43.200 --> 00:05:45.780
For example, with JSON web tokens,

00:05:45.920 --> 00:05:47.700
that would be a popular approach.

00:05:48.380 --> 00:05:51.460
But that approach also has certain

00:05:51.460 --> 00:05:52.420
disadvantages.

00:05:53.120 --> 00:05:56.360
For example, that those tokens are then

00:05:56.360 --> 00:05:58.960
the only thing that identifies a user.

00:05:59.480 --> 00:06:02.820
And if for some reason, such a token

00:06:02.820 --> 00:06:06.160
would get stolen, if an attacker could get

00:06:06.160 --> 00:06:09.380
hold of such a token of an authenticated

00:06:09.380 --> 00:06:12.500
user, they could basically assume their

00:06:12.500 --> 00:06:16.080
identity and then send requests on

00:06:16.080 --> 00:06:17.200
behalf of that user.

00:06:17.700 --> 00:06:19.660
Now, there are defense mechanisms

00:06:19.660 --> 00:06:20.420
against that.

00:06:20.860 --> 00:06:23.120
For example, those tokens are typically

00:06:23.120 --> 00:06:26.140
short lived to make sure that if they do

00:06:26.140 --> 00:06:29.600
get stolen, they are not available for a

00:06:29.600 --> 00:06:30.420
long time period.

00:06:30.680 --> 00:06:33.020
But still, it can be a problem.

00:06:33.460 --> 00:06:35.700
And if you have a seamless integration,

00:06:36.160 --> 00:06:38.020
implementing session based

00:06:38.020 --> 00:06:40.700
authentication, where the

00:06:40.700 --> 00:06:43.540
authentication status is stored on the

00:06:43.540 --> 00:06:45.180
server instead of the client,

00:06:45.900 --> 00:06:48.300
implementing that is easier.

00:06:48.600 --> 00:06:51.420
And that can also add an extra layer of

00:06:51.420 --> 00:06:52.000
security.

00:06:52.280 --> 00:06:54.760
It can also be easier than implementing

00:06:54.760 --> 00:06:57.060
authentication tokens, JSON web

00:06:57.060 --> 00:06:59.520
tokens, and storing them on the client.

00:06:59.900 --> 00:07:02.900
So that's another area where those meta

00:07:02.900 --> 00:07:04.720
frameworks and that seamless

00:07:04.720 --> 00:07:07.500
integration of backend and frontend can

00:07:07.500 --> 00:07:10.740
potentially solve certain problems, or at

00:07:10.740 --> 00:07:13.940
least make certain common things like

00:07:13.940 --> 00:07:16.780
user authentication easier and

00:07:16.780 --> 00:07:18.240
straightforward to implement.

00:07:18.520 --> 00:07:20.500
And that, of course, can be a great thing.

00:07:21.060 --> 00:07:23.820
There also is another advantage I see

00:07:23.820 --> 00:07:25.880
when using such meta frameworks.

00:07:26.380 --> 00:07:30.300
And that would be that since you are in

00:07:30.300 --> 00:07:33.940
the end blending those ends, you can

00:07:33.940 --> 00:07:36.580
still use all the knowledge you have

00:07:36.580 --> 00:07:40.280
about React or Vue or Angular to render

00:07:40.280 --> 00:07:41.320
the user interface.

00:07:41.600 --> 00:07:43.880
And you can still add all that client side

00:07:43.880 --> 00:07:45.700
interactivity you want to add.

00:07:45.860 --> 00:07:48.080
Because the great thing about those

00:07:48.000 --> 00:07:51.340
meta frameworks is that once they did

00:07:51.340 --> 00:07:54.180
send back that first response that

00:07:54.180 --> 00:07:56.360
contains all the content already, as I

00:07:56.360 --> 00:07:59.220
described, once that happened, it's

00:07:59.220 --> 00:08:02.040
again client side JavaScript that takes

00:08:02.040 --> 00:08:05.260
over and in the end gives the user this

00:08:05.260 --> 00:08:08.160
single page application experience

00:08:08.160 --> 00:08:11.160
again, where everything on the page is

00:08:11.160 --> 00:08:13.940
again updated by client side JavaScript

00:08:13.940 --> 00:08:14.520
code.

00:08:14.680 --> 00:08:17.760
And behind the scenes new data or new

00:08:17.760 --> 00:08:20.580
HTML code is fetched from the backend.

00:08:21.040 --> 00:08:23.860
But as a user of the website, you still

00:08:23.860 --> 00:08:26.880
have all the instant transitions and the

00:08:26.880 --> 00:08:29.900
great user experience you often get from

00:08:29.900 --> 00:08:31.280
single page applications.

00:08:31.800 --> 00:08:35.159
So you keep those advantages, but you

00:08:35.159 --> 00:08:37.600
enrich them with more advantages.

00:08:38.480 --> 00:08:41.039
And of course, since you have that

00:08:41.039 --> 00:08:44.800
seamless integration, you do render all

00:08:44.800 --> 00:08:47.120
the content that's being sent back from

00:08:47.120 --> 00:08:49.540
the backend to the frontend on that first

00:08:49.540 --> 00:08:49.980
request.

00:08:50.360 --> 00:08:53.320
You do that all with the templating

00:08:53.320 --> 00:08:56.040
language you already know and love.

00:08:56.280 --> 00:08:59.580
So with JSX, for example, if you're using

00:08:59.580 --> 00:09:03.740
React, you don't have to use a separate

00:09:04.000 --> 00:09:06.800
templating language to dynamically

00:09:06.800 --> 00:09:09.580
generate HTML code on the server.

00:09:10.120 --> 00:09:12.580
And that is what you would typically do

00:09:12.580 --> 00:09:16.180
when building backends that send back

00:09:16.180 --> 00:09:19.480
HTML instead of just data without such a

00:09:19.480 --> 00:09:20.060
meta framework.

00:09:20.580 --> 00:09:23.380
If you would build a backend with, for

00:09:23.380 --> 00:09:28.140
example, Node.js and Express, as many

00:09:28.140 --> 00:09:30.720
companies still do it because it is a fine

00:09:30.720 --> 00:09:33.920
way, then you would typically either

00:09:33.920 --> 00:09:37.520
create an API, a REST API, for example,

00:09:37.880 --> 00:09:39.780
that's then used by a separated

00:09:39.780 --> 00:09:40.420
frontend.

00:09:40.860 --> 00:09:42.820
But if you want to build an integrated

00:09:42.820 --> 00:09:45.700
full stack application without such a

00:09:45.700 --> 00:09:48.300
meta framework, you would typically do

00:09:48.300 --> 00:09:51.640
that by using a templating engine on

00:09:51.640 --> 00:09:54.440
the backend in that Node Express code.

00:09:54.980 --> 00:09:58.020
And here you have popular options like

00:09:58.020 --> 00:10:01.240
EJS or handlebars and so on.

00:10:01.560 --> 00:10:04.840
But these are all separate templating

00:10:04.840 --> 00:10:07.080
engines you have to learn so that you

00:10:07.080 --> 00:10:09.540
understand how you can use them to

00:10:09.540 --> 00:10:11.300
render the content you want to render.

00:10:11.680 --> 00:10:14.120
So it's an extra thing to learn.

00:10:14.520 --> 00:10:16.560
And then if you want to add client-side

00:10:16.560 --> 00:10:20.500
interactivity, you have to add React or

00:10:20.500 --> 00:10:22.900
Vue as an extra dependency to that

00:10:22.900 --> 00:10:26.180
project and manually write all the code

00:10:26.180 --> 00:10:29.900
that makes sure that it takes over once

00:10:29.900 --> 00:10:31.880
the page has been loaded in the

00:10:31.880 --> 00:10:33.180
browser of your visitor.

00:10:33.620 --> 00:10:36.300
And you manually have to set up all the

00:10:36.300 --> 00:10:39.680
extra API endpoints, which then could

00:10:39.680 --> 00:10:43.400
be used by that frontend library if it

00:10:43.400 --> 00:10:46.240
wants to fetch or send new data after

00:10:46.240 --> 00:10:48.220
that initial first page load.

00:10:48.420 --> 00:10:50.420
So that would be more complex than

00:10:50.420 --> 00:10:51.960
using such a meta framework.

00:10:52.700 --> 00:10:55.580
And for all those reasons, I think that if

00:10:55.580 --> 00:10:58.460
you want to build a full stack application

00:10:58.460 --> 00:11:01.360
that has all the advantages you know

00:11:01.360 --> 00:11:04.220
from working with React or Angular or

00:11:04.220 --> 00:11:07.420
Node, if you want to do that, then

00:11:07.420 --> 00:11:10.300
picking up such a meta framework is

00:11:10.300 --> 00:11:12.540
really important and a good idea.

00:11:13.400 --> 00:11:15.760
Now, it's also worth noting, though, that

00:11:15.760 --> 00:11:19.140
we're still in the early days of this entire

00:11:19.140 --> 00:11:23.380
development and evolution of frontend

00:11:23.380 --> 00:11:25.020
web development, if you want to call it

00:11:25.020 --> 00:11:25.620
like that.

00:11:26.060 --> 00:11:29.880
Of course, Next.js, for example, which is

00:11:29.880 --> 00:11:32.740
arguably the most important and

00:11:32.740 --> 00:11:36.140
popular meta framework for React, has

00:11:36.140 --> 00:11:38.600
already been around for many years, but

00:11:38.600 --> 00:11:41.960
it's only been recently for one and a half

00:11:41.960 --> 00:11:46.000
years or probably two years now that

00:11:46.000 --> 00:11:49.800
they really moved quickly towards that

00:11:49.800 --> 00:11:52.960
integrated approach and towards a

00:11:52.960 --> 00:11:55.100
world where the frontend and backend

00:11:55.100 --> 00:11:58.160
code blend together and blend into

00:11:58.160 --> 00:11:59.180
each other, so to say.

00:11:59.280 --> 00:12:01.740
That's a relatively new development.

00:12:02.080 --> 00:12:04.820
And it is a development which we now

00:12:04.820 --> 00:12:08.240
see in other meta frameworks as well.

00:12:08.560 --> 00:12:10.820
But it's still pretty new and therefore, of

00:12:10.820 --> 00:12:14.440
course, there still are some rough edges

00:12:14.440 --> 00:12:17.340
and some new patterns to be learned

00:12:17.340 --> 00:12:20.640
and some things to be understood to, for

00:12:20.640 --> 00:12:22.780
example, make sure, as I mentioned

00:12:22.780 --> 00:12:25.900
before, that your code doesn't end up on

00:12:25.900 --> 00:12:27.700
the wrong end and you're getting

00:12:27.700 --> 00:12:31.240
strange bugs or you're exposing data in

00:12:31.240 --> 00:12:32.940
places where it shouldn't be exposed.

00:12:33.280 --> 00:12:36.720
So there also are pitfalls related to that,

00:12:37.100 --> 00:12:39.360
also because it is so new.

00:12:39.800 --> 00:12:43.400
But ultimately, as always in the world of

00:12:43.400 --> 00:12:45.480
programming, things will, of course,

00:12:45.480 --> 00:12:48.000
become better and smoother and

00:12:48.000 --> 00:12:50.300
patterns will emerge and certain

00:12:50.300 --> 00:12:51.800
problems will disappear.

00:12:52.180 --> 00:12:53.840
Well, and I guess new problems will

00:12:53.840 --> 00:12:56.020
appear, but you get my point.

00:12:56.300 --> 00:12:59.560
I think we're definitely heading towards

00:12:59.560 --> 00:13:01.880
such a world where those meta

00:13:01.880 --> 00:13:04.180
frameworks will be super important,

00:13:04.740 --> 00:13:07.740
though I will also say that this is still just

00:13:07.740 --> 00:13:10.940
one area of web development.

00:13:11.580 --> 00:13:15.220
We absolutely still have those separated

00:13:15.220 --> 00:13:18.100
frontend and backend applications and

00:13:18.100 --> 00:13:21.320
we absolutely still have full stack

00:13:21.320 --> 00:13:24.120
applications where HTML code is

00:13:24.080 --> 00:13:26.600
rendered on the server with help of

00:13:26.600 --> 00:13:29.620
templating engines like EJS or, for

00:13:29.620 --> 00:13:33.920
example, in PHP-based backends with

00:13:33.920 --> 00:13:35.660
Laravel's Blade engine.

00:13:36.080 --> 00:13:38.500
So we definitely have those applications

00:13:38.500 --> 00:13:41.560
as well and actually those websites and

00:13:41.560 --> 00:13:43.840
applications are the majority.

00:13:44.240 --> 00:13:46.180
So it's always important to keep in mind

00:13:46.400 --> 00:13:50.220
that we're in a niche here, nonetheless in

00:13:50.220 --> 00:13:53.020
an important niche, which I believe will

00:13:53.020 --> 00:13:55.660
grow because it offers certain

00:13:55.660 --> 00:13:56.320
advantages.

00:13:57.100 --> 00:13:58.800
And the advantage is that we have the

00:13:58.800 --> 00:14:02.260
best of both worlds, that single page

00:14:02.260 --> 00:14:04.980
application experience, the great user

00:14:04.980 --> 00:14:07.120
experience offered by that, combined

00:14:07.120 --> 00:14:09.460
with all the advantages of rendering

00:14:09.460 --> 00:14:11.920
content on the server and having such

00:14:11.920 --> 00:14:13.600
full stack applications.

00:14:15.060 --> 00:14:18.080
Now, as mentioned, Next.js is arguably

00:14:18.080 --> 00:14:20.440
the most popular and important meta

00:14:20.440 --> 00:14:23.340
framework, but for React we, for

00:14:23.340 --> 00:14:26.180
example, also have Remix, which is a

00:14:26.180 --> 00:14:28.680
competitor to Next.js, if you want to call

00:14:28.680 --> 00:14:31.180
it like this, which is also growing in

00:14:31.180 --> 00:14:32.980
popularity and becoming more and

00:14:32.980 --> 00:14:36.120
more important and which offers, in my

00:14:36.120 --> 00:14:39.180
opinion, certain advantages over Next.js,

00:14:39.480 --> 00:14:42.380
though that probably would be a topic

00:14:42.380 --> 00:14:45.140
for a separate episode or video.

00:14:45.700 --> 00:14:47.920
Nonetheless, you have these two options

00:14:47.920 --> 00:14:51.080
and if you are working with React, I

00:14:51.080 --> 00:14:52.900
would simply recommend that you take

00:14:52.900 --> 00:14:55.400
a look at both meta frameworks and you

00:14:55.400 --> 00:14:58.260
go through their quick start guides to

00:14:58.260 --> 00:15:00.360
see which one you like the most, for

00:15:00.360 --> 00:15:00.900
example.

00:15:01.680 --> 00:15:04.100
Now, if you're an Angular developer,

00:15:04.500 --> 00:15:06.120
there are less choices.

00:15:06.820 --> 00:15:09.720
Here you basically have analog.js and

00:15:09.720 --> 00:15:13.660
this is a project which, as far as I can tell,

00:15:13.780 --> 00:15:17.000
is a bit less mature than Next.js or

00:15:17.000 --> 00:15:17.580
Remix.

00:15:17.860 --> 00:15:20.460
It doesn't have the same set of features

00:15:20.460 --> 00:15:23.260
and it has certain limitations, also

00:15:23.260 --> 00:15:25.320
because it's mainly developed by just

00:15:25.320 --> 00:15:26.280
one person.

00:15:26.780 --> 00:15:29.680
Though I believe that meta frameworks

00:15:29.680 --> 00:15:33.040
will be and will mostly become so

00:15:33.040 --> 00:15:35.780
important that we'll see more

00:15:35.780 --> 00:15:38.340
development in that area in the Angular

00:15:38.340 --> 00:15:39.500
world as well.

00:15:40.120 --> 00:15:42.500
Maybe because the Angular team

00:15:42.500 --> 00:15:45.680
makes analog.js or something like that

00:15:45.680 --> 00:15:49.220
an official extension of the Angular

00:15:49.220 --> 00:15:51.460
framework, so we might see more

00:15:51.460 --> 00:15:53.300
development because of that or

00:15:53.300 --> 00:15:55.580
because more community projects

00:15:55.580 --> 00:15:56.220
come up.

00:15:56.680 --> 00:15:59.360
Now, if you're a Vue developer, things are

00:15:59.360 --> 00:16:01.880
actually different because there we do

00:16:01.880 --> 00:16:05.100
have a very popular and successful meta

00:16:05.100 --> 00:16:08.300
framework called Next.js and it's been

00:16:08.300 --> 00:16:11.740
around since 2017, I think, so it's really

00:16:11.740 --> 00:16:14.240
old by now but of course it has also

00:16:14.240 --> 00:16:17.280
evolved over all that time and I would

00:16:17.280 --> 00:16:20.200
say it's pretty comparable to Next.js

00:16:20.200 --> 00:16:22.780
regarding its maturity, for example.

00:16:23.360 --> 00:16:26.240
Now, it works differently but the main

00:16:26.240 --> 00:16:28.520
idea is the same, that you can build

00:16:28.520 --> 00:16:31.720
full-stack applications with Vue and that

00:16:31.720 --> 00:16:33.780
you can blend back-end and front-end

00:16:33.780 --> 00:16:36.020
and it has many features that help you

00:16:36.020 --> 00:16:38.000
with that and that help you with

00:16:38.000 --> 00:16:42.540
building complex and user-friendly web

00:16:42.540 --> 00:16:45.060
applications and websites in general.

00:16:45.580 --> 00:16:48.260
And therefore, as web developers, we

00:16:48.260 --> 00:16:50.540
now essentially have one additional

00:16:50.540 --> 00:16:54.060
option where besides traditional

00:16:54.060 --> 00:16:57.240
full-stack applications where we, for

00:16:57.240 --> 00:16:59.640
example, use Node, Express and then a

00:16:59.640 --> 00:17:03.100
templating engine like EJS or separated

00:17:03.100 --> 00:17:05.900
front-ends and back-ends, we now also

00:17:05.900 --> 00:17:08.740
have that very intriguing option of

00:17:08.740 --> 00:17:11.400
building full-stack applications where

00:17:11.400 --> 00:17:13.599
we get the best of both worlds by

00:17:13.599 --> 00:17:16.500
seamlessly integrating and blending

00:17:16.500 --> 00:17:19.780
front-end and back-end with those meta

00:17:19.780 --> 00:17:20.359
frameworks.

00:17:20.819 --> 00:17:22.980
And of course, we have those rough

00:17:22.980 --> 00:17:25.520
edges you should be aware of and you

00:17:25.520 --> 00:17:28.740
should expect but those will absolutely

00:17:28.740 --> 00:17:31.640
become smoother in the future and

00:17:31.640 --> 00:17:34.020
therefore, I'm convinced that every

00:17:34.020 --> 00:17:37.180
React, Angular or Vue developer should

00:17:37.180 --> 00:17:40.180
also at least take a look at those meta

00:17:40.180 --> 00:17:40.600
frameworks.