WEBVTT

00:00:00.000 --> 00:00:10.440
Speaker 0: Last week we had Svelket III and Solid II being released as release candidates, so not fully stable yet but almost.

00:00:10.980 --> 00:00:14.860
Speaker 0: And a couple of years ago this would have been an interesting thing.

00:00:15.060 --> 00:00:19.920
Speaker 0: you would've seen a bunch videos about it including by me off course maybe even a chorus.

00:00:21.240 --> 00:00:24.700
Speaker 0: And the question nowadays is, does that still matter?

00:00:24.840 --> 00:00:30.720
Speaker 0: Do new frameworks still matter at all or a new framework versions as we have it here.

00:00:31.280 --> 00:00:32.420
Speaker 0: Or does it not matter?

00:00:32.520 --> 00:00:37.800
Speaker 0: because with AI It's all about react anyways right and why would you even care?

00:00:38.120 --> 00:00:46.360
Speaker 0: I mean if AI writes so much code maybe all your code Why Would You Care About The Underlying Framework Or Library?

00:00:46.940 --> 00:00:49.320
Speaker 0: And I'd say you should care quite a bit.

00:00:49.540 --> 00:00:59.000
Speaker 0: and new frameworks or libraries do matter, but of course gaining traction is much harder than it used to be.

00:01:02.820 --> 00:01:04.920
Speaker 0: but it may be worse now.

00:01:05.060 --> 00:01:06.500
Speaker 0: But let's dig in!

00:01:07.020 --> 00:01:22.000
Speaker 0: Now I will not take a closer look at what exactly these frameworks or versions are about, we'll link the official announcements and blog posts though so you can dive into that... ...but i will say both are pretty interesting indeed.

00:01:32.580 --> 00:01:33.880
Speaker 0: it works with AI.

00:01:34.420 --> 00:01:55.000
Speaker 0: Because that is important, one reason against these new frameworks or the importance of new frameworks to speak against would be that AI has a favorite stack and that of course reacts etc.

00:01:55.920 --> 00:01:56.680
Speaker 0: And that's true.

00:01:58.360 --> 00:02:12.140
Speaker 0: but AI is pretty good at working with new unknown things too, as it turns out if you as the developer give it a right context and that's not to be underestimated.

00:02:12.540 --> 00:02:28.660
Speaker 0: Of course if your just vibing away & you're not steering AI in any way If you're vibe coding, which can be fine for certain one-off projects or throwaway software.

00:02:28.900 --> 00:02:37.240
Speaker 0: But if your doing that then of course yeah it'll not know what SvelteKit version three is necessarily and YOU wouldn't care about it!

00:02:37.300 --> 00:02:39.980
Speaker 0: You woudn't even tell AI to use that version.

00:02:40.060 --> 00:02:46.440
Speaker 0: so obviously new frameworks don't have a place in THAT world.

00:02:49.980 --> 00:03:07.260
Speaker 0: place and I don't know which role vibe coding will play in a few years, but right now you can definitely get a lot out of actually steering AI.

00:03:07.400 --> 00:03:07.860
Speaker 0: That's kind.

00:03:12.220 --> 00:03:14.860
Speaker 0: Our role as developers simply is changing.

00:03:15.200 --> 00:03:29.580
Speaker 0: We still should be controlling what we build and how we built it, And that we don't write the code anymore necessarily does not mean That we should not care about The code the architecture the decisions we make.

00:03:29.760 --> 00:03:34.580
Speaker 0: that Is As important as ever or maybe more Important than ever before.

00:03:34.880 --> 00:03:45.800
Speaker 0: I think the reasons for picking a framework over another are different now You know, back in two thousand nineteen and so on.

00:03:46.920 --> 00:03:54.340
Speaker 0: one major reason for picking a certain framework amongst others of course was the developer experience.

00:03:54.800 --> 00:03:58.000
Speaker 0: Do you have a good time working with it as a developer?

00:03:58.180 --> 00:03:59.300
Speaker 0: Obviously that mattered!

00:03:59.660 --> 00:04:09.720
Speaker 0: You don't always have that choice.

00:04:09.800 --> 00:04:28.360
Speaker 0: You may be employed somewhere where you are simply forced to use a certain framework or library, but as a developer depending on the company where your working and especially of course if yourself employed ,you can have some leverage in how decisions are made.

00:04:32.060 --> 00:04:41.240
Speaker 0: a framework has good developer ergonomics, if it offers a good developer experience.

00:04:41.300 --> 00:04:42.780
Speaker 0: That was not the only thing of course.

00:04:42.860 --> 00:04:43.280
Speaker 0: back then.

00:04:43.480 --> 00:04:45.120
Speaker 0: already performance mattered.

00:04:45.240 --> 00:04:48.900
Speaker 0: bundle size mattered than there are other things that may matter.

00:04:49.040 --> 00:05:05.500
Speaker 0: for example how easy or hard is to do service at rendering with aspects are less important now.

00:05:05.940 --> 00:05:09.640
Speaker 0: I would say developer experience doesn't really matter anymore!

00:05:10.140 --> 00:05:15.380
Speaker 0: Now what will matter is the AI experience, i don't know... What we call that?

00:05:15.440 --> 00:05:16.060
Speaker 0: Is it AX?

00:05:16.740 --> 00:05:27.020
Speaker 0: That of course matters a lot and things like the performance and the bundle size and all that stuff also still matters of course.

00:05:28.640 --> 00:05:42.800
Speaker 0: And I would argue You could say with AI now, because AI is so fast at spitting out code obviously it may actually matter less which framework you use.

00:05:43.140 --> 00:05:52.740
Speaker 0: Switching is easier than it used to be and you can therefore really see... And take a look at Which aspects matter for the app?

00:05:52.840 --> 00:06:00.340
Speaker 0: The project your working on what's most important for you framework or library for that and just use it.

00:06:00.400 --> 00:06:03.500
Speaker 0: And you don't have to care about developer experience, or anything like that?

00:06:03.820 --> 00:06:07.740
Speaker 0: I would say You Don't even Have To Care As Much About The Ecosystem Anymore!

00:06:07.840 --> 00:06:10.180
Speaker 0: The ecosystem Of Course Still Matters.

00:06:10.320 --> 00:06:11.560
Speaker 0: It Is A Factor.

00:06:11.680 --> 00:06:17.620
Speaker 0: For Example If Your Working With React You're Obviously Buying Into A Huge Ecosystem.

00:06:17.700 --> 00:06:32.940
Speaker 0: You Have Shad CN You Have A Bunch of Other Libraries But One Aspect That Matters Less Of course unfortunate for me, but that matters less is the amount of tutorials you have on a technology because again You may not be writing to code yourself anymore.

00:06:33.320 --> 00:06:34.240
Speaker 0: So that's one aspect.

00:06:34.280 --> 00:06:35.680
Speaker 0: That's not as important any more.

00:06:35.760 --> 00:06:39.220
Speaker 0: and also The other part of ecosystem the libraries and so on.

00:06:39.540 --> 00:06:46.360
Speaker 0: yeah sure It's nice to have that But AI it pretty good at just building whatever you wanted to build.

00:06:46.440 --> 00:06:50.700
Speaker 0: And if YOU want your own Shazian for Svelte?

00:06:51.700 --> 00:06:53.840
Speaker 0: There already is a Schatzi and Forsweld.

00:06:54.100 --> 00:07:02.440
Speaker 0: But if you wanted to build your own version of the library that exists for React but not for your favorite framework, You can just ask AI to do it!

00:07:02.840 --> 00:07:11.940
Speaker 0: You Can Just Ask AI To Fork Some Popular React Library And Port It To Your Favorite Framework Now.

00:07:12.060 --> 00:07:17.160
Speaker 0: That Will Not Be Worth The Effort For Every Little Site Demo Project You're Building Before Bigger Projects.

00:07:17.240 --> 00:07:18.520
Speaker 0: It Very Well May be.

00:07:19.360 --> 00:07:21.360
Speaker 0: you can do stuff like that.

00:07:21.840 --> 00:07:28.860
Speaker 0: So actually, I would say the ecosystem still matters but is less important than it used to be now.

00:07:29.100 --> 00:07:33.480
Speaker 0: what matters though and i mentioned this before Is the AI experience?

00:07:33.520 --> 00:07:35.480
Speaker 0: You could say in What Do I mean with That?

00:07:36.820 --> 00:07:39.060
Speaker 0: There are probably different things you Could Mean Here.

00:07:39.120 --> 00:07:54.220
Speaker 0: what I mean is how easy is It for AI To learn or understand The Thing the Framework the Library you Wanted to work With And How much does this framework force AI to write good code?

00:07:54.260 --> 00:07:55.400
Speaker 0: and I'll give you an example.

00:07:55.600 --> 00:07:57.620
Speaker 0: There is a fact now effect.

00:07:57.720 --> 00:08:08.500
Speaker 0: Is not a JavaScript front-end framework, but it nonetheless is a JavaScript or a typescript library Designed to help developers easily create complex synchronous and asynchronous programs.

00:08:08.760 --> 00:08:10.620
Speaker 0: You can for example use it on the back end.

00:08:10.860 --> 00:08:12.100
Speaker 0: It has a bunch of stuff included.

00:08:12.140 --> 00:08:16.140
Speaker 0: This really amazing And one thing that makes a factory may be amazing.

00:08:17.060 --> 00:08:35.740
Speaker 0: Probably one of the reasons why it is popular in a certain niche right now at least, Is that fact comes with a lot of rules That are actively enforced and will yell at you if your or DAI Are writing the wrong code.

00:08:35.799 --> 00:08:54.220
Speaker 0: If you're violating certain rules Of the effect library because its a typescript library It heavily embraces type script A lot of other stuff that can really force you to follow a certain set of rules, to write your programs in a certain way.

00:08:54.620 --> 00:09:09.080
Speaker 0: And when working with AI anything that enforces rules and yells at AI if it invents stuff or tries Anything like that can be good.

00:09:09.140 --> 00:09:12.560
Speaker 0: and thats one aspect of a good AI experience I would say.

00:09:12.960 --> 00:09:25.720
Speaker 0: Working with a library or framework, that enforces certain rules And that basically minimizes the amount of mistakes you can make or the amount off variants.

00:09:25.900 --> 00:09:29.200
Speaker 0: You could have in your code if you want to put it like dad, so let's one aspect.

00:09:29.600 --> 00:09:44.160
Speaker 0: The other aspect is how easy it is for AI to learn something and here It's Of course all about the docs because I mentioned earlier That with a eye You have something that is pretty good at working with new unknown things too.

00:09:44.800 --> 00:10:08.020
Speaker 0: Sure, it has all the baked in knowledge about React but to some degree you could even argue this was a bad thing because they learned a lot of bad patterns from these public repositories... But you just point AI on the right docs pages or give them the right skill And it can do pretty, pretty well at working with a certain technology.

00:10:08.200 --> 00:10:09.320
Speaker 0: I'm doing that all the time!

00:10:14.000 --> 00:10:30.340
Speaker 0: the docs, or what I like to do.

00:10:55.140 --> 00:10:57.320
Speaker 0: but the reasons shifted to some degree.

00:10:58.320 --> 00:11:06.040
Speaker 0: As mentioned, things like performance and so on will always matter because ultimately you're hopefully building products for The End User!

00:11:06.180 --> 00:11:10.840
Speaker 0: And The End user could be YOU if it's an internal tool or something like that.

00:11:10.920 --> 00:11:14.740
Speaker 0: But still... You want Something That Is Fast It Doesn't Crash All The Time.

00:11:15.040 --> 00:11:16.380
Speaker 0: So THAT ALL MATTERS.

00:11:16.740 --> 00:11:24.960
Speaker 0: But then in addition to that, what matters today is how well does a certain framework or library work with AI?

00:11:25.060 --> 00:11:26.260
Speaker 0: And of course changes.

00:11:26.960 --> 00:11:34.160
Speaker 0: How these frameworks and libraries are developed or should be developed and What the priorities of the developers behind this framework should be.

00:11:34.600 --> 00:11:43.080
Speaker 0: they should really try to build something That forces AI to work in a certain way and that minimizes The amount of mistakes I can make.

00:11:43.760 --> 00:11:53.520
Speaker 0: because Ultimately, what we're trying to do here is force a non-deterministic thing into kind of a deterministic world.

00:11:53.800 --> 00:11:55.320
Speaker 0: To get the best of both worlds!

00:11:55.380 --> 00:12:03.280
Speaker 0: To get flexibility and speed but avoid it going rogue and spitting out horrible code.

00:12:04.000 --> 00:12:08.560
Speaker 0: And yeah... New frameworks & libraries play an important role here.

00:12:11.040 --> 00:12:14.260
Speaker 0: Learning these frameworks and libraries certainly has changed.

00:12:14.840 --> 00:12:23.260
Speaker 0: You as a developer will most likely not spend hours on A huge course to learn a new framework or library.

00:12:24.020 --> 00:12:34.300
Speaker 0: you Will probably, And you should probably I certainly do Spend some time To pick up the basics with The docs With a YouTube video with a chorus.

00:12:34.760 --> 00:12:36.500
Speaker 0: of course that is also changing.

00:12:36.720 --> 00:12:37.360
Speaker 0: i'm Changing what?

00:12:37.460 --> 00:12:42.540
Speaker 0: I am producing because in order to efficiently work with something.

00:12:42.600 --> 00:12:49.160
Speaker 0: No matter what it is, through AI you need a basic understanding of the... thing you're working with.

00:12:49.240 --> 00:12:55.900
Speaker 0: You need to understand what to ask AI for, potential pitfalls best practices and so on!

00:12:56.280 --> 00:13:05.720
Speaker 0: So that is certainly changing how YOU learn things but does not mean the innovation around frameworks or libraries wouldn't matter anymore….

00:13:06.200 --> 00:13:20.340
Speaker 0: I think it matters more than ever because there's a lot of empty space for innovation, for frameworks that give AI clearer rules and of course always four frameworks libraries tools.

00:13:20.580 --> 00:13:26.100
Speaker 0: That allow us to build faster more performant more error-free and so on applications.

00:13:26.160 --> 00:13:33.060
Speaker 0: because ultimately as I mentioned