I am pretty happy to see my patch for RubyGems (edited: Actually, it's Bundler!) from 4.5 years ago got merged: https://github.com/ruby/rubygems/pull/4892
Thanks @hsbt for taking care of that.
| Profile | https://www.godfat.org |
| Taiwanese | |
| GitLab | https://gitlab.com/godfat |
| GitHub | https://github.com/godfat |
I am pretty happy to see my patch for RubyGems (edited: Actually, it's Bundler!) from 4.5 years ago got merged: https://github.com/ruby/rubygems/pull/4892
Thanks @hsbt for taking care of that.
Oh! I only realized now that my patch for rspec-mocks was merged 5 years ago: https://github.com/rspec/rspec-mocks/pull/1218
It's still in 4.0 beta though, no stable release yet 😬 https://github.com/rspec/rspec/blob/v4.0.0.beta1/rspec-mocks/Changelog.md#400beta1--2026-02-18
I understand it's considered a breaking change because it's fixing a "bug" that does change the behavior.
I am still pretty proud that most of the bugs I found in rspec mocks could not be reproduced in muack: https://github.com/godfat/muack
It's also pretty small, too! However it's fully feature complete.
Maybe I should move to a Mastodon instance where I can post more than 500 characters. This limit annoys me to no end for English.
Chinese on the other hand, 500 characters can possibly contain 10x more information within the same limit... much less of an issue to be honest. This speaks that "characters" limit is quite arbitrary 🤷 Systems like this usually use "bytes" limit which in some way makes better sense after all. A Han character is 3 bytes in UTF-8, which is more "balanced".
RE: https://hachyderm.io/@rradczewski/116212327811508257
I didn't read through everything because it's quite long, and this is certainly quite mind blowing, yet it reads to me more like a human problem than software problem to be honest.
Reports were ignored, and people who actually used the software weren't trusted.
> Subpostmasters began reporting balancing errors within weeks of the Horizon system being installed, via the helpline they were instructed to use.
> ...
I suspect most people outside of the UK won't have heard about the post office scandal, but it seems highly relevant to learn about now (given *waves* this):
For over 15 years, the software post offices in the UK had to use contained severe bugs, particular in accounting, that everyone at Fujitsu/horizon and the post blissfully ignored. Over 900 (!!!) postmasters were sentenced for alleged theft and fraud, some went to jail, some committed suicide. All because the software was shit and everyone who could do something about it didn't care and swept it under the rug.
Everything, including how it was uncovered, about this seems bizarre and Kafkaesque, but we better prepare for it to happen more often.
Look at this disclaimer:
> MalusCorp International Holdings Ltd. is not responsible for any moral implications, existential crises, or late-night guilt spirals resulting from the use of our services. The MalusCorp-0 License is provided "as is," much like the open source software it replaces, except that we charge for it.
In the end, I think if this is killing open source (not from this service, but the overall idea in the era of AI), copyright should be updated to somehow protect open source.
Quoting the closing clause:
> [...] maintained by a generation of developers who believed that sharing code was its own reward and have been comprehensively proven right about the sharing and wrong about the reward.
>
> We owe them a debt we have no intention of repaying. But we do, at least, have the decency to say thank you.
>
> So: thank you. Truly. We'll take it from here.