Earlier quoted context omitted.
[flagged]
[flagged]
Ruby Central's Attack on RubyGems [pdf]
111–120 of 286 posts
Re: Ruby Central's Attack on RubyGems [pdf]
#112Earlier quoted context omitted.
[flagged]
In the linked article, DHH links out to a wikipedia article titled "Ethnic groups in London"[0]. He then uses a statistic that "only a third" are native brits in 2021, which roughly lines up with the "White British" line in the chart. You can argue that "white supremecist" is a charged and problematic term, but I'd say that "Here he complains about too many brown people in London." is a fairly accurate representation…
Re: Ruby Central's Attack on RubyGems [pdf]
#113Earlier quoted context omitted.
I clarified the toot.
Thanks Mike, I editted, and asked this: > Why do the maintainers have a problem with this? I thought the stated reason was about RC removing everyone's access with no warning. I seem to remember some of DHH's controversy due to banning politics at basecamp or something. Is it related to that?
I wouldn't be surprised. The presence of this quote in the linked document:
> A person’s character is determined not only by their actions, but also the actions they stay silent while witnessing.
Suggests that the person who wrote it is deeply obsessed with political activism.
Re: Ruby Central's Attack on RubyGems [pdf]
#114Sorry for all the maintainers, that must suck.
Re: Ruby Central's Attack on RubyGems [pdf]
#115Earlier quoted context omitted.
Someone with absolutely no technical background, a recipe for disaster.
Rhiannon worked with Ruby Central for a bit, left a few weeks ago, and just shared this: https://bsky.app/profile/rhiannon.io/post/3lz6zcflg2s26
Re: Ruby Central's Attack on RubyGems [pdf]
#116What almost surprises me the most, is that such a mature ecosystem still doesn't have a formalized governance structure after all this time. How common is this among large and widely-used open source projects?
Re: Ruby Central's Attack on RubyGems [pdf]
#117[flagged]
Re: Ruby Central's Attack on RubyGems [pdf]
#118Earlier quoted context omitted.
what are these hallmarks? is this becoming the latest way to attack an idea? instead of engaging with the actual content you just claim it is AI and therefore it can be ignored? seems disingenuous to say the least.
Overuse of rule of three, cliches like "This was not X. It was Y." and similar, obligatory bulleted list, overall overly grandiose. None of these are a smoking gun, but the smell is definitely here. AI detection tools also confirm my suspicions. I don't have a horse in the race in regards to the content, since I'm not a Ruby developer, I would just prefer to not see AI-written comments on HN. If this is so important,…
Re: Ruby Central's Attack on RubyGems [pdf]
#119[flagged]
They tried to cancel Matz for not supporting weird DEI corporate speak in the TOS, they've been trying to cancel DHH for years for his mild conservative lean.
There's also a weird contingent who keep trying to push stuff like TypeScript for Rails and typing for Ruby, at one point they wanted to fork Rails when DHH made Hotwire default (they wanted React), etc..
Outside the weird US corporate bubble, Ruby is doing just fine. Japan, Europe, Canada, etc... Rails World gets bigger and bigger, Ruby Kaigi is growing, etc...
Re: Ruby Central's Attack on RubyGems [pdf]
#120An update from Ruby Central: Strengthening the Stewardship of RubyGems and Bundler https://rubycentral.org/news/strengthening-the-stewardship-o...
Totally reads like post-facto CYA. they could have communicated this to the maintainers internally beforehand instead of blindsiding them.
If you're arguing that is what ruby central should have done, that's a social engineering attack.