Ooooh really nice, I need to load multiple audio files and I was wondering how to do that properly. Thanks for the awesome tutorial!
@yt-sh
2 ай бұрын
thank you for the video and for svelte as well
@ozgurNY
2 ай бұрын
After React, learning Svelte 4 was fun. After seeing Svelte 5 runes, Lavaral looks joyful to learn. Svelte 5 runed Svelte experience.
@spellsaif
3 ай бұрын
Thanks for this, really cleared most of confusion
@mijmijrm
3 ай бұрын
Catweasel!
@IFIListen
3 ай бұрын
Also, what’s wrong with on:click? It’s indeed better than onClick visually. Why do you feel like you have to follow the norms? You’ve come up with something better than the standard way, and now you’re getting rid of it? Why? on:click is indeed more eye-catching in my code; it helps me quickly identify event handlers on elements. 🤦♂
@IFIListen
3 ай бұрын
This is not an update; this is a downgrade. As someone who picked Svelte for its simplicity, I’ve been developing really good websites without even considering these issues. The simplicity of Svelte always allowed me to find a way to achieve my goals. With this update, it feels like I have to change my mental model of thinking, and aesthetically, it’s not like Svelte. It’s sad to see they decided to take this path. I wonder who got into Rick’s mind. They forgot why we chose Svelte in the first place: because we hate coding, but we want to build stuff.
@zap813
3 ай бұрын
Just FYI getters/setters are NOT necessarily idempotent, since they are just functions like any other. Take this for example: const obj = { get prop() { const rand = Math.random(); if (rand < 0.5) return null; return { str: 'blah' }; } }; Accessing prop on obj could get you two different data types if called twice, but TS doesn't know that, so it incorrectly thinks you are good. Even though this is a contrived example the fact that it's possible means that it's not real type safety since you are just fooling the TS compiler in the same way you would with a non-null assertion, although in this case it's not explicit.
@cherubin7th
3 ай бұрын
So basically the mission didn't work out. Very sad. I guess we just cannot have nice things in the JS hell.
@memestagestartup
3 ай бұрын
Ain't nobody got time for that...!
@D_bugit
4 ай бұрын
I like the he's re schooling us in JavaScript 😅😅😅... Please you should make a new framework that teaches how to code in JavaScript 😅😅😅😅😅😅😅😅😅... I like the content though
@mylastore
4 ай бұрын
The `$state` rune is only available inside `.svelte` and `.svelte.js/ts` files I get the above error when I follow your example above
@appurist
4 ай бұрын
In my fantasy dreams (hey, I'm a geek), I dream of a world where Rich and Ryan get together and create a "greatest hits" framework that isn't necessarily backwards-compatible (but could have a migration layer) like SolidSvelte 6 or something like that. (I know, supporters of both frameworks would probably revolt, I'm looking at the future only. And I've already ported things from Svelte to Solid and Solid to Svelte so I'd do it one more time for SolidSvelte (stupid name but you get the idea).
@todormarkov2860
4 ай бұрын
Even before the first release I have been following the progress, I can't wait for Svelte 5 to come out.Congratulations Rich for the brilliant design, simplicity and intuitiveness behind Svelte
@fcnealvillangca7943
6 ай бұрын
Svelte native when
@mavdotj
6 ай бұрын
Although I really love svelte stores and I have formed a relationship with them, but being able to do reactive values like this is just *shefs kiss*
@hellodefhellow
6 ай бұрын
Bruh rich is cool ashit, i like how he tryna make sveltekit the modern ruby on rails,long story short im starting a new business, choosing the right stack was difficult for me as i have only 1 year of web dev knowledge, i was confused between laravel and sveltekit, but i choose sveltekit.
@junaga2
7 ай бұрын
jo jo gang
@gersom3318
7 ай бұрын
I actually ran into this issue earlier but with a PDF that I generate and save on the server dynamically, so importing it build-time with Vite wouldn't work as the PDF will be regularly updated on-server. I solved it by saving and reading it from an absolute path on server. The issue with the Stream that you mentioned I solved by using the createReadableStreamFromReadable from @remix-run/node
@DanteMishima
7 ай бұрын
Zoom your code Rich, I implore you
@aurorapaisley7453
7 ай бұрын
Why is your video quality in 720p
@bergerblancsuisse.
7 ай бұрын
Svelte had the best stores of them all as shown by Fireship. In my opinion, enforcing writable() and removing reactivity from .svelte files unless it was declared with writable() would have been the best option because the interoperability issue around .ts/.js files and .svelte files would be solved with a pattern that is already superior to ref/signals. Open to seeing how this develops either way, but what I most enjoyed about svelte was not having to .value or getCount anymore and knowing that $count meant it was a store.
@Programming-Fun-With-Hima
7 ай бұрын
💗💙💜💛❤🧡
@fredguth1315
7 ай бұрын
I can't see the code very well. Is there a higher res version?
@afrowave
7 ай бұрын
This is excellent. It will work really well for static sites that are Markdown driven.
@jenslindo
7 ай бұрын
cool! is there already a solution for responsive images in sveltekit that adapts the image on the width needed for the current screen size - that would be more of a real world image problem (maybe)
@sandrosxila
7 ай бұрын
what if counter returned () => { count, increment } at 3:02 and have const {count, increment} = counter() at 4:41 or we can do something like currying const {count, increment} = createCounter()() ?
@PaulSebastianM
8 ай бұрын
I don't want to be rude, but I understand everything you're saying here, because that is indeed how the language works and there's no way getting around the language, you just have to use the language as the tool that's meant to be used in a certain way. So it seems to me... it just seems to me, that all the naysayers perhaps don't really understand the language they've been working with for years, instead they are used to the libraries they've been working with, and the abstractions those have, thinking with time, that that is how the language works. React is just JavaScript in the end, no? It's ironic how true that is, yet how misconstrued that statement can become. 🤷🤷
@Ryguy12543
8 ай бұрын
Love all the KZitem content you’ve been featured in lately. About time I found your channel. Thanks for the content big man very helpful as always🔥
@RasmusSchultz
8 ай бұрын
can't hear you. normalize your audio, please.
@c3cris2
8 ай бұрын
Upload with at least 1080p so the code isn’t a blurry mess. Thank you.
@MaxHDeveloping
8 ай бұрын
Please upload your Videos in a higher quality or increase your text size. It is very hard to read the code
@peppi69
8 ай бұрын
Very nice that is exactly what i need for my current projects. Instead of writing some very sketchy code or having to store base64 in a database I'd rather do this.
@-ion
8 ай бұрын
This sounds very useful for me. I import certain images on pages to get an immutable file that can be cached for a long time with a hash in the URL. However, I would also like the pages to have og:image:url metadata which needs a permanent URL for the image which should mutate when updated. Once read works with other adapters, it sounds like I will be able to use it to solve this nicely.
@aralroca
8 ай бұрын
In the framework I'm doing I preferred to create a prebuild folder where the server assets are placed and then an environment variable to access it but with more flexibility for developers. For example when loading compiled files to use FFI you have to specify the path, read is not useful here. I think it is better to give flexibility to use the own api of the runtime platform.
@maxburkhardt1
8 ай бұрын
Why can I not use $lib or get it from static?
@sahar23391
8 ай бұрын
rich the content creator > rich the developer
@pietraderdetective8953
8 ай бұрын
Cool feature! Can you please increase your font size? It's too small for mobile phone users. Please make it larger, thanks!
@mustofa_id
8 ай бұрын
I can't believe Rich uses dark theme
@Kevin192291
8 ай бұрын
Svelte becomes better and better :)
@mazedeux
8 ай бұрын
Thank you for the tutorial on duck typing sir
@scaffus
8 ай бұрын
So that's what sveltekit-pdf-demo was, very cool!
@whatplan4335
8 ай бұрын
Larger font size please Unwatchable on mobile
@alwayzsmarter
8 ай бұрын
My usual comment of I don't fully get it but when I watch it 5 more times over the next week I'll be wowed. I already think I'll use it in a case where I have an endpoint to get permissioned files and I get my dirty signed supabase url and want to pass that to the user through my pretty endpoint like /storage/[some_id] or something. I'm guessing this will improve my current implementation once I understand it more
@asimshamim113
8 ай бұрын
"fowl play" lmaoooo
@ScriptRaccoon
8 ай бұрын
It's very cool to get these updates directly from you, Rich :). Just a small suggestion for improvement: can you please increase the font size in your editor? Currently you show about 50 lines, for KZitem (which is also consumed on mobile devices) it would better to have around 25 lines. Then it is easier to follow what is happening in the code.
@rich_harris
8 ай бұрын
i know, sorry - still new at this 😅 i thought it was recording at a higher res
@Joseph-zd8jw
8 ай бұрын
@@rich_harris The audio was also a little low
@kirso
8 ай бұрын
@@rich_harris will be a proper KZitem Tech influencer in no time!
@lian1238
8 ай бұрын
KZitem has pinch to zoom.
@lolotronop
8 ай бұрын
@@rich_harris It's not about res, it's about size on screen. Even at 4k code that small would be really hard to read on a phone. Sorry if I'm overexplaining a bit, just to be 100% clear
@samuswarner
8 ай бұрын
Awesome - I had exactly the same 'your file read doesn't work in prod because the build doesn't know to include them' issue and had to build a brittle fix for it. Now I can remove all of that code. @richharris, since you asked, my specific use-case for this is serving js scripts (as text with permissive CORS headers) from my sveltekit application, for consumption by other frontend apps.
@coolemur976
8 ай бұрын
Dude needs a glass of water
@jonathangamble
8 ай бұрын
Hey Rich, this would go well with vercel/og image if you could speak to Vercel to make it compatible with SvelteKit.
@rich_harris
8 ай бұрын
yep, perfect use case! you _can_ use satori (the thing that powers vercel/og) with SvelteKit - Geoff did a great write-up [here](geoffrich.net/posts/svelte-social-image/). We use this technique to render the OG cards on svelte.dev (e.g. svelte.dev/blog/runes/card.png), and [here's a PR](github.com/sveltejs/svelte/pull/10246/files) to remove all the hackery that's no longer required thanks to this new feature
@jonathangamble
8 ай бұрын
Problem is it won't work on the edge until Vercel fixes a font error. Maybe you could push it up the chain 😊
@rich_harris
8 ай бұрын
ah, well `read` doesn't work on the edge either at present - there's no filesystem. experimenting with using `fetch` to just grab the asset from the CDN (which is obviously less good than reading from the same machine but probably still perfectly usable). will see which buttons i can push
@BaptistPiano
8 ай бұрын
@@rich_harris **love** the shameless use of markdown where it’s not supported! I do the same thing
Пікірлер