it’s in gemini, just create it in ai studio. oh, that’s for your personal google one account. for workspace you need gemini business. no, not gemini advanced, that’s ai pro now. unless you need ai ultra. oh agents? you do that in spark actually. no, not gemini api managed agents, that’s different. for coding use jules. unless you mean the agentic ide, that’s antigravity. no, that’s the old antigravity, download the new one. actually gemini cli is being deprecated, use antigravity cli. no the flash model is smarter than the pro model. unless you need pro. if it’s video, use flow. no, flow uses veo. no, nano banana is images. actually that’s in gemini now. unless you’re in search, then it’s ai mode. no, research is notebooklm. anyway it’s all very simple.

#rubyfriends #rubykaigi with @paracycle @spikeolaf

#rubyfriends #rubykaigi 仲良しの皆さんで！

Is this ad a test to see who will fall for it? 🤦‍♂️

I can't make sense of this: UK makes a statement at ~23:00 (Cyprus time) about UK joining the war effort in a defensive capacity & the drone hit in Akrotiri happens at 00:03. Lebanon is 250km away, and Shahed-136 top speed is 185km/h. Make the math work!

Rspec isn’t not only deprecated, it is forbidden. Projects using it in the past aren’t asked to rewrite the tests, but new projects can’t use. And with AI, there is a possibility we will rewrite

The confidence with which LLMs can explain a concept to you but be wrong needs its own concept. I propose "llmsplaining"

TruffleRuby kicks off the year with a new website, a new release, and a blog post to go with it! 🎉 truffleruby.dev/blog/truffle… Many changes: * New versioning * Thread-safe Hash * No system dependencies anymore * Installs in 2 seconds * Development is now fully in the open

I recently built psych-pure, a YAML 1.2 parser and emitter written in Ruby. At a high-level, I wanted: - a fully conforming parser, runnable on any Ruby - the ability to preserve comments through load/dump kddnewton.com/2025/12/25/psy…

Last call! Program Committee applications close on December 22. If you're passionate about shaping RubyConf’s content — from keynote visioning to speaker selection — this is your chance to have a meaningful impact. Apply here → buff.ly/UMvBVX4

I was recently reminded that not everyone fully understand what the frozen string literal magic comment is about. So I figured it was the occasion for another deep dive. byroot.github.io/ruby/perfor…

I wrote about some of my thoughts on the lessons we can learn from the RubyGems situation and how we can move forward. blog.peterzhu.ca/open-source…

I am happy to see that RubyGems and Bundler have moved to the Ruby Core team. Being one of the originating authors of RubyGems (and host of RubyGems for 4 years!) this was always about making Ruby easier to use and share code as a community. I still write Ruby almost every day and I want our community to thrive. Thank you @rubycentralorg and @yukihiro_matz!

We just publicly posted about the Rubygems.org AWS root-access security incident from September 2025, what occurred, what we verified, and the actions we’ve taken to strengthen our security processes. rubycentral.org/news/rubygem…

I tried to explain why I don't believe the recent accusations toward my former teammates, as well as how the Ruby and Rails Infra team at Shopify operates and why it can be trusted. byroot.github.io/opensource/…

Why I'm not rushing to take sides in the RubyGems fiasco justin.searls.co/posts/why-i…

Since we're all in fact-checking mode this week, here's something that caught my eye and why I don't think we'll ever have all the facts. A maintainer explicitly used the word "fired" in a social media post when referring to someone terminated from Ruby Central last year... the same person allegedly singled out by Shopify. Yet that person's own detailed history of Bundler skips right over their employment ending, jumping from 2021 to now. Plot twist: they also launched a competing service before this drama started. Having run a company and served on a nonprofit board, I know employment details can't be discussed publicly. Some of the current board and current ED probably weren't even involved in whatever happened last year. So we have: potential employment disputes competitive business interests governance fights funding pressure, all tangled together. I don't believe Ruby Central can be quite as transparent as we'd all like them to be. Complicated things are complicated. It's messier than 'corporate takeover' or 'community defense' narratives suggest. Sometimes there just isn't a clean villain or hero. I'm going to remain optimistic that this will all get resolved amicably.

I took some time to delve into my latest work on reducing Ractor contention. This time: Generic Instance Variables byroot.github.io/ruby/perfor…

Beyond performance work, I deprecated a bunch of APIs in the JSON gem, and added others, so I figured it would be a good occasion to talk about API design: byroot.github.io/ruby/json/2…

The final #RailsConf was an amazing end of an era. Thank you to the entire team that made it happen!