Thanks for the analysis! A bit off-topic, but I wanted to ask: My OKX wallet holds some USDT, and I have the seed phrase. (alarm fetch churn bridge exercise tape speak race clerk couch crater letter). What's the best way to send them to Binance?

Interesting approach...

Interesting

Go Tash 👍

you know it's gonna be an interesting talk when you see Chris Oliver

Cheateeeer!!! xDDD

MAJOR MOMENTS IN THE HISTORY OF WRITING

Nice talk :) Regarding fibers going across threads, I think it's a reasonable idea for implementing work stealing, however the problem right now is threads also limited by the GVL, so in terms of parallelism, there is little to gain. We'd have to make threads work without the GVL for it to have real benefit. As it stands, it's probably not worth the effort without "free threading". Regarding actual Fiber going across threads, it was impossible before due to the default copy coroutine implementation, but I removed that and replaced it with a pthread implementation (fibers emulated on threads). Because of this, there is no longer any reason why fibers can't go between threads.

I feel that this code introduces a meta programming unnecessarily. I know it is a cultural thing in Ruby and Rails to look for elegance (or perceived elegance) than simplicity, but it comes at a cost. For example, * Why use symbols and then constantize it? Just specify the class name. * Why use meta programming to call the `inherited` hook and create classes dynamically. Just create the classes manually. In my experience, simplicity beats elegance.

Mu Fan congrats on sharing this comprehensive talk about the reinvention of the app. I find it interesting that ruby code tend to be structured in a slightly different way depending on the country or past experiences of a developer. Keep up the good talks!

This was so helpful. Thank you

really nice talk

我很喜欢这位大师的发型👍

I don't get it. You say that GIL prevents threads from executing in parallel, then in the last slide you suggest to use Threads for CPU intensive tasks. Did we suddenly start using JRuby or something? And example of Fibers in action would have been nice.

Great talk <3

Very nice

Seeing CRuby + jit being so close to JRuby is quite impressive

I enjoyed speaker vibe and speachfullness, thanks!

Anyone knows if those files are in a public repository?

Rails code is heavily written ith thread in mind, it will need a lot of rewriting. If you can contribute please do so.

Awesome!

Thank you!

One question: What would be the difference between "Fiber" and "Ractor"? Which one would you recommend for the production environment?

I liked your presentation.

How come Ruby expects the user to implement the Fiber scheduler?

Happy to have found this gem (<- see what I did here?) and sharing it w/ my coworker 😅

Isn't this whole presentation, in a nutshell, the same reasoning behind Ryan Dahl introducing NodeJS in 2010? 😊

Don't know what to think of it. You seem to be struggling even after investing so much time in it.

This is probably the most underwatched source control video listed on YT

proc > rape > girl for < sex 0:38

Good presentation, the sound need some improvement though

Great talk!!! These are essential skills for great software teams IMO. A great tip I received once while working on a PR to an opensource project was that if you feel the need to leave comments on your PR explaining parts of the code, maybe consider instead breaking those changes out into their own commits with commit messages explaining the change instead.

It seems like isolating gems installed to those required for the current test set + prod gems would have caught this. Rubocop is needed during the CI lint step, but probably not during the testing stage. This still leaves you vulnerable to accidental dependencies on dependencies of your testing framework (which if minitest is only anything defined within minitest itself), but the risk is much smaller. Also perhaps running independent end to end UI tests in staging (or better yet, prod behind a feature flag). I may be missing something though. Either way, I loved the talk

18:11 Deps module will overwrite the initialize method, setting defined deps as arguments.

Absolutely brilliant, love it!!!

Fantastic presentation! I wish I discovered the trick with multiple id's on Brave to settle down that nonsense poll with 'tabs' vs 'spaces'. Everybody knows we need to embrace more 'green' practices, stop wasting resources and littering 2, 4 and sometimes 6 'spaces' everywhere, when we can easily get away with only 1-tab. Just imagine how many wasteful 'space' characters are out there, wasting precious storage... OUTRAGEOUS

Thanks all for attending. I hope it was insightful and not too boring, I forgot half of my dad jokes though - It was a bit intense to present in front of such an Elite crowd, haha. Ping me if you need any clarifications / want to pair up. Also, UPD Re Sidekiq question at 37:00 on how to include a separate Sidekiq span into a calling span - there is a way to do it by updating your OT Sidekiq instrumentation config "c.use 'OpenTelemetry::Instrumentation::Sidekiq', { with 'propagation_style: :child }" Cheers and stay happy! The name... is TheFriendlyTelemetrAntz

Thanks all for attending. I hope it was helpful! Be happy, cheers

Thanks for pushing the ruby community to the future Sam!

This is brilliant!

Mind has been blowned

Truly an impressive effort! Thank you for all your hard work :)

Thanks Adam, just hauled some old codebases up to ruby 3.2 so was starting to look around at what "new toys" this has unlocked for us and was eyeballing YJIT with great "how much of a rabbit hole is this going to be?!" trepidation! Will give it a crack next hack day and see if I can get a similar shift on our APM graphs :)

Great talk, not great "question" from the audience at the end 😒

This is both great work and a great presentation! Thanks Sam.

😭 Promo_SM

Such a valuable talk!

Great presentation, thanks! Looking forward to fiber based concurrency in Rails 7.1 🤞

This is magnificent!!

is this project on github?