[phaedryx]

I recommend whatching "Ruby3: What's Missing?", a presentation Matz gave earlier this month: https://www.youtube.com/watch?v=cmOt9HhszCI

This might be misleading. That is, jump to around the 29 minute mark where he talks about the type profiler and .rbi file stuff.

[aasasd]

As a user of Homebrew, I just wonder if Ruby's ever going to have performance.

[localhostdotdev]

homebrew's performance is mostly network (git / http / https) and compilation times when needed.

also for some reason homebrew really likes to updates its index all the time (I think it got tamed in the newest version), but setting HOMEBREW_NO_AUTO_UPDATE to 1 helps a lot.

[aasasd]

With HOMEBREW_NO_AUTO_UPDATE and HOMEBREW_NO_GITHUB_API, it still gobbles up a core for a full minute to find a substring in a list of strings. Even if it looks through directories for this, I can't imagine how this task would perform so badly. It's not system cpu time primarily.

[ihuman]

Does homebrew still download sources and compile them? I thought it moved to only downloading binaries.

[bjoli]

It is no worse than python, but with the 3x3 initiative the main implementation will be a lot faster than today, which will never happen to python unless the current lead will go 180 degrees against what Guido always claimed.

[aasasd]

By the way, could you please summarize as to what biggest improvements you expect from Ruby that are against Python's policy?

[aasasd]

> It is no worse than python

Eeeeeeeh…

[bjoli]

Python and ruby have about the same speed for most common tasks (or at least in the same ballpark), IE: dirt slow once you leave the comfort of the fast parts of the runtime that are written in C.

In reality this is fast enough for most tasks.

[aasasd]

The thing is, I do some Python programming for money, and I'm having a hard time imagining what the Brew team did to make `brew search` and its other parts so slow. I'd probably have to compare strings byte by byte in Python code for that.

Might have to learn me some Ruby just to figure out this mystery.

[bjoli]

The slowness of brew isnt ruby's fault. They don't keep a local cache of the taps, but instead searches for taps using an API that interfaces with github and searches local taps, remote taps, then blacklisted taps and then probably something more. It is limited by network speed, not by string searching.

Edit: explained better here: https://github.com/Homebrew/brew/issues/3056#issuecomment-32...

[theredbox]

Yes and no. You need to basically fork the compiler and invent a new type of ruby that sacrifices certain things in favor of performance.