5 ms·

> is anybody still excited about Ruby when Rails isn't involved? Far more excited than I am about JS when the browser isn't involved. > what modern SaaS offer

by ericb 4y ago

> is anybody still excited about Ruby when Rails isn't involved? Far more excited than I am about JS when the browser isn't involved. > what modern SaaS offerings are choosing Rails Github, Airbnb, Shopify, Constant Contact, SlideShare, CrunchBase, Bloomberg, Yammer, GitLab, ZenDesk, Hashicorp, Hulu, Netflix.

reducesuffering 4y ago
GitHub is actively transitioning away from Rails. Netflix is mostly Java / Node.js, they are not a significant Rails shop. Also, OP said "modern", probably to mean not companies that chose their tech stack a decade ago. New SaaS these days trend towards Next.js / Node (Supabase, Substack, Notion, Planetscale, Railway, Secureframe, Newfront, etc.), some Django, the occasional Rails or Phoenix.
- AlchemistCamp 4y ago
  Supabase wrote their backend in Elixir. AFIK, their offering started as essentially “various stuff common in Elixir systems, as a service for JS devs”. More here: https://thinkingelixir.com/podcast-episodes/073-elixir-at-supabase-with-paul-copplestone/ https://thinkingelixir.com/podcast-episodes/073-elixir-at-su...
  - reducesuffering 4y ago
    Yes, some portion of their backend is Elixir/Phoenix: https://github.com/supabase/realtime https://github.com/supabase/realtime but most of their current stack and active development, frontend and backend, is Next.js, and not the Rails/Phoenix fullstack way: https://github.com/supabase/supabase https://github.com/supabase/supabase
    - kiwicopple 4y ago
      I just did a full write up on the Architecture becaase we have this question often: https://supabase.com/docs/architecture#architecture https://supabase.com/docs/architecture#architecture > most of their current stack and active development, frontend and backend, is Next.js This is only the Dashboard. We dogfood Supabase to build Supabase, so we use the tools in the doc above
      - reducesuffering 4y ago
        No better clarification than the author! In my mind, I was thinking of just the web framework UI-for-CRUD comparison, where Next.js is supplanting what Rails is typically used for (like your Dashboard / GUI, and most of the core webapps for the previous 2010 Rails co's), but fair enough, you're probably leveraging a lot more of your own PostgREST, triggers, functions, & webhooks than a typical backend Next shop.
- jrochkind1 4y ago
  > GitHub is actively transitioning away from Rails Cite?
  - reducesuffering 4y ago
    https://www.theregister.com/2018/08/16/github_rails_microsoft/ https://www.theregister.com/2018/08/16/github_rails_microsof... "GitHub is about a third of the way through an architectural change that began last year. The company is moving away from Ruby on Rails toward a more heterogeneous, composable infrastructure. Ruby still has a place at GitHub – Lambert referred to the company as a Ruby shop, but he said there's more Go, Java and even some Haskell being deployed for services." https://github.blog/2021-03-16-improving-large-monorepo-performance-on-github/ https://github.blog/2021-03-16-improving-large-monorepo-perf... "We’re also in the middle of a significant refactoring effort, doing our part to decompose GitHub’s famous Ruby monolith, and writing a new microservice in Go"
    - ericb 4y ago
      He referred to the company as "a Ruby shop" so maybe that's a bit overstated?
      - reducesuffering 4y ago
        No major company completely overhauls their tech stack overnight. I originally stated that they're transitioning away from Ruby so I don't think that's overstated, they are. Just like Twitter, LinkedIn, Soundcloud, Grab, Parse, Twitch, and Deliveroo have done before them, it's not unique. It's 20 years ahead of Perl, but same fate. It doesn't have a niche besides web w/ Rails, which javascript/typescript is now dominating. It's the slowest and has the most well-known scale problems. The dev ecosystem is almost unanimously moving towards static types, a la Typescript and MyPy. It's symbols are not as transferable like more popular C-based langs: Javascript, Java, Python, Go. The only point devs will routinely point to in favor of it is "well, it just feels fun and nice to work with", while actually StackOverflow survey data shows Rust, Typescript, Python all leagues ahead in "loved", while Ruby is in majority dissatisfaction land right next to the monstrosities of C++ and Scala.

by ericb 4y ago

reducesuffering 4y ago

GitHub is actively transitioning away from Rails. Netflix is mostly Java / Node.js, they are not a significant Rails shop. Also, OP said "modern", probably to mean not companies that chose their tech stack a decade ago. New SaaS these days trend towards Next.js / Node (Supabase, Substack, Notion, Planetscale, Railway, Secureframe, Newfront, etc.), some Django, the occasional Rails or Phoenix.

AlchemistCamp 4y ago
Supabase wrote their backend in Elixir. AFIK, their offering started as essentially “various stuff common in Elixir systems, as a service for JS devs”. More here: https://thinkingelixir.com/podcast-episodes/073-elixir-at-supabase-with-paul-copplestone/ https://thinkingelixir.com/podcast-episodes/073-elixir-at-su...
- reducesuffering 4y ago
  Yes, some portion of their backend is Elixir/Phoenix: https://github.com/supabase/realtime https://github.com/supabase/realtime but most of their current stack and active development, frontend and backend, is Next.js, and not the Rails/Phoenix fullstack way: https://github.com/supabase/supabase https://github.com/supabase/supabase
  - kiwicopple 4y ago
    I just did a full write up on the Architecture becaase we have this question often: https://supabase.com/docs/architecture#architecture https://supabase.com/docs/architecture#architecture > most of their current stack and active development, frontend and backend, is Next.js This is only the Dashboard. We dogfood Supabase to build Supabase, so we use the tools in the doc above
    - reducesuffering 4y ago
      No better clarification than the author! In my mind, I was thinking of just the web framework UI-for-CRUD comparison, where Next.js is supplanting what Rails is typically used for (like your Dashboard / GUI, and most of the core webapps for the previous 2010 Rails co's), but fair enough, you're probably leveraging a lot more of your own PostgREST, triggers, functions, & webhooks than a typical backend Next shop.
jrochkind1 4y ago
> GitHub is actively transitioning away from Rails Cite?
- reducesuffering 4y ago
  https://www.theregister.com/2018/08/16/github_rails_microsoft/ https://www.theregister.com/2018/08/16/github_rails_microsof... "GitHub is about a third of the way through an architectural change that began last year. The company is moving away from Ruby on Rails toward a more heterogeneous, composable infrastructure. Ruby still has a place at GitHub – Lambert referred to the company as a Ruby shop, but he said there's more Go, Java and even some Haskell being deployed for services." https://github.blog/2021-03-16-improving-large-monorepo-performance-on-github/ https://github.blog/2021-03-16-improving-large-monorepo-perf... "We’re also in the middle of a significant refactoring effort, doing our part to decompose GitHub’s famous Ruby monolith, and writing a new microservice in Go"
  - ericb 4y ago
    He referred to the company as "a Ruby shop" so maybe that's a bit overstated?
    - reducesuffering 4y ago
      No major company completely overhauls their tech stack overnight. I originally stated that they're transitioning away from Ruby so I don't think that's overstated, they are. Just like Twitter, LinkedIn, Soundcloud, Grab, Parse, Twitch, and Deliveroo have done before them, it's not unique. It's 20 years ahead of Perl, but same fate. It doesn't have a niche besides web w/ Rails, which javascript/typescript is now dominating. It's the slowest and has the most well-known scale problems. The dev ecosystem is almost unanimously moving towards static types, a la Typescript and MyPy. It's symbols are not as transferable like more popular C-based langs: Javascript, Java, Python, Go. The only point devs will routinely point to in favor of it is "well, it just feels fun and nice to work with", while actually StackOverflow survey data shows Rust, Typescript, Python all leagues ahead in "loved", while Ruby is in majority dissatisfaction land right next to the monstrosities of C++ and Scala.