Y
Yorick Peterse
yorickpeterse.com · Personal blog · on HN since 2011
Yorick Peterse, a programmer and former GitLab employee, writes about programming languages, memory management, async IO, and self-hosting.
What HN saysHN commenters cite his GitLab experience and his posts on bcrypt, bootc, and returning a Framework laptop, sometimes with a skeptical tone.
22HN people shared it
6linked it in comments
37stories submitted
1.2Kstory points
4 months agolast shared
2011people per year2026
Most-shared posts
- 1What it was like working for Gitlab5 people · 461 points · first shared 2024 · 542 comments on HN
- 2Friendship ended with the garbage collector3 people · 120 points · first shared 2021 · 137 comments on HN
- 3Three HTTP versions later, forms are still a mess3 people · 12 points · first shared 2025 · 1 comments on HN
- 4The mess that is handling structure arguments and returns in LLVM3 people · 4 points · first shared 2025 · discussion on HN
- 5Asynchronous IO: the next billion-dollar mistake?2 people · 164 points · first shared 2024 · 159 comments on HN
- 6The inevitability of the borrow checker2 people · 143 points · first shared 2025 · 77 comments on HN
- 7Oga: a new XML/HTML parser for Ruby (2014)2 people · 37 points · first shared 2014 · 7 comments on HN
- 8Deciding When to Collect Garbage2 people · 2 points · first shared 2019 · discussion on HN
- 9A decade of developing a programming language2 people · 2 points · first shared 2023 · discussion on HN
- 10Funding open-source software without compromising it2 people · 2 points · first shared 2026 · discussion on HN
- 11I'm returning my Framework 162 people · 1 points · first shared 2025 · discussion on HN
- 12Use bcrypt fool2 people · first shared 2013
- 13A brief look at FreeBSD1 people · 164 points · first shared 2025 · 107 comments on HN
- 14Building a better and scalable system for data migrations1 people · 68 points · first shared 2024 · 36 comments on HN
- 15Oga (XML/HTML Parser for Ruby) 1.0 Released1 people · 7 points · first shared 2015 · 1 comments on HN
What HN people wrote when they linked it
sytse · 2015-09-18
I agree ruby is slow and it lost the race with javascript. And the lack of a corporate sponsor has a lot to do with this. At GitLab the company we think that having a company behind an open source project is a plus (although the OP was talking about a user such as Twitter instead of Ruby Inc.). We hope to do our part in helping ruby become faster, our new hire Yorick will spend 20% of his time on Rubinius http://yorickpeterse.com/articles/hello-gitlab/
Although Rails is stagnating as far as I know the library ecosystem is superior to that of others. Sure, there are more npm packages than gems. But I bet that the total complexity that Rails gems tackle is higher than what is available for Meteor. GitLab has close to 1000 non-unique dependencies https://gitlab.com/gitlab-org/gitlab-ce/blob/master/Gemfile.lock I don't think that anything in the javascript world compares. But please show me I'm wrong, I love to learn.
I think that in a few years the situation might be different. Personally I hope that Elixir and Phoenix will replace Ruby and Rails. But maybe it will be Meteor or another js framework (Sails?). But I would optimize for the next few years and build my next startup on Rails. As indicated by the OP, a rewrite can happen even when you bet on javascript.
YorickPeterse · 2026-02-28
For those looking for a more extensive article about bootc, I recently wrote about using it in https://yorickpeterse.com/articles/self-hosting-my-websites-using-boot… including a comparison to some other existing tools.
phoronixrly · 2025-12-26
You're telling me you didn't return your Framework 13 because *checks notes* its power LED was too bright[1]?
[1] https://yorickpeterse.com/articles/im-returning-my-framework-16/#power…
karolist · 2024-02-18
Not according to [1] where the author said
> This effectively results in two code paths in many parts of your platform: one for the SaaS version, and one for the self-hosted version. Even if the code is physically the same (i.e. you provide some sort of easy to use wrapper for self-hosted installations), you still need to think about the differences.
1. https://yorickpeterse.com/articles/what-it-was-like-working-for-gitlab…
moondowner · 2013-07-29
+1 for bcrypt and related solutions.
http://yorickpeterse.com/articles/use-bcrypt-fool/
http://codahale.com/how-to-safely-store-a-password/
blhack · 2013-03-26
Because you mentioned bcrypt, it might be a good time for everybody to read this:
http://yorickpeterse.com/articles/use-bcrypt-fool/
(sidenote: GCHQ cannot reverse bcrypt. Jgrahamc was making a joke.)