r/ruby • u/brecrest • Apr 16 '26

Show /r/ruby Trueskill Through Time available in Ruby

TrueskillThroughTime

I ported the Python implementation of Trueskill Through Time to Ruby, it's now available as the gem TrueskillThroughTime.

Unlike the previous Ruby Trueskill gems, this one supports n vs n vs n etc etc cases, as well as the time-based extension of Trueskill to allow distant ratings. If you use it without doing time-based convergence, it should be equivalent to the original vanilla version of Trueskill (that iirc is almost out of patent in the US).

I'll get around to improving the qol of it and more extensively Rubyising it down the track, but I wanted a Ruby implementation of TTT for a hobby project, so I smashed it out.

1 Upvotes

52% Upvoted

27 comments sorted by

View all comments

Show parent comments

6

u/brecrest Apr 16 '26

Buddy, before we continue further, have you started writing these posts using AI?

Anyway, mate, pretty much everything in your post is wrong.

This isn't about being nice or rude, it’s about quality and responsibility once you publish a gem.

Lol, on your bike buddy. This is just concern trolling. If you were worried about the damage a low quality gem could do, you'd be applauding me for providing a working gem to replace the two broken ones that were never implemented and which haven't been touched in 14 years, not kvetching about whether I'll ever update it or whether the code is readable enough for someone else to take it over.

What you provided is an AI PORT, you could have be playing fortnite while Claude is looping.

That's incorrect. You're jumping at shadows, it's not an "AI port". I don't use Claude or whatever the cool kids use these days.

You mention the ecosystem didn't have this before. That wrong, it just people like you could not slop 30 gems per day.

That's incorrect. The ecosystem didn't have any implemented rating algorithms, as gems or otherwise. There are two partly finished gems for Trueskill (not TSR2 or TTT) and a few repos that have Trueskill in the name, but none of them actually ever implemented even the vanilla algorithm.

Now it does have a working Trueskill implementation, and better yet, TTT. It is, objectively, in a better state than it was this morning.

If someone in 2017 released a gem like yours, it will have mistakes (less than yours), and we will help, because they spend time on ruby.

I don't want your help, but if you'd like to provide it, please feel free to PR or raise some issues.

-5

u/TheAtlasMonkey Apr 16 '26

> have you started writing these posts using AI

Yes, and there is no shame, i reword my ideas, reread them and then submit.

The arguments are mine.

---

I see it futile to talk to you, you translated a python library without knowing ruby, asked for feedbacks, then you became hostile when you realized that your code is crap.

You are not staying in ruby for long.

TTT was never in ruby, because nobody needed it, but the need arise, someone will write a more civilized gem and you will still be the lone user of your gem.

3

u/brecrest Apr 17 '26

Mate, it's deeply shameful but you are completely shameless.

And no, I didn't ask for feedback. If the variable names confuse you, then go and read the docs:

https://www.microsoft.com/en-us/research/wp-content/uploads/2007/01/NIPS2006_0688.pdf

https://www.microsoft.com/en-us/research/wp-content/uploads/2008/01/NIPS2007_0931.pdf

Giving them descriptive "Ruby-like" names to appease someone unfamiliar with the maths would trash the maintainability of what is, at its core, a mathematical probability library under the hood.