Lightnews — Scholar-powered news

Jean Boussier @byroot.bsky.social · 21h

Does it really matter much in practice? TrueClass and FalseClass have basically no methods on them.

I bet you could replace `true` by `Object` (or some other constant) in most codebase and they'd still work.

2

Jean Boussier @byroot.bsky.social · 1d

Yup, just saying I would have named `boolish` -> `bool` and `bool -> Boolean`.

But I'm not a static typing enjoyer so 🤷

Jean Boussier @byroot.bsky.social · 1d

And another to encode that the value will be an instance of either `TrueClass` or `FalseClass` for the purpose of calling a method on it.

Given the conditional case is more common IMO, that's what I would have named `bool`, and the `true | false` type I would have named `Boolean`.

Jean Boussier @byroot.bsky.social · 1d

Not a fan of the naming either. The discussion in github.com/ruby/rbs/iss... is interesting.

Regardless of the naming, there is indeed a need for two "bool" types.

One to encode that the value will be used in a conditional (more common I suspect).

Add a shorthand for "TrueClass | FalseClass" · Issue #133 · ruby/rbs

I see in syntax.md there's a bool type, but it allows "nil or any other values", which seems to defeat the purpose a bit. I'd expect passing anything other than true or false to warn, because other...

github.com

2

Reposted by Jean Boussier

Robby Russell @robbyonrails.com · 2d

Ruby Central’s made some tough… and yeah, rough… calls lately.
I still think they deserve a second act.

robbyonrails.com/articles/202...

Organizations, Like Code, Deserve Refactoring | Robby on Rails

I’ve been thinking about what happens when open source organizations hit their breaking point… when funding dries up, relationships fracture, and everyone’s ...

robbyonrails.com

1 2 16

Jean Boussier @byroot.bsky.social · 2d

I usually use the round method for that: docs.ruby-lang.org/en/master/Ti...

class Time - Documentation for Ruby 3.5

class Time: Time. t = Time.

docs.ruby-lang.org

1 6

Jean Boussier @byroot.bsky.social · 2d

Sorry you took it that way, my point really isn't about personal relationships, or even specific people here (I'm still thankful for the ruby-head/Gemfile.lock fix from Euruko BTW).

I really mean it when I say it's about structures and incentives, not individuals.

1 3

Jean Boussier @byroot.bsky.social · 2d

Alright my bad then. I'm still trying to piece things together.

1 1

Jean Boussier @byroot.bsky.social · 2d

While I'm just as appalled as you at the RC communication so far, I do understand that corporations/associations have to worry about legal consequences of their communication.

At least I hope that's the reason.

1 4

Jean Boussier @byroot.bsky.social · 2d

About 6 days 😫. And yes, it was hard to find way to get my points across without triggering knee jerk reactions.

4

Jean Boussier @byroot.bsky.social · 2d

I do hope we'll get to the bottom of this one day.

To be clear, and I think I say it in the post, I don't believe one bit the accusations toward my former teammates, but I have very little knowledge of what really happened inside RC, so I stay open minded for now.

3

Jean Boussier @byroot.bsky.social · 2d

Right, and Hiroshi and Colby were employees, while others weren't I presume?

If the contributors agreements indeed didn't exist that's very concerning to me. But I also wonder how much of all this was intended versus happened because they expected a different reaction from maintainers.

2 1

Jean Boussier @byroot.bsky.social · 2d

Who is "us" though? What I get from Freedom's post is that RC only wanted some maintainers removed, but the others chose to leave on their own.

Or at least not to sign the agreements. But I don't know what was in these agreements so I don't know if it was a position of principle, or something else.

1

Jean Boussier @byroot.bsky.social · 2d

Aaron opened a pull request to improve performance!! You see there is a conspiracy!!

1 9

Reposted by Jean Boussier

Stan Lo @st0012.dev · 2d

Thank you for writing this, especially:

> Aaron got nerd sniped into making Bundler faster, and now he’s being called out for supposedly being part of a hostile takeover? Give me a break.

Jean Boussier @byroot.bsky.social · 2d

I tried to explain why I don't believe the recent accusations toward my former teammates, as well as how the Ruby and Rails Infra team at Shopify operates and why it can be trusted.

byroot.github.io/opensource/r...

Dear Rubyists: Shopify Isn’t Your Enemy

I’ve been meaning to write a post about my perspective on Open Source and corporate entities. I already got the rough outline of it; however, I’m suffering from writer’s block, but more importantly, t...

byroot.github.io

6 23

Jean Boussier @byroot.bsky.social · 2d

As discussed recently, I don't like the "gift" analogy: bsky.app/profile/byro...

But yes. I think most people realize Shopify is contributing a lot, but they still are underestimating how much.

Jean Boussier @byroot.bsky.social · 13d

It's more of a personal pet peeve, but I don't like the "gift" analogy. A gift is very take it or leave it and one sided. That works if you just open source some code and forget about it.

But also it justify seeing simple users as "freeloaders", a term that makes no sense for software IMO.

2 5

Jean Boussier @byroot.bsky.social · 2d

I tried to explain why I don't believe the recent accusations toward my former teammates, as well as how the Ruby and Rails Infra team at Shopify operates and why it can be trusted.

byroot.github.io/opensource/r...

Dear Rubyists: Shopify Isn’t Your Enemy

I’ve been meaning to write a post about my perspective on Open Source and corporate entities. I already got the rough outline of it; however, I’m suffering from writer’s block, but more importantly, t...

byroot.github.io

11 36 90

Jean Boussier @byroot.bsky.social · 3d

Ah yeah, this one can be though, but there are multiple ways to make it easier through exploration (get rid of some enemies, get allies, etc).

Also some tools do trivialize the fight.

Jean Boussier @byroot.bsky.social · 3d

What are you stuck on?

1 1

Jean Boussier @byroot.bsky.social · 4d

This is by far the most sensible take ever since all this mess started.

Glad there are still some people capable making the difference between unsubstantiated conspiracy theories and proper reporting of facts.

Thank you ❤️

Code and the Coding Coders who Code it @codingcoders.bsky.social · 4d

🎙️ New (Bonus) Episode of Code and the Coding Coders who Code it, with @andrewm.codes and @chaelcodes.bsky.social

podcast.drbragg.dev/episodes/rub...

#ruby #Rails #code #coding #coders #podcast #rubycentral #bundler #rubygems

Ruby’s Trustquake

We talk about Ruby, Rails, JavaScript, and everything in between. From tiny tips to bigger challenges we take on 3 questions a show; What are you working on? What's blocking you? What's something cool...

podcast.drbragg.dev

1 9 28

Reposted by Jean Boussier

Robby Russell @robbyonrails.com · 5d

Delighted to share this deep dive into how Doctolib's team has been speeding up their test suite...when they have 10 databases, 84k tests, with over 3M LOC.

onrails.buzzsprout.com/2462975/epis...

Florent Beaurain: Optimizing Rails Tests at Doctolib Scale - On Rails

In this episode of On Rails, Robby is joined by Florent Beaurain, a longtime Rails engineer at Doctolib, home to one of the largest Rails monoliths in Europe with over 3 million lines of code and 400+...

onrails.buzzsprout.com

1 3 8

Jean Boussier @byroot.bsky.social · 8d

I don’t know much about Hanami, but I suspect nothing prevents you from using Active Job with it.

1

Jean Boussier @byroot.bsky.social · 10d

Does the community want that? I personally don't care how the sausage is made as long as I trust it's made in the general interest. I think that's what has been broken and need repairing here.

My take is that Ruby's governance is very largely trusted in the community.

2

Jean Boussier @byroot.bsky.social · 10d

All these years are just a blurry mess for me.

1 2

Jean Boussier @byroot.bsky.social · 10d

Yes, we first met at the gathering in London late 2020, and then again recently at Ruby Kaigi.

2 1