Building a robust data synchronization framework with Rails
1–9 of 9 posts
Re: Building a robust data synchronization framework with Rails
#2Ruby reads like a charm and makes these examples so elegant. It truly shows that the language was optimized for developer happiness.
Re: Building a robust data synchronization framework with Rails
#3Really elegant stuff, thank you for sharing.
Re: Building a robust data synchronization framework with Rails
#4Hey Philippe! Very nice to see this from you. Looks great.
Re: Building a robust data synchronization framework with Rails
#5Ruby reads like a charm and makes these examples so elegant. It truly shows that the language was optimized for developer happiness.
Does everyone that loves Rails also love Ruby? I'm not one of them. I personally think Ruby is awful but Rails is incredible.
Re: Building a robust data synchronization framework with Rails
#6Ruby reads like a charm and makes these examples so elegant. It truly shows that the language was optimized for developer happiness.
Does everyone that loves Rails also love Ruby? I'm not one of them. I personally think Ruby is awful but Rails is incredible.
I'm curious how you can find rails incredible while simultaneously hating ruby? Rails takes a lot of its inspiration from the language itself (internals relying heavily on metaprogramming, lots of exploitation of ruby's quirks all over the place). Like, what do you like about rails and what do you hate about ruby and how do those two things not overlap?
Re: Building a robust data synchronization framework with Rails
#7Ruby reads like a charm and makes these examples so elegant. It truly shows that the language was optimized for developer happiness.
Does everyone that loves Rails also love Ruby? I'm not one of them. I personally think Ruby is awful but Rails is incredible.
I like Ruby a lot, but I find it large codebases get convoluted since it doesn't have a proper typing system. RBS doesn't count lol. Even RubyMine by JetBrains gets confused with classes and such in a "large" codebase I wrote (50k lines give or take). And that's with doing things the proper Ruby/Rails way, with full RBS files for everything.
Re: Building a robust data synchronization framework with Rails
#8An odd choice of language for something with such robustness and scalability requirements. I love ruby, but for this?
Re: Building a robust data synchronization framework with Rails
#9An odd choice of language for something with such robustness and scalability requirements. I love ruby, but for this?
Hey Martin,
All our services are built using Ruby, so it's the obvious choice. It scales and it's robust. We might just spend a little bit more on Heroku than if we'd use another language such as go - but it's definitely not worth introducing a new language to our stack.
Thanks for the comment!