Alessandro Fazzi
looopToolsOMFG can we just talk about how awesome #ruby #sinatrarb and #active_record is! I simply cannot get why Ruby is not a more popular #programming language
Tom 🇪🇺🇺🇦🇩🇰🇬🇱🏳️🌈🏳️⚧️@looopTools “performance”
@purelyatom Compared to like Python ? or to C++ ?
@looopTools it’s always the discussion. People went to Go or Rust. But nothing really beats Ruby for me.
Mufid@looopTools wait how do you integrate AR and Sinatra? The last time I did it was PITA; might just use RoR completely already.
@mufid So it is cumbersome. I have a script that generate the base of migrations, but I have to hand write them. Then I need to add the model class, the script does that to. But after that smooth sailings.
Janne Moren@looopTools
I prefer Ruby. But Python has a large ecosystem of modules I'd miss in Ruby.
I prefer Ruby. But Python has a large ecosystem of modules I'd miss in Ruby.
Andreas Haller@looopTools Most of our backend at work is build on Sinatra and Sequel (alternative to AR). Ruby hardly get's in the way of what you want to build.
@ahx Do you have good experience with Sequel ?
@looopTools I don't think there is much of a difference between the two. If your brain already is used to how AR handles relations you sometimes have to rethink.
We use Sequel::Model as an ORM but often fall back to using raw `Sequel::Database` (`DB[:my_table]…`, which I think is a good option to have.
I sometimes think that the code would look better without using an ORM at all, because these Model classes tend to attract code that does not seem to belong there. Sequel makes that easy.
We use Sequel::Model as an ORM but often fall back to using raw `Sequel::Database` (`DB[:my_table]…`, which I think is a good option to have.
I sometimes think that the code would look better without using an ORM at all, because these Model classes tend to attract code that does not seem to belong there. Sequel makes that easy.