はてなブックマーク

As someone who, like many here, depends on Rails for my job, I’m worried about the long term effects of the last week on Rails. I’m not going to discuss those changes at Basecamp but I want to discuss my concerns about what this means for Rails itself. In the last week we’ve seen: One Rails core team member resign from the core team The creator and major contributor to important features in Rails,

This isn’t a vote for it necessarily but as far as I know it’s main selling point was having a substantially smaller learning curve. I have no idea if that’s true however. My personal experience with Rollup is that that is only true in very specific circumstances, mostly around node rather than web JS packaging, but I’m open to others’ mileages varying.

Hi, this is Matz. A few Rails core developers (including DHH himself) contacted me that the recent keyword argument changes are too painful. I admit we underestimate the pain of migration of the keyword arguments. After serious consideration, I decided to change/postpone the migration schedule. We are awfully sorry but Ruby3.0 will not have the real keyword arguments. But there are too many possib

We all lose time to “Rails WTFs.” Something goes weird in our Rails process, and we spend four hours frantically reading Stack Overflow before it finally occurs to us to restart Spring. Or we make one silly typo and it c…

About a year ago I noticed various benchmarks such as running specs were running abnormally slow on macOS. Noah Gibbs started some basic investigation but did not come up with anything definitive. Since then I crafted a version of Discourse Bench (used at: https://rubybench.org/) that is there to profile “performance” of local development machines. It is a simple benchmark that measures performanc

More Resources Keep up to date with Rails on Twitter and This Week in Rails Policies: Conduct, License, Maintenance, Security, Trademarks