Stan Lo
@st0012.dev
Ruby committer working on various projects to improve Ruby’s developer experience: rdoc, irb, ruby-lsp, ruby-lsp-rspec
@Shopify Ruby DX
@Shopify Ruby DX
I doubt we’ll get observably better signal from the community simply by reducing this barrier of entry. Even in an issue with 30 comments it’s still hard to argue it’s representative.
I feel pollings on social media is probably the best we can do. Ofc designing good polls is another challenge
I feel pollings on social media is probably the best we can do. Ofc designing good polls is another challenge
October 28, 2025 at 8:41 PM
I doubt we’ll get observably better signal from the community simply by reducing this barrier of entry. Even in an issue with 30 comments it’s still hard to argue it’s representative.
I feel pollings on social media is probably the best we can do. Ofc designing good polls is another challenge
I feel pollings on social media is probably the best we can do. Ofc designing good polls is another challenge
Not defending the status quo, but I think we need to be more specific about this:
- What counts as engagement? Blog? Conf talks? In any languages or just English?
- Everyone can already participate on bugs.r-l.org and the discussions there are high quality. So what do we need other fields for?
- What counts as engagement? Blog? Conf talks? In any languages or just English?
- Everyone can already participate on bugs.r-l.org and the discussions there are high quality. So what do we need other fields for?
October 23, 2025 at 1:53 PM
Not defending the status quo, but I think we need to be more specific about this:
- What counts as engagement? Blog? Conf talks? In any languages or just English?
- Everyone can already participate on bugs.r-l.org and the discussions there are high quality. So what do we need other fields for?
- What counts as engagement? Blog? Conf talks? In any languages or just English?
- Everyone can already participate on bugs.r-l.org and the discussions there are high quality. So what do we need other fields for?
Even ZJIT’s development is very open. Most of todos have open issues in github.com/Shopify/ruby...
We also have had contributions from GH employees, Python committers, and a few community members.
We also have had contributions from GH employees, Python committers, and a few community members.
Shopify/ruby
The Ruby Programming Language [mirror]. Contribute to Shopify/ruby development by creating an account on GitHub.
github.com
October 19, 2025 at 3:14 PM
Even ZJIT’s development is very open. Most of todos have open issues in github.com/Shopify/ruby...
We also have had contributions from GH employees, Python committers, and a few community members.
We also have had contributions from GH employees, Python committers, and a few community members.
I’m only starting to explore 石狩 now
October 19, 2025 at 2:03 PM
I’m only starting to explore 石狩 now
FWIW, I renamed those files in RDoc just to try HERB, and it caught tons of issue!
So I'd really love to make HERB and associated tools part of RDoc's dev dependencies :-)
So I'd really love to make HERB and associated tools part of RDoc's dev dependencies :-)
October 16, 2025 at 12:20 PM
FWIW, I renamed those files in RDoc just to try HERB, and it caught tons of issue!
So I'd really love to make HERB and associated tools part of RDoc's dev dependencies :-)
So I'd really love to make HERB and associated tools part of RDoc's dev dependencies :-)