byroot

8 ms·

1.
by byroot 16d ago
> Uses 1.5GB of RAM on my laptop atm. That's crazy, I just checked on mine (macOS), it's only ~300MiB, about as much as Apple Mail which is native. Still a bit much for what I need it for, but tolerable.
2.
by byroot 2mo ago
Nope. It’s been the default MRI parser for a couple years now.
3.
by byroot 2mo ago
TruffleRuby is pretty close too, if anything it’s even a bit more compatible because it’s able to run native extensions. Also keeping compatible with MRI have been made significantly easier by Prism, the new parser that is shared by all imp
4.
by byroot 2mo ago
> lost 3 of 3 members of the Open Source Committee (Gabi, Mike, Ufuk) This is rich given they left in big part because of how much abuse they have received by "supporters" of André & co...
5.
by byroot 2mo ago
There's a public survey: https://surveys.ecb.europa.eu/10b/neweuro/
6.
by byroot 2mo ago
That's why C23 introduce free_sized [0]. [0] https://en.cppreference.com/c/memory/free_sized
7.
by byroot 5mo ago
Similarly, when writing Facebook apps with Rails, when you'd hit that same bug you'd see Mark Zuckerbeg: https://www.facebook.com/profile.php?id=4
8.
by byroot 5mo ago
It was just one of many. Alone it wouldn't have been very noticeable, but I did many small optimizations like that, which ultimately shaved about 20 seconds of setup time. Looking from another angle, the app boot time on CI (not eager
9.
by byroot 5mo ago
https://github.com/ruby/ruby/blob/master/NEWS.md
10.
by byroot 5mo ago
Nothing ground breaking we simply deploy Buildkite agents on EC2 nodes. As mentioned in the post, the only thing really limiting CI parallelism is the ratio of "setup time" vs "test time". If your setup time is too long,
11.
by byroot 5mo ago
Aside from the oddness of making this cache git aware, with the new implementation I suspect querying git to revalidate the cache would take longer than just rebuilding it.
12.
by byroot 5mo ago
> every method call is a string dict lookup Doesn't the Python VM have inline caches? [0] https://en.wikipedia.org/wiki/Inline_caching
13.
by byroot 5mo ago
Nitpick, but France never left NATO proper, only the integrated command, and reintegrated it in 2008 under Sarkozy.
14.
by byroot 8mo ago
That's also something Rails helps abstract away by automatically deferring enqueues to after the transaction completed. Even SolidQueue behave that way by default. https://github.com/rails/rails/pull/5142
15.
by byroot 8mo ago
> The ideal situation with Rails would be if there is a simple way to switch back to Redis That's largely the case. Rails provide an abstracted API for jobs (Active Job). Of course some application do depend on queue implementation
16.
by byroot 9mo ago
You are describing bootsnap. And yes I proposed to integrate bootsnap into bundler ages ago, but got told to go away.
17.
by byroot 9mo ago
> none of the providers really do this out of the box CircleCI does. And I'm sure many others.
18.
by byroot 9mo ago
> My experience with GHA default caches is that it’s absolutely dog slow. GHA is definitely far from the best, but it works:, e.g 1.4 seconds to restore 27 dependencies https://github.com/redis-rb/redis-client/a
19.
by byroot 9mo ago
GHA with the `setup-ruby` action will cache gems. Buildkite can be used in tons of different ways, but it's common to use it with docker and build a docker image with a layer dedicated to the gems (e.g. COPY Gemfile Gemfile.lock; RUN b
20.
by byroot 9mo ago
Ye,s but if your CI isn't terrible, you have the dependencies cached, so that subsequent runs are almost instant, and more importantly, you don't have a hard dependency on a third party service. The reason for speeding up bundler
21.
by byroot 9mo ago
I know that tweet, it's real, but that doesn't contradict my comment. They indeed replaced Unicorn by Falcon in one application, but falcon is configured in "Unicorn mode" (no concurrent requests). So the gain is effecti
22.
by byroot 9mo ago
> GC still stops the world, right? Yes, Ractor local GC is the one feature that didn't make it into 4.0. > Can't you just have completely separate boxes with their own copies of all classes etc, or does that use too much mem
23.
by byroot 9mo ago
They already truly run in parallel in Ruby 4.0. The overwhelming majority of contention points have been removed in the last yet. Ruby::Box wouldn't help reducing contention further, they actually make it worse because with Ruby::Box c
24.
by byroot 9mo ago
> It seems Ractor is still work in progress The Ractor experimental status could almost be removed. They no longer have known bugs, and only one noticeable performance issue left (missing Ractor local GC). But the API was just recently c
25.
by byroot 9mo ago
It was removed because rubygems was made to be required by default so it was now useless. The stdlib still contains `un.rb` though: https://github.com/ruby/ruby/blob/d428d086c23219090d68eb2d02...
26.
by byroot 10mo ago
> They aren't interned frozen strings Doesn't matter. The parent claim was: > You'd just have a broken VM if you used mutable strings for metaprogramming in Ruby From day one it was possible to freeze strings used in me
27.
by byroot 10mo ago
Ruby always had immutable (frozen) strings, so no, this never was a reason for Symbols existence.
28.
by byroot 10mo ago
HashWithIndifferentAccess was added because back in the day symbols were immortal, hence could not be used for request parameters. It no longer make sense today, and any new use of it is a smell.
29.
by byroot 10mo ago
No they’re not. String can be interned in Ruby, but it’s always possible for an equal string that is not interned to also exist. Hence interned strings can’t benefit from the same optimization than symbols. You can first compare them by poi
30.
by byroot 10mo ago
Is it? Smaller business usually comes with smaller applications. Most cloud and hardware vendors give you about 4GiB of RAM per core, maybe only 2 when using "CPU optimized instances", that's huge and leave plenty of space fo

More ›