WEBVTT

00:00:00.000 --> 00:00:05.120
So Angular 18 was released and for React

00:00:05.120 --> 00:00:09.240
the version 19 release candidate was

00:00:09.240 --> 00:00:12.660
announced at ReactConf and it's

00:00:12.660 --> 00:00:15.580
definitely interesting to have these big

00:00:15.580 --> 00:00:19.580
new major releases for two of the

00:00:19.580 --> 00:00:21.840
biggest web development frameworks

00:00:21.840 --> 00:00:24.360
front-end web development frameworks

00:00:24.360 --> 00:00:28.180
one should probably say side by side so

00:00:28.180 --> 00:00:30.580
close to each other because that of

00:00:30.580 --> 00:00:32.580
course has not always been the case.

00:00:33.320 --> 00:00:36.220
Angular essentially releases a new major

00:00:36.220 --> 00:00:40.160
version every six months and React has

00:00:40.160 --> 00:00:41.300
no fixed schedule.

00:00:41.740 --> 00:00:45.220
Indeed React 18 which was the last

00:00:45.220 --> 00:00:49.160
major version before React 19 was

00:00:49.160 --> 00:00:53.900
released in 2022 so over two years ago

00:00:53.900 --> 00:00:55.960
now but now we have these two big

00:00:55.960 --> 00:00:58.800
new versions even though React 19 isn't

00:00:58.800 --> 00:01:02.720
stable yet but soon and the question is

00:01:02.720 --> 00:01:05.379
what does this mean for us and the

00:01:05.379 --> 00:01:07.740
answers can already be found in many

00:01:07.740 --> 00:01:10.700
articles and videos the short summary is

00:01:10.700 --> 00:01:14.300
that both versions don't change

00:01:14.300 --> 00:01:17.100
everything don't force you to rewrite

00:01:17.100 --> 00:01:19.760
your code or anything like that even

00:01:19.760 --> 00:01:21.960
though you could think that they do if

00:01:21.840 --> 00:01:24.060
you read some comments but hey it's

00:01:24.060 --> 00:01:27.240
the internet so of course it is like that but

00:01:27.240 --> 00:01:29.320
in the end if we maybe start with

00:01:29.320 --> 00:01:34.060
Angular 18 I have to be careful to not mix

00:01:34.060 --> 00:01:36.460
up these version numbers Angular 18

00:01:36.460 --> 00:01:40.640
brings some much needed stability I

00:01:40.640 --> 00:01:44.240
would say whilst still continuing its

00:01:44.240 --> 00:01:47.340
innovation path if you want to call it like

00:01:47.340 --> 00:01:51.140
this Angular 18 now marks the new

00:01:51.140 --> 00:01:53.700
control flow syntax as stable the

00:01:53.700 --> 00:01:56.400
deferrable views as stable but at the

00:01:56.400 --> 00:02:00.000
same time new signals related APIs were

00:02:00.000 --> 00:02:02.340
added though technically those were

00:02:02.340 --> 00:02:05.840
already added with Angular 17 minor

00:02:05.840 --> 00:02:09.660
versions of Angular 17 I guess but there

00:02:09.600 --> 00:02:11.700
aren't these big groundbreaking

00:02:11.700 --> 00:02:14.960
changes now with Angular 18 instead

00:02:14.960 --> 00:02:17.700
they're just taking more small steps into

00:02:17.700 --> 00:02:20.660
the right direction whilst and that's also

00:02:20.660 --> 00:02:24.140
important of course also supporting the

00:02:24.140 --> 00:02:27.340
old Angular you don't have to use signals

00:02:27.340 --> 00:02:29.700
you don't have to use these new features

00:02:29.700 --> 00:02:31.980
if you don't want to that's super

00:02:31.980 --> 00:02:34.080
important obviously also to them

00:02:34.080 --> 00:02:37.560
because the Angular framework

00:02:37.560 --> 00:02:41.200
landscape also is a bit fragmented not all

00:02:41.200 --> 00:02:43.320
projects use the latest version indeed

00:02:43.320 --> 00:02:46.340
there are projects that still use rather old

00:02:46.340 --> 00:02:50.080
versions so that's that but Angular 18

00:02:50.080 --> 00:02:52.120
therefore is another new major version

00:02:52.120 --> 00:02:54.040
which adds some new features but

00:02:54.040 --> 00:02:55.740
which brings some much needed

00:02:55.740 --> 00:02:58.600
stability at least in my opinion which is

00:02:58.600 --> 00:03:01.340
also why I took it as an opportunity to

00:03:01.340 --> 00:03:04.500
release a big course update with more to

00:03:04.500 --> 00:03:09.380
come now react 19 is kind of similar and

00:03:09.380 --> 00:03:12.280
then it's not I guess it's complicated

00:03:12.280 --> 00:03:16.600
because react 19 in most projects

00:03:16.600 --> 00:03:21.240
doesn't add too much new stuff not too

00:03:21.240 --> 00:03:23.680
many new features there isn't

00:03:23.680 --> 00:03:25.580
something groundbreaking new like

00:03:25.580 --> 00:03:27.940
react hooks instead there are small

00:03:27.940 --> 00:03:30.960
quality of life improvements I'd say like

00:03:30.960 --> 00:03:33.480
the fact that you can provide context

00:03:33.480 --> 00:03:36.260
with the context object itself now

00:03:36.260 --> 00:03:38.400
instead of that nested provider or

00:03:38.400 --> 00:03:41.020
component or the fact that you can

00:03:41.020 --> 00:03:44.720
finally use refs on your own components

00:03:44.720 --> 00:03:46.980
without using forward ref you can

00:03:46.980 --> 00:03:49.660
simply accept them as regular props

00:03:49.660 --> 00:03:52.100
and use them as such that's great that's

00:03:52.100 --> 00:03:54.960
actually a big useful change but it's not

00:03:54.960 --> 00:03:57.520
a big change regarding the code you

00:03:57.520 --> 00:03:59.660
write it's just making your code a bit

00:03:59.660 --> 00:04:02.560
easier and using forward ref and that old

00:04:02.560 --> 00:04:06.400
approach also still works so nothing too

00:04:06.400 --> 00:04:08.680
fancy there a bit more interesting

00:04:08.680 --> 00:04:11.460
maybe form actions a new way of

00:04:11.460 --> 00:04:13.820
handling form submissions that's now

00:04:13.820 --> 00:04:17.120
offered by react basically now it has a

00:04:17.120 --> 00:04:18.839
built-in way of handling form

00:04:18.839 --> 00:04:21.380
submissions that's interesting and

00:04:21.380 --> 00:04:24.440
definitely something to to take a look at

00:04:24.440 --> 00:04:27.360
once it's out but also nothing you have

00:04:27.360 --> 00:04:30.200
to use the the most interesting parts I

00:04:30.200 --> 00:04:32.780
guess are react server components

00:04:32.780 --> 00:04:35.860
server actions and the new use hook

00:04:35.860 --> 00:04:38.880
and the funny thing regarding these

00:04:38.880 --> 00:04:42.340
features is that in most react projects I

00:04:42.340 --> 00:04:45.280
guess you can't use them you can't use

00:04:45.280 --> 00:04:47.920
them in vit based projects at least react

00:04:47.920 --> 00:04:50.100
server components and server actions

00:04:50.100 --> 00:04:53.480
can't be used there unless you make

00:04:53.480 --> 00:04:56.380
sure that you edit and adjust your

00:04:56.380 --> 00:04:58.980
project such that these features are

00:04:58.980 --> 00:05:01.820
supported which is not necessarily trivial

00:05:01.820 --> 00:05:05.220
because these are features which as

00:05:05.220 --> 00:05:07.040
their name kind of implies server

00:05:07.040 --> 00:05:09.420
components server actions which

00:05:09.420 --> 00:05:12.060
require a server or which at least don't

00:05:12.060 --> 00:05:14.240
run on the client side they need to run

00:05:14.240 --> 00:05:16.400
somewhere else on a server or at build

00:05:16.400 --> 00:05:19.340
time and therefore you need a project

00:05:19.340 --> 00:05:21.400
setup that provides such an

00:05:21.400 --> 00:05:24.480
environment also in production and that

00:05:24.480 --> 00:05:26.920
splits the code appropriately so that

00:05:26.920 --> 00:05:29.620
server side code doesn't end up in the

00:05:29.620 --> 00:05:32.420
client side bundle and vice versa but

00:05:32.420 --> 00:05:34.660
most of all it's important that the server

00:05:34.660 --> 00:05:37.320
code doesn't go to the client side and

00:05:37.320 --> 00:05:39.880
therefore these features are part of react

00:05:39.880 --> 00:05:43.300
19 they're stable though they'll still keep

00:05:43.300 --> 00:05:45.480
on working on it but they are there now

00:05:45.480 --> 00:05:47.980
but you can't just use them instead you

00:05:47.980 --> 00:05:50.300
need projects that support these

00:05:50.300 --> 00:05:54.640
features and at the moment that mostly

00:05:54.640 --> 00:05:59.680
still means next.js it won't stay that way

00:05:59.680 --> 00:06:01.580
and of course you could set up your own

00:06:01.580 --> 00:06:04.200
projects there are other projects out

00:06:04.200 --> 00:06:06.360
there as well other frameworks remix

00:06:06.360 --> 00:06:09.600
will eventually support react server

00:06:09.600 --> 00:06:12.760
components though it's not really called

00:06:12.760 --> 00:06:14.960
remix anymore but I'll create a separate

00:06:14.960 --> 00:06:16.900
video on that but at the moment it

00:06:16.900 --> 00:06:19.700
mostly is next.js at least that's the

00:06:19.700 --> 00:06:22.300
biggest framework that supports these

00:06:22.300 --> 00:06:24.520
features and that has supported them

00:06:24.520 --> 00:06:27.360
already over the last year because next.js

00:06:27.360 --> 00:06:30.340
used that experimental react version

00:06:30.340 --> 00:06:33.240
under the hood now it can use the react

00:06:33.240 --> 00:06:35.480
19 version since now these features are

00:06:35.480 --> 00:06:37.660
built in there so that's nice but it doesn't

00:06:37.660 --> 00:06:39.360
change too much for you as a developer

00:06:39.360 --> 00:06:42.460
and the use hook is also kind of tricky

00:06:42.460 --> 00:06:45.020
because you can use it to read context

00:06:45.020 --> 00:06:47.600
that's great but you can also use it on

00:06:47.600 --> 00:06:50.260
promises but not on promises created

00:06:50.260 --> 00:06:52.980
by you in your component but instead

00:06:52.980 --> 00:06:56.460
on promises that are either created in a

00:06:56.460 --> 00:06:58.460
server component and passed to the

00:06:58.460 --> 00:07:00.940
client component or on promises that

00:07:00.940 --> 00:07:03.380
come from libraries that integrate with

00:07:03.380 --> 00:07:05.820
react suspense so I guess you get my

00:07:05.820 --> 00:07:09.320
point it's non-trivial now that's not

00:07:09.320 --> 00:07:13.320
necessarily bad I'd say because the the

00:07:13.320 --> 00:07:16.460
upside of course is that react does give

00:07:16.460 --> 00:07:18.420
us a lot of features which we can use

00:07:18.420 --> 00:07:21.880
implicitly I guess through libraries and

00:07:21.880 --> 00:07:24.780
through frameworks that make building

00:07:24.780 --> 00:07:27.340
more complex projects and full stack

00:07:27.340 --> 00:07:30.340
applications easier because the idea

00:07:30.340 --> 00:07:32.260
behind react server components and

00:07:32.260 --> 00:07:35.060
server actions is pretty intriguing at least

00:07:35.060 --> 00:07:38.700
to me and working with next.js besides

00:07:38.700 --> 00:07:41.340
all the things that are not great about it

00:07:41.340 --> 00:07:45.460
I'd say is indeed pretty nice building full

00:07:45.460 --> 00:07:48.500
stack apps with react and next.js is

00:07:48.500 --> 00:07:51.100
definitely something I want to do and

00:07:51.100 --> 00:07:54.620
therefore both releases react 19 and

00:07:54.620 --> 00:07:58.660
angular 18 are in my opinion huge steps

00:07:58.660 --> 00:08:02.340
in the right direction and they do offer

00:08:02.340 --> 00:08:05.180
new feature or in angular's case offer

00:08:05.180 --> 00:08:07.820
smaller new features and stabilize

00:08:07.820 --> 00:08:11.440
important new features but they do that

00:08:11.440 --> 00:08:13.540
without changing the way you write

00:08:13.540 --> 00:08:16.360
your code and in react's case it offers

00:08:16.360 --> 00:08:18.160
new features which you might not be

00:08:18.160 --> 00:08:20.060
able to use but if you are able to use

00:08:20.060 --> 00:08:23.420
them then they can be really useful and

00:08:23.420 --> 00:08:25.800
therefore it's definitely an interesting

00:08:25.800 --> 00:08:29.080
development quite different from what

00:08:29.080 --> 00:08:31.180
was the standard a couple of years ago

00:08:31.180 --> 00:08:31.660
I'd say.

00:08:32.120 --> 00:08:35.280
I remember when react hooks were

00:08:35.280 --> 00:08:40.539
introduced with 16.8 I think that really

00:08:40.539 --> 00:08:43.200
changed the way we write react code

00:08:43.200 --> 00:08:45.200
and you could use it in every react

00:08:45.200 --> 00:08:49.480
project and that's now not like this in the

00:08:49.480 --> 00:08:50.240
react world.

00:08:50.520 --> 00:08:52.620
In the angular world on the other hand

00:08:52.980 --> 00:08:55.560
we're taking a short break now before

00:08:55.560 --> 00:08:58.740
we'll probably see more new features

00:08:58.740 --> 00:09:01.340
but we already got a lot of new features

00:09:01.340 --> 00:09:03.720
over the last couple of months and years

00:09:03.720 --> 00:09:06.900
there so that angular today is quite

00:09:06.900 --> 00:09:09.180
different from what it was two years ago

00:09:09.180 --> 00:09:11.980
and therefore definitely interesting

00:09:11.980 --> 00:09:15.960
times to live in two big frameworks with

00:09:15.960 --> 00:09:19.400
two pretty interesting releases that do

00:09:19.400 --> 00:09:22.380
offer interesting new features that can

00:09:22.380 --> 00:09:24.760
definitely become very useful in future

00:09:24.760 --> 00:09:28.600
projects but obviously that's just my take

00:09:28.600 --> 00:09:30.600
on it and I also don't know what will

00:09:30.600 --> 00:09:32.620
happen in the future so what do you

00:09:32.620 --> 00:09:32.880
think?

00:09:33.100 --> 00:09:35.080
What do you think about react 19,

00:09:35.300 --> 00:09:36.080
angular 18?

00:09:36.520 --> 00:09:38.540
You might not care at all, definitely let

00:09:38.540 --> 00:09:41.120
me know, but definitely even more so let

00:09:41.120 --> 00:09:43.180
me know if you do care and let me know

00:09:43.180 --> 00:09:45.280
what you think about these releases.