How to build a search engine with Ruby on Rails
blog.testdouble.com
How to build a search engine with Ruby on Rails
1–10 of 65 posts
Re: How to build a search engine with Ruby on Rails
#2Re: How to build a search engine with Ruby on Rails
#3This is a bit off topic but I wanted to say I’m really glad there are still people out there hacking on some ruby + Postgres projects and writing about it. I feel that ruby is an excellent language and dread the demise of it.
Re: How to build a search engine with Ruby on Rails
#4This is a bit off topic but I wanted to say I’m really glad there are still people out there hacking on some ruby + Postgres projects and writing about it. I feel that ruby is an excellent language and dread the demise of it.
Re: How to build a search engine with Ruby on Rails
#5This is a bit off topic but I wanted to say I’m really glad there are still people out there hacking on some ruby + Postgres projects and writing about it. I feel that ruby is an excellent language and dread the demise of it.
Re: How to build a search engine with Ruby on Rails
#6This is a bit off topic but I wanted to say I’m really glad there are still people out there hacking on some ruby + Postgres projects and writing about it. I feel that ruby is an excellent language and dread the demise of it.
How is it demised? Shopify, Stripe and many new YC startups use it.
Ruby hasn't evolved much either.
Rails only scales so far and then scaling gets really challenging, obviously the named companies have figured it out, but its not easy. For example, rails due to the high coupling between models and the database, rspec test get very contrived trying to setup the db state for each test run. Compared to other languages like Python or golang where the sql-layer is abstracted from the model layer.
Compared to languages like Python which provide very similar developer experiences but also the power of ML modeling, ruby is falling behind.
Re: How to build a search engine with Ruby on Rails
#7Earlier quoted context omitted.
How is it demised? Shopify, Stripe and many new YC startups use it.
Rails hasn't had any interesting updates since version 4, and arguably introduced a few regressions IMHO (I'm looking at you, active storage and action cable) Ruby hasn't evolved much either. Rails only scales so far and then scaling gets really challenging, obviously the named companies have figured it out, but its not easy. For example, rails due to the high coupling between models and the database, rspec test get…
Re: How to build a search engine with Ruby on Rails
#8This is a bit off topic but I wanted to say I’m really glad there are still people out there hacking on some ruby + Postgres projects and writing about it. I feel that ruby is an excellent language and dread the demise of it.
How is it demised? Shopify, Stripe and many new YC startups use it.
Re: How to build a search engine with Ruby on Rails
#9Earlier quoted context omitted.
How is it demised? Shopify, Stripe and many new YC startups use it.
I think it's easy to say it's declining based on things like Red Monk's ranking, but with GitHub, Stripe and Shopify behind it, it's not going anywhere soon. And apparently Rails us is slowly increasing: https://arstechnica.com/gadgets/2021/09/php-maintains-an-eno...
Re: How to build a search engine with Ruby on Rails
#10Earlier quoted context omitted.
Rails hasn't had any interesting updates since version 4, and arguably introduced a few regressions IMHO (I'm looking at you, active storage and action cable) Ruby hasn't evolved much either. Rails only scales so far and then scaling gets really challenging, obviously the named companies have figured it out, but its not easy. For example, rails due to the high coupling between models and the database, rspec test get…
I highly doubt that you will reach the scaling limits of rails unless you have a massive product and even if you do Python would not be a good replacement.
But there are more things in the world than CRUD apps. I'm building tools to track hate on social media, and there's a lot of social media out there. Rails, or any RDBMS-centered architecture, won't cut it. And if you're not using Rails, then I think the case for using Ruby isn't very strong these days; Python has a bigger community and is much stronger in important niches, like ML. So we picked Python as our default language not because the Python runtime is vastly more efficient than the Ruby one, but because the ecosystem is a much better match for our needs.
I wish it were the other way, as honestly I like Ruby better as a language. But my personal tastes are ultimately a pretty small factor when I'm picking the tooling for a project.