*LIPSMACK*

33:32 😬

9:21 RIP @MikeRogers0 😢

Great presentation. Keep it up! 💪

Unity can easily render 20000 sprites at 60fps. Those blows on Unity were pure nonsense.

bashing truffle ruby 🤔

Uhh.. That's just lazy OOP, with unnecessary fluff when all the good terms are already the without creating classes like "SomethingCreator", "SomethingDoer", etc.. Presumably in this case User class "has_many :orders". Extend the relationship with a module: "has_many :orders, extend: UserOders". In that UserOrders create your variant of "create" method. Since given example does auth, charge and emails, let's call method "place". So "user places an order". In that method you can access the owning side of relationship (in our case instace of User) through "proxy_association.owner". That's it.. And then your controller code will looks something like: "order = user.orders.place(verified_params); if order.persisted? redirect_to(...) else render :new" (this is bit of a pseudocode since youtube comment section won't allow good code formatting). There's little bit of trickery in error handling, but everything is there. Note that relationship can have multiple extending modules. If one module starts becoming unwieldy - you can always split in multiple modules by some sort of "theme".

Amazing job Alan, thank you! ❤

Great conference we are lucky to have Amir and dragonruby toolkit. Im considering making a game in because it seems very pleasant to code in. Keep going dragonruby.

No idea why rails has to be so absurdly complicated. In react, you never once have to think about the details of what’s going on in the AJAX requests because all that detail is abstracted away from developers and it just.. works. Having to understand all the nuances of low level details just to write a front end in exchange for not having to write JavaScript is NOT a good trade off at ALL. That’s like saying we can write all our clientside code in assembly but at least there’s no JS!

20k sprites at 60 FPS???? How???... was it written in ASM????

I think it’s a mindset difference people who like monolith can only like this. React is micro service mindset people who like to breakdown mammoth into rats.

Please orginize rubyconf in India as well

Here's the "same" presentation from N. Means but with better video (no stupid rubycon burned in ad): kzbin.info/www/bejne/aZ7LfYdpl9SibKM

Such a great talk.

I think the author is doing a fabulous job taking the watcher along for the ride and letting them have the same epiphanies. But I also think there’s more places where mocking is necessary and beneficial and would encourage the reader of this comment to look up some of the talks by Sandi Metz about the magic rules for testing.

Woow!😂

I like such talks where the takeaways are simple and can be implemented in our day to day projects or job.

glimmer feels interesting

Good time, thanks

Just as my company is moving to trunk based development. I'm going to enjoy this.

This video definitely needs more likes. Thanks for sharing it.

👇 'Promosm'

Reminds me of when I started. Now it makes sense but then, omg, I did as you did. Copy and pasted.

This pattern shown at the beginning (pass config and collaborators to the initialiser, pass data to the call method) is exactly how I personally like to create service objects: it’s great and makes for straightforward testing and dependency injection. But it’s not the command pattern, as I understand it? My understanding of the command pattern is that it’s for a very specialised use case where you build an object with everything, including the data, and then execute it (with no arguments) later. The canonical example I’ve seen is of a text editor, where individual commands are created into an undo stack. But maybe there are competing definitions? Does anyone have a link describing the version of the command pattern described in this talk?

1:39 Cross-dependency hell 4:58 What is Big Rails 5:40 Ownership with code_ownership 8:13 Boundaries and dep management with packwerk 17:31 Modularizing techniques compared (Engine VS Pack)

This was quite useful. Thanks for sharing the previous experiences as well.

loved this talk!

I love simple things that are powerful as well. I felt that my life guided me to Ruby.

His pronouns are "They/Them" LMAO

wrongly think that the tattoo is part of the shirt

“I wish…” 🤣🤣🤣

best engine yet.

I'm here because I saw JRuby at the very bottom of an energy efficiency list and got curious as to why.

It's fun seeing you after hearing your voice for months on the bikeshed :D Loved the talk!

Thank you bro for the explanation. Can i see the git hub repo?

Neat!

Great speech and congratulations on shipping prism!

Wonderfully pragmatic. Elle offers strategies that are clear and firm, but never rude

Great talk! Very nuanced, clear, and relevant for programmers. Thanks!

Good video

Isn’t Ruby using semantic versioning? Does this mean Ruby won’t have any major releses until 2030?

nicely and accurately explained. well done

Thanks to Matz for Ruby 💎🎉

I find the approach taken in by Makandra in the Growing Rails book more preferable.They create use-case specific subclasses of the primary model like `User::AsSignup` and put this once-off logic within those classes. When used with `active_type` then view rendering and url helpers continue to work as normal with these subclasses and your validations still work fine with forms. Oh yeah and you can add single-purpose fields to these models too.

Good talk, I learned a lot, and also it makes me want to research more about time and dates.

Those implicit includes of deps looks strange. Also dependency injection containers making feeling that you’re not controlling object construction that declared as dependency. I understand that object in deps just created & included as a part of class but why not just simply pass needed objects & params using new(email_service: service, another_param: some_val). You will strictly control what passed into initializer. Also what if need to pass different params to component initializer defined as dep, how to do it?

So exciting and inspiring! Thank you, Kevin!

Conflating the name of a file with the file type was a tragic misstep.

Nicely done Murray. And I like the "why?" discussion most of all…