Is Ruby On Rails Too Slow!? 😱
HTML-код
- Опубликовано: 6 фев 2025
- Ruby on Rails is too slow, and I can prove it with numbers! Everyone should go learn GoLang or Rust instead. 😤
Checkout my course(s) at: learn.deanin.com
Benchmarks are from this website:
programming-la...
Join this channel to help support these videos:
/ @deanin
Follow me on social media:
linktr.ee/deanin
If you liked this video, please consider subscribing: t.co/RZ4EwP0F2a
#Deanin #Software #Programming
Rails is only too slow if you need something fast, which most people won't need.
Give me the fastest programming language in the world and I'll slow it to a crawl with my spaghetti code. 😤
This is ridiculous, I came here to be offended but not personally attacked. My code isn't spaghetti! 😠
@@Deanout lol 😅😅, dean you the best
Shopify disagrees
I somehow doubt Shopify disagrees, but okay lol.
@@Deanin hahaha I meant disagreen on been slow
The app you build in Rails in a day would take you a week or two(even a month) in Go or Rust. This is the speed benchmark that will matter in real life.
Word.
And Scale a RoR app take months. Pros and Cons.
@@thundergabriel Dude, What are you even taking about?Rails is super easy to scale.
Ever heard of kubernetes and container?
Na
@@siyaram2855 Sometimes people just forget that not only microservices can be scaled using containers... Plus you can always rewrite bottlenecks in a rust or other very performant language. No need to write the whole project in rust when you just starting.
If you want something fast as a Ruby developer you can try Amber or Lucky for Crystal. Crystal is very close to Ruby's syntax so there is not that much to learn more.
I tend to leverage GFY when told Rails is dead. It starts with a Go and ends with a Yourself :)
This is so elegant. 🤣👍
hmmm that's strange comparaison.. a language vs a framework ? yeah ruby in itself is slow, could save microseconds here and there... but in practice, pretty much every latency I ever had on a project came from server issues, disk space, bad db indexing or queries, n+1 queries, network issues & so on... I'm pretty sure it's possible to mess that up in golang or rust too
this dude and I have very different ideas of what a love child is
Ruby can go away and you can sleep just fine! Woah your heartless. 😂
Nobody uses rails to go from 1 to 100, it is used to validate your idea for product market fit and build iterations from 1 to 10 maybe. Once you reach that scale you can hire devs that will help you scale your lanuage
Good video! Fast description. wink.
I once wrote my websites search crawler that processed millions of sites. First i did it with php. Then i wrote it in go and it became at least 10x faster. It run multiple http requests in parallel. With go i hit the limit of possible connections on my linux laptop... also linux gave 2x or so boost comparing to windows in php
ScrapyCluster?
Better algorithm, better performance. No language or framework makes your app faster
This is just incorrect lmao
Tell me you've never worked on large scale software without telling me you've never worked on large scale software
I don't use golang for performance i use it for readability and simplicity
Have you used ruby?
@@jsalguero94 No so i have nothing good or bad to say about it.
@@JasonJA88 ok because ruby is also readable and simple. I have used both, both has pros and cons.
@@jsalguero94 Ruby is alright, but with Go there are numerous idiosyncrasies on top of a very lean syntax means you can go line by line and know explicitly what happens. Ruby's syntax looks pretty, but there are 20 different methods to do the same thing, and can very quickly lead to some really stupid code golf that makes it hard to know exactly what's happening, or even what the code's purpose is.
Waiting peoject like rails writing in go
Likely won't happen. The Go community has a very strong DIY, and "never gonna need it" dogma built into it. They do everything by hand and import small packages only for specific things that do one thing, like a session manager, or router.
I start coding my app only after I get a million confirmed users who will promise my server 1000's of times a second. :D
How dare you be practical! Be unreasonable like the rest of us lol
In my view we should start with Ruby its pretty fast and when you want more speed migrate the code to Crystal, which is largely compatible with ruby syntax. And easier to migrate the code base to crystal than to deal with oddities of converting highly OOP code base to a procedural one like Golang. Correction: I am aware Golang has interfaces and does support some OO but ruby and crystal are a different league altogether. Also crystal beats the b'jesus out of Go.
The problem with migrating to crystal later on is there isnt nearly as many shards as there are gems, so migrating could be a huge pain. would be better off to just start there. the productivity levels between writing ruby and writing crystal arent hugely different
@@tylerbonklevoss8986 Well yeah, but since it supports C lib calling conventions building shards that call C lib functions is not that hard. Build the ones that you need. But good point! Overall i think we have to see how to save programmer time which is the most expensive thing here.
good!