วีดีโอ

"Shush please!"

"rust requires you to deal with the possibility of an error" .. i love this about rust, ngl

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

Wow I looked at this year's ago and was super impressed, at the time I was even think this would have been better in rust. Now I find you again just as I need an embedded dB in my rust app. Woohoo I'm excited

Leptospirosis? really?

@6:36 What is sense of this code anway ? Iterate over items and add copy of them to the same collection if predicate is true ? Also without a clone we may end in endless loop if we add items to collection we iterate ? (depends on iterator implementation). Anyway doing it in any other language without using index or some form of .clone/.copy is asking for trouble.

"Going to introduce Barbaras intern Alan".. well.. he's Captain Disillusions intern.. I'm now so confused

This guy has no clue about presentations and talk to public , horrible presentatation hearing this guy speak like running 😊

Very helpful talks 🎉

With tokio::join! you get structured cooperative concurrency, with tokio::spawn you get unstructured cooperative/parallel concurrency.

0:06 nice try chris, but there's no 'h' in ayup... great presentation, I'm learning a lot from your knowledge of rust.

Greate!

lol, in the case of the C++ code you're using a low-level API (poll() syscall directly) yet, in teh Rust you're using high-level APIs that wrap all that. Comparing these two is idiotic. That is NOT idiomatic C++ - that looks and smells like C code. Not C++. There's plenty of high-level wrappers for this in c++ yet you use low-level C-style code. Nice one.

Unwraps aren't bugs, they're unhandled errors. When you start writing Rust, you write programs for yourself and when invalid input is passed, you just use the panic report for info. You don't fix "the bug" for unwraps, you handle the error to remove them.

Люди, которым нравится писать ТАКОЕ на раст - не от мира сего. Им нравится натягивать сову на глобус при помощи микроскопа. Зачем?

Huawei sells minorities' info to the CCP to punish and track them.

Why the fuck are you sponsored by Huawei? Do you have any integrity?

great efforts

2:54 "after you children are dead!". Ugh, that escalated quickly.

Thanks for the talk, this is genious... code should be written to be as easy as possible to read ... in 99.9% of the cases, the easy mode rust will be already faster than all the other languages... so reducing the barries of entry should be the target... if the rust comminity understands that there will be no challenge to take over. I am a 20 years xp developer learning rust for the past weeks... I am in love but I recon that it might be hard for begginers. Cheers!

Can windowing be disabled so messages are sent immediately? Can messages be broadcast to all actors in a group?

How is a two-phase struct different from a type state?

This is looking awesome and should definitely help the rust web backend development experience. Excited to give this a go.

Interesting talk, never heard of rhai before 😎

Genocide enabler.

Nice talk :) Really good for new users or people that don't know how cargo work.

Great presentation Jon! Thank you

I've been surprised that functional solution is so easy to think, since people assumed that functional programming is hard.

I have implemented a lite version of this dependency injection myself now. It was... an experience. Basically I wanted callback functions, but one of the parameters could have an arbitrary type parameter, and the return type could also have an arbitrary type parameter. (Bounded by traits, actually, but arbitrary enough) I think it's based on three traits and a struct wrapper... Took me a long time to even understand some of the issues that cropped up. (The most important one being the ability for a type to have multiple Fn implementations. I just didn't consider that at all and was wondering why it kept claiming my blanket impls weren't bound properly... So if you want to do something like this, keep that in mind.)

Great talk! I don't agree though that platforms are best at UI - technically this may be true but it just doesn't scale. Needing two separate teams for basically the same application is just not a good enough solution in my opinion. Being idiomatic on a platform is hugely overrated - none of the "big" apps really are, they just follow their own UI/UX guidelines. It's only important to be consistent and provide a good user experience without conflicting with the underlying OS. Also the web is a mess anyway and people use it everyday. I worked previously on a pretty big cross-platform project and we resorted to Qt/Qml, which I really don't like, but it was okayish at least. UI/UX for sure wasn't the problem - no one ever complained, not a single user! The main issues were related to C++ and Qt bugs. We really need a solid platform-independent UI framework. Flutter could have become it if Google didn't make the really stupid decision to base it on Dart. Maybe Slint will fill this role in future? I don't know. Unfortunately they don't really support mobile very well as of today.

Great talk! Leptos is amazing, I hope it get's the attention it deserves. Together with Tauri it's the best thing since sliced bread for writing cross-platform apps.

i was excited to use it but after a speed comparison with postgres, postgres smoked surreal

Thanks! It was great to see these real-world examples.

Leptos helped me build a website and API for an event last year and it was delightfully easy and fast (after a little help from Greg). I updated that site and API a month ago with the latest Leptos version and was again delighted with how all the changes made things easier with less boilerplate. Leptos's rate of development is amazing 🚀

Frédéric could easily be the first ever person that doesn't grind my gears as a Frenchman, and yet he is. Great talk 👏🏻👏🏻👏🏻

Giving a talk is not easy, and the best delivery comes when you plan ahead and know exactly what you’re going to say and demonstrate. I think this one would have benefited from more prep, and less wandering around in the editor dealing with irrelevant compiler errors.

Is it Zellij running in Alacrity?

I am not sure about use case for Leptos. It looks like React in Rust.

i hate that amazon has infiltrated rust

Exactly what I was looking for. Thank you!

Yet another Jon awesome presentation 👏👏

The whole thing doesn't feel like an "easy" Rust. It feels more like a collection of weird, contrived dance moves that beginners need to learn in order to avoid those invisible, contrived barriers that the language put up for the name of safety. "If you wanna avoid using lifetimes, use Arc. What is Arc you might ask? Well, let me explain about Rc first before we go into Arc, so that you can "easily" avoid lifetime annotations." Only Rust people think this is ok. Don't get me wrong. I'm totally onboard with the capabilities the language brings. But if those capabilities come with a learning curve, then just let people climb that curve, properly, and maybe even painfully to an extend, in order to bring them the full benefits.

I do wonder... What is the most used package that includes an unsafe block? I mean, including transient uses. If one knows what that is, and re-implement the unsafe blocks in a safe way (or provide extra features in core to do it), the number of projects with unsafe would go way down.

wow, this was pretty cool talk. thank you.

Very hard to listen to due to his pronounciation.

I learned a lot, thanks Chris!

At 34:08 it should be // unlock the mutex

Title is inadvertently hilarious

i thought this was easy mode.

Wait, who's on first? Not a hit on the speaker, oc. It's just another part of rust that's a bit wonky atm.