Rubyist. Leading Hanami, Dry, Rom.
Canberra, Australia. he/him.
@timriley.infoReally sorry this happened, Drew :(
Tim Riley
@timriley.info
@timriley.info
@konnorrogers.comReposted by @timriley.infoWhen you start writing your own framework, you start to understand the decisions the Hanami team made 😅
@afomera.devReposted by @timriley.infoI just pushed a first-version of hanami-turbo a RubyGem for using Turbo with Hanami
https://github.com/afomera/hanami-turbo
The readme links an example app showing #hanami #ruby app with a few patched gems.
Give it a try and let me know how you get on!
@aaronmallen.devReposted by @timriley.infoToday I have published part three of my Hanami, Why? series Hanami, Why?: Class Action, where we will dive into what makes Hanami actions awesome.
https://aaronmallen.me/writing/hanami-why-class-action?ref=bluesky
#ruby #hanami #hanakai
@timriley.infoWeeknotes! All of the CLIs are getting into shape, lazy exposures lazed their way into Hanami View, and a bunch of resource routing bugs got fixed.
Hanami 3.1 is just around the corner! We’re aiming to get all code changes made by the end of October.
@jardo.devReposted by @timriley.infothis week in Solidus:
Solidus v4.8 is out!!!
https://solidus.io/blog/solidus-v4-8
@timriley.infoWeeknotes! thoughbot sponsors Hanakai, Hanami goes green on JRuby, Dry CLI gets required options and a built-in spinner, Hanami View gets lazy exposures, Rom factory gets transient attributes, and much more! Heckuva week.
@amyhoy.bsky.socialReposted by @timriley.infothis is just so wholesome. tonic masculinity. mamdani really is our new mr rogere
@aaronmallen.devReposted by @timriley.infoToday I have published part two of my Hanami, Why? series Hanami, Why?: Bits & Bobs
https://aaronmallen.me/writing/hanami-why-bits-bobs?ref=bluesky
#hanami #hanakai #ruby
@aaronmallen.devReposted by @timriley.infoToday I have published the first issue of "Hanami, why?". This is a new series I'm starting where we will dive in together to learn about #hanami.
https://aaronmallen.me/writing/hanami-why-introductions
#ruby #hanakai
@timriley.infoGIANT SPONSORS SMASHING INTO OTHER GIANT SPONSORS
@hanakai.orgReposted by @timriley.infoWe’re so happy to share that @thoughtbot.com is our newest silver sponsor!
@timriley.infoWeeknotes: timriley.info/posts/contin...
Single-file Hanami apps are back, next-gen code reloading is ready to land, Dry CLI gets styled text formatting and a spinner, settings loading gets some YAML, and views might just get some streaming.
Lots of progress this week!
@aaronmallen.devReposted by @timriley.infoHello, world!
@timriley.infoThis is very cool!!
@timriley.infocheckin’ these out, ‘cos charts rule
@baweaver.bsky.socialReposted by @timriley.infoIt is not responsible stewardship of a language or framework community to collectively invalidate the hard work of that same community and abdicate responsibility rather than providing a clear vision for the future.
@jardo.devReposted by @timriley.infobesides being full of holes, DHH's latest keynote also had near nothing to say to Rails users. cool cool cool. https://jardo.dev/what-about-rails
@timriley.infoYou can even help out—Andrea’s been with us exactly one year and made a huge impact! I love helping people come on board as contributors. Come and build something we can all feel proud of long into the future.
@afomera.devReposted by @timriley.infothis. come tell the Hanakai team your papercuts and let’s make Hanami and co really really great.