Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Plenty of discussions about this:

Shopify, pulling strings at Ruby Central, forces Bundler and RubyGems takeover

https://news.ycombinator.com/item?id=45348390

Ruby Central's Attack on RubyGems

https://news.ycombinator.com/item?id=45299170

A board member's perspective of the RubyGems controversy

https://news.ycombinator.com/item?id=45325792

I'm leaving Ruby Central

https://news.ycombinator.com/item?id=45352432

Bundler Belongs to the Ruby Community

https://news.ycombinator.com/item?id=45371061

Why I'm not rushing to take sides in the RubyGems fiasco

https://news.ycombinator.com/item?id=45405221



I believe this is the first version that's long-form journalism.

(I'm not a fan of the HN submissions which are short, anecdotal blogposts, that leave you questing for the rest of the story across the internet. I think all those previous ones were of that format. Discussions that start in medias res and assume you've been following every new development daily from the beginning).


Understood. This is collecting the various developments.

However, this isn't some isolated story that happened a week ago and nobody knows what's happened in the days since. As evidenced by the many discussion comments many have been following the developments/commentaries. Each of those posts were appearing as the story developed and/or referred to the initial overarching incident. Some even reference the other posts as part of the development. My thing of course when we get to this 'long-form' coverage is must we then repeat all of the prior discussions? Perhaps, but there's the prior discussion links anyways.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: