Congratulations to the team. Oxide & Friends, Bryan, Adam & Team are such a valuable resource to our community. Their podcast is amazing, the problems they encounter, and their willingness to share with the rest of us is not taken for granted!
Its a personal project? Do you truly believe that individuals are required to have the foresight into how their project will get adopted or viewed by the community that it would require them to create a separate github account to host it under?
Roblox has 43+ million daily active users. The issue you are wildly speculating about is enormously small compared to their size and scale. I guarantee you they’ve dealt with that potential issue (if they even are using Postgres) years ago.
The landing page seems to provide absolutely zero information other than giving off the impression that something may be taking an extremely long time to load.
Edit: Seems to just be completely broken in Firefox...
Regardless it helped them initially scale and attract users by shipping features and focusing on proving their business. Down the road as they attracted users they kept their rails core but started adding in other systems that were met their performance needs.
Rails allows companies to grow quickly and focus on attracting users and delivering business value at the sacrifice of a re-write or complexity of managing rails and performance issues down the road.
I'm not sure why this continually comes as such a surprise on HN. It's a mature framework with tons of community involvement and 3rd party gems to help ship features out the door.
The vast amount of projects and internal tools out there don't need to be "webscale" or process millions of requests a minute.
Maybe not for all parts of the U.S. campuses, sure. Those facilities aren't producing hundreds of thousands of new iPhones everyday. It wouldn't surprise me if there were similar security measures in place for areas where prototypes and sensitive information are handled though.
Not once does the article mention Bugsnag or try to market their product. Who is to stop an enthusiastic engineer from sharing a workflow they find useful. The article has great content and powerful visuals to help convey their point. I'm happy to see companies not try to influence authors to plug their product in their blog posts.