Ouch! Rust beat Ruby SO HARD!

Поделиться
HTML-код
  • Опубликовано: 21 окт 2024

Комментарии • 8

  • @siyaram2855
    @siyaram2855 2 года назад +2

    Rust is a systems programming language. It is made with performance in mind
    Ruby is made with programmer happiness in mind.
    Programming in Ruby/Rails is a joy, can't say the same for any other system programming language, that includes rust.

    • @lindblomdev
      @lindblomdev  2 года назад +1

      Rails was the reason why I bought my first mac. I used to do ruby on rails up until rails 3.2. Writing some ruby again was really fun 😍 it could be nostalgia.
      One problem i would have with ruby today is that it would eat all my memory and (if I happened to gain some success) also consume the Cpu. Then my wallet would not appreciate decision making criteria 😅 and I would really miss types. I think crystal has types, but thats not ruby.
      What do you think is the reason why you find joy in rails development that you cannot find somewhere else? Or haven't found elsewhere yet.

    • @siyaram2855
      @siyaram2855 2 года назад

      ​@@lindblomdev Sorbet solves issues of types.
      I don't came across types related problems so I really don't care.
      DHH make too much sense to ignore. I was doing SPA + backend, from that background Rails feels like a therapy.
      Rails 7 is the best thing that has happened, as a solo developer, I can build things without worrying about the pity little things. I am focused on the product and the problem solving part, rather than the tooling and bundling nonsense.

  • @JayGodseOnPlus
    @JayGodseOnPlus 2 года назад +2

    The performance differences are staggering!

  • @RR-et6zp
    @RR-et6zp 2 года назад

    can you make a web backend with rust? How much faster would it be compared to Rails ?

    • @lindblomdev
      @lindblomdev  2 года назад

      Yes, rust works great for web backends. I would be surprised if you couldn't execute a request handler faster in your rust based solution (unless all you do is wait for i/o). With that said, rails is a batteries included framework. Depending on how much you use of that, you might need to solve the issues rails solved on your own. There might be many ways that you can mess that up and end up with a solution that is perceived as slower to the end user even if the server is executing faster and can handle more requests per second. If you are using rails as an api only, then rails might not be the best fit for you and a more light weight ruby framework would be a better fit and easier to transition to.

  • @yaroslav-harakternik
    @yaroslav-harakternik 2 года назад

    Thanks for your work