Building Robust APIs with Ruby on Rails: A Glimpse into Modern Web Development
Building Robust APIs with Ruby on Rails: A Glimpse into Modern Web Development
I like RoR but "Ruby on Rails" and "modern" in the same sentence seems kind of funny.
But then again, "modern" is subjective in itself and most of the websites I see these days (even built and maintained by large companies) seem pretty ancient.
No semantic HTML, still using
divs everywhere, no accessibility, all these useless third-party dependencies and lockins vs the new APIs being introduced natively in the browser every day, ajax, jquery instead of using the web platform, hell-- most web developers don't even know what a dialog element is.15I've never actually heard of most of that. I've never heard of semantic HTML and I don't know what a dialog element is.
I think a part of the problem is there are a lot of people doing web development that never actually learned it. I'm a backend developer who occasionally has to do web development and I never learned web dev. All my training was with databases and serverside code and all my coworkers are the same.
7As someone who has worked with RoR in the last year, they've come a LONG way in the last three years.
Take a look at Turbo/Hotwire and other new implementations in RoR. They eliminate like 90% of the necessary Javascript and the libraries are reliable which is nice. A guarantee not always found in the npm ecosystem.
Plus they did create a lot of web development ideas/concepts that were later integrated into the "modern" approach of web development.
I will say though that article is sparse and not informative of modern Rails.
Here is a better article: https://www.monterail.com/blog/why-ruby-on-rails-development
3
Ruby on Rails
modern
Lol
2