วีดีโอ

Thank you for amazing video. Please tell use your opinion about SEO too :)I

Solidjs mentioned! lets go!

m.th-cam.com/video/e0xAmR_iIAs/w-d-xo.html

Just came back from a Frontend Sheffield Meetup and one of the speakers, an Amazon engineer Tom Johnson, said they were using Leptos in their Prime team for 3rd party devices.

Thanks for making the video.

All you need to do is get rid of the DOM. Then all other assertions hold true, WASM is fast, awesome, will take over the world. Honestly I haven't tried using rust wasm yet, being a javascript dev I'm making my own thing in javascript for now and then after a lot of time I may be able to port it to rust, which is a complete different language in many ways. But I'm just doing math so there's only nodejs and no DOM, I could probably gain some performance with rust wasm.

Man, seeing how easy you walk through it and how well you can explain that.. I feel intimidated :D

The thing that I wonder is this: If vanilla JS keeps winning all contests for UI rendering performance, memory usage and network bandwidth, why are we not generating vanilla JS instead of running frameworks in the browser? Solid JS is close to vanilla, so much so that I don't see a good reason not to use Solid in favor to vanilla. But if we would put the effort we are currently spending on trying to make the web better into making it easier to express what UI we want to get and render that to the web using the technologies we find, we would probably get better results in most if not all performance metrics and then may have additional benefits from using a good abstraction for UIs. And yes, I used the bad word. Not object oriented, but I said "abstraction". And I don't feel bad about it. The problem is not to use abstractions or to think upfront before you implement stuff. The problem is to use the wrong abstractions. One of the greatest challenges of web applications is state management. More precisely the problem how to manage several layers of remote state. It starts with the browser display that has to synchronize the DOM with the graphics display. Then comes the local model we keep in our web apps that needs to synchronize with the DOM. Then there are worker threads and web services that affect or query remote states and need to synchronized with our local app state. These services talk to other services or databases. Most applications grow using these layers with very minimal if any understanding of various dependencies and implications of this structure. I believe it would be much more beneficial to use an abstraction that models the data flow on a platform agnostic level with the option to optimize deployments and generate as much code as possible for specific deployment options. This would eliminate the need for most of our fancy frameworks, minimize the amount of unnecessary computations, data transport, data transformations and most of all headaches at the boundaries of any of these frameworks. I'm not even sure if such an approach would be much more work than to create a Rust/Wasm framework.

Do you have goals to make ur full stack framework compatible with multiple devices.

Is there a list where we can see the websites using these Rust UI frameworks?

Such an informative video man. I really enjoyed the behind the scenes explanations from an expert like yourself :)

Looks like I should refactor into leptos instead of yew

I'm allergic to js. js-free frontend wen?

I'm new to programming and I've been enjoying tutorial hell before I invest time into writing code. I was wondering if wasm can replace json?

Great vid! Thanks! Keep them coming ;)

I think that one problem with javascript is that it's a terrible language. Yes, it is true that millions of dollars were spent on improving javascript performance, but at the end of the day there's only so much you can do when the fundamentals are broken. For me WASM could have been a way to bypass javascript entirely. Unfortunately the big corpos decided that WASM can only be called with javascript. Is that a failure or some innate limitation of WASM, not really. Honestly if I could, I would go without javascript, html and css if given the option. Unfortunately this functionality is not exposed by the web-engines. Coming back to the real world, I agree with basically everything you said. On the other hand I also think a lot of the use cases currently of WASM and Rust on the frontend are very niche and limited. I don't think using leptos is worth it. For me, being able to develop for proton and run apps anywhere sounds great but the actual implementation never seems to work. Native is the way to go.

I am new to Rust, new to reactive systems and yet this video makes it so easy to understand the concepts and the inner workings. Thank you for the insightful video and clear explanation!

Ok, after days of searching and fiddling around, this video answered all of my questions. You sir, are a godsend. Was so confused with different frameworks and opinions. Thanks again!

I am here because I am the maintainer of a web-app that at some point has do display interactive charts and maps that handle larges amounts of data. The frontend post-processing and the many abstraction layers of Plotly (and mapboxgl) are causing a huge slowdown and everything gets laggy. I am searching for alternatives of how I could perform faster post-processing (I already did my best with JavaScript) and GIS/Plotting. Do you gentlemen and women and anything in between have any suggestions?

this framework is insanely powerful, almost a paradigm shift.

Really interesting comparison. Thanks!

How current is it in the context of Leptos versions, please? For example, the logic in this video would be mapped to which Leptos version?

I love these sort of deep dive philosophy topics

Just coming over from Svelte4 -> Svelte5 ; having to compare/contrast SolidJS style signals in both those frameworks, and seeing your talk just made EVERYTHING make so much more sense. Thank you.

Honestly canvas is a pain to use.

I wouldn't pick rust over javascript for effeciency. I don't think we need better performance on the web today, but more statical typing and robustness, while keeping the access to web development pretty easy. The goal to me is to find a way so that with very little knowledge we can't mess up code and create invisible bugs, incoherent dependencies, while at the same time it shouldn't be very hard to develop a good web application. Rust looks a like a very good language for that, thank you guys for the frameworks you're developping!

Thank you SO much man for how you've done the introduction! I wish more people did this "gist-of-the-video" type of intros, it saves so much time!

you are a great teacher man

31:29 This is exactly why Rust is so great. Even if it's a runtime borrow-check, it's still a borrow-check, and not a data race. ^^ Same thing in 33:56.

fantastic presentation, thank you so much! I'm evaluating leptos for multiple future projects, and it looks very promising to me.

Could you provide code you created throughout this tutorial? It'd be so helpful to study your code without scrolling youtube video back and forth :p Great work, BTW, many thanks!

So you are saying I should use React..... to keep my job...

😂 No effects is like saying no event handlers and no callbacks. Do people really not see the similarity?

you are the man! I started to love Rust a couple days ago and now I'm starting to love the community too!

Super cool. Needed to watch it a second time to code along. Thanks a ton !!!

if i write performance based code in c++ can i use wasm and see a significant performance improvement

In my opinion performance is not so important now. When a company choose a stack they look for support, libraries, popularity etc.

Using the link in the description I cannot see Sledghammer in the benchmarks. I also can't find it in the git repository. Is there a fork that includes the rust frameworks?

That was amazing. I didnt fully understand all the rust parts. But i feel like i finally get signals and effects. Phenomenal video. Thanks a lot

Thank i m new to rust and its so hard for me to tackle wasm closure, your framework are really great and this vidio are plus plus. Now i understand better into borrow checker with your explanation

Why not set the current running effect in the create effect method instead of run effect method. because you only need to figure out which effect depend on which signals only once and not every time the signal is run?

I may be wrong but isn’t this exactly how react hooks work? React maintains one giant array where all the state is maintained (don’t need to do <dyn Any> because js is dynamically typed) and it returns the reference to read the state and a function to update the state

"Do people read docs, idk" The Leptos book sent me here lol

As someone happily running a 2011 CPU with the RAM maxed out to 32GiB for everything except web apps (I have a separate gaming rig I'm quite happy with... it's a hand-me-down of similar age with 8GiB of RAM and a Radeon HD 5870 from 2009), I'd say that WEB APPS IN GENERAL aren't ready for prime time, regardless of what they're written in. When normal "a few open tabs and a TH-cam video at 480p" web browsing doesn't reliably maintain better P99 janklessness than games like Superliminal or A Hat In Time, something's wrong.