Xavier Noria
@fxn.bsky.social
2K followers 140 following 860 posts
Everlasting student · Rails Core · Zeitwerk · Freelance · Life lover
Posts Media Videos Starter Packs
fxn.bsky.social
In my signatures, the return type for predicates was Object!
fxn.bsky.social
My point is that, idiomatically, that would be `bool`.

The name does not formally restrict the interface, it is what it means, right?
fxn.bsky.social
So if you are told `bool` and that means `top` you know you cannot assume much and the object is mean to be used in boolean contexts.
fxn.bsky.social
you can discuss that with Matz :)

While Ruby is the way it is, all objects are booleans and official stuff should match Ruby senantics
fxn.bsky.social
Not really, in Ruby `nil` and `false` are both as false.

We could also have 0, empty strings, etc. only we don't.
fxn.bsky.social
I dislike the -ishms because they diminish Ruby semantics.

The symbol `:foo` is not kind-of-true or truish, it *is* true. It is as true as `true`.

And I am not into bending POLS to mean "least surprising to people coming from Java". You do not design a language to accommodate foreign expectations.
fxn.bsky.social
RBS has changed its mind wrt booleans.

The wiki says `bool` is like `top`, since all objects are booleans. Use the union type `true | false` otherwise. And recommends the former as preferable choice. This is the Ruby way.

But the spec defines `bool` and `boolish`. Man, I dislike the -ishms.
Object.new
fxn.bsky.social
According to the newly shared email, on Sept 18 he was clearly not working for RC anymore.

We have to conclude the password change, okus lack of communication, and all days that lasted are just unnacceptable.
fxn.bsky.social
Media Quality settings!
fxn.bsky.social
"The team of former RubyGems maintainers"

I am seeing this universal quantifier repeated or implied in all this conversation, but I don't think that is correct. Isn't it a subset of them?
Reposted by Xavier Noria
chaelcodes.bsky.social
Arko told Socket, “I have requested Ruby Central stop claiming to own or create ‘bundler’, although they are welcome to modify the source code and share it under some other name. Ruby Central has replied only to ask for time to review my request with their legal counsel.”

socket.dev/blog/gem-coo...
Reposted by Xavier Noria
chaelcodes.bsky.social
Maybe from when he trademarked Bundler?
andre.arko.net/2025/09/25/b...
Elsewhere he said that he's asked them to stop distributing Bundler, and they'd asked to review it with their legal team. I can't find that quote though.
fxn.bsky.social
On the topic of music streaming, Spotify added a lossless setting recently (😱 finally!), but it is only up to 44.1 kHz.
fxn.bsky.social
It's not even clear if by then he was actually on call or had any paid duty.

And perhaps it was all so messy that you could not tell, or you could tell but with a suspicion that something could be very wrong.

I don't know.
Reposted by Xavier Noria
rkh.cool
Yes, according to that post the password change was in order to lock down the account. Which makes sense, in a way. My interpretation based on public statements would be that André failed to properly disclose it to RC (and from their perspective shouldn’t have accessed the account at all).
Reposted by Xavier Noria
bradgessler.com
I don’t know anybody who is jumping to conclusions. Most conversations I’ve been involved in or read about are people asking questions trying to understand what happened.

The only conclusions I’ve seen are that RC is terrible at communications and it’s starting to look like they’re bad at OpSec.
fxn.bsky.social
I would be surprised if that wording is ment to cover "selling".

These texts are not expressed in first-order logic and we have to take into account this is RC.
fxn.bsky.social
Policies permit selling private info?
fxn.bsky.social
I miss this kind of details in the posts by affected people.
fxn.bsky.social
Is that bass technique exploiting that harmonics may trick your mind to listen low frequencies even if they are not being produced for real?