Live data from Hacker News

Viewing profile — maxime_cb

maxime_cb

HN member
Joined
Mon, Dec 06, 2021, 7:25 AM UTC
HN karma
429
Public activity
75 items

About maxime_cb

No profile information was provided.

Recent public activity

  1. story
  2. comment
    Comment #49183132

    Thanks :) I've made a couple of music apps over the years, including one of the oldest JS music apps on the web, that also does URL encoding: https://pointersgonewild.com/2012/04/2…

  3. story
    Show HN: I built one of the most advanced web-based drum/beat sequencers

    Hi there! Just wanted to share an open source music project I've been working on. There are already a number of web-based drum machines, but I think most of them are pretty basic (…

  4. comment
    Comment #47473999

    I gave a talk about ZJIT and the motivation for the change at RubyKaigi 2025 if people are curious. It's on YouTube.

  5. comment
    Comment #47470920

    Max Bernstein is now leading the team. He's also an excellent compiler engineer.

  6. comment
    Comment #44506186

    Thanks Ken. Apologies if I misunderstood the situation. I wish you all the best.

  7. comment
    Comment #44501787

    Ruby has the same unfortunate problem.

  8. comment
    Comment #44501651

    Instigator of YJIT, the CRuby JIT here. It's easy to dismiss our efforts, but Ruby is just as dynamic if not more than Python. It's also a very difficult language to optimize. I th…

  9. comment
    Comment #39458383

    YJIT is optimized primarily for web workloads. We look at rails performance a lot, but also at various other libraries that are used in that context. If you look at the headline be…

  10. comment
    Comment #39458314

    Yes, Marc Feeley was my PhD advisor. We came up with the original idea together. I also see it as a development of the work I did in my M.Sc. thesis on type-driven versioning of fu…

  11. comment
    Comment #38687279

    Hope you try again with 3.3. The improvements we've made to YJIT since Ruby 3.1 are massive.

  12. comment
    Comment #38270997

    It is enough iterations for these VMs to warm up on the benchmarks we've looked at, but the warm-up time is still on the order of minutes on some benchmarks, which is impractical f…

  13. comment
    Comment #38236945

    The article doesn't go into super deep details but we do touch on it in the paper we've recently published: https://dl.acm.org/doi/10.1145/3617651.3622982 And I went into some more…

  14. comment
    Comment #38220113

    Ruby 3.3 (coming this Christmas) will have a much faster and more memory efficient YJIT than 3.2. We've made major improvements this year.

  15. comment
    Comment #38219954

    YJIT tech lead here. On the flip side, YJIT is probably one of the most memory-efficient JIT compilers out there (for any language). I say this having spoken to other JIT implement…

  16. comment
    Comment #36226707

    And very crispy.

  17. comment
    Comment #36124309

    Looks pretty cool :)

  18. comment
    Comment #36119616

    Author here. If you've grown up in a "normal", functional family, with two loving parents, and you enjoy talking to them on the phone, you should consider yourself very lucky. I on…

  19. comment
    Comment #36118299

    > I was wondering what the author was smoking with the "ringtone & notifications" complaint. I don't remember seeing an Android phone that did not have separate volume slider for e…

  20. comment
    Comment #36118273

    Author here. The reason I tend to think it's a software bug is that it seems that the system to dispatch deliveries is automated. The subcontractors get their orders from some kind…

  21. comment
    Comment #35083801

    > However the Ruby community seem to want having their own JIT written in C more than they want performance. YJIT is written in Rust, not C, but it's also not just a matter of want…

  22. comment
    Comment #35074867

    Yes. Prior to that point we used to allocate a large chunk of executable memory upfront. We switched to mapping that memory on demand, and that alone was a huge improvement.

  23. comment
    Comment #35074576

    For anyone curious, we've been working to reduce the memory overhead and have added some stats to keep track of memory usage over time. On this graph, you can see a comparison with…

  24. comment
    Comment #35074509

    You're right that the peak performance could be on par (or even better), but, and I acknowledge that I'm biased since I'm tech lead of the YJIT team, my takeaway is: 1. Kokubun, wh…

  25. comment
    Comment #35037468

    Shameless plug: for something more approachable, I've created NoiseCraft, which runs in a web browser, has fewer primitives, and is designed to be easier for beginners to grasp: ht…