Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ruby on Rails: The Documentary [video]

youtube.com

Post reply on HN
Print view View original

41–50 of 248 posts

Re: Ruby on Rails: The Documentary [video]

#41

Post by AlchemistCamp »

monooso wrote: post #16
Towaway69 wrote: post #12

Earlier quoted context omitted.

True, nodejs really doesn't have _the_ framework. Python had flask, php is WordPress and RoR. Why is that? Especially since most of the new frameworks copy the ideas of existing frameworks. P.S. Perhaps because a JS framework based off the ideas of rails would be called jails! /s

Laravel would be a better example for PHP, especially as it borrowed so many ideas from Rails.

I agree. The only frameworks I’ve found about as productive as Rails are Laravel and Phoenix.

Django and Sails.js both seemed like they were a step down in terms of general productivity, though each had a unique advantage of their own (admin out of the box, websockets & realtime features).

I haven’t had a chance to really give RedwoodJS a trial run, but it's the JS-based fullstack framework I'm most curious about.

Re: Ruby on Rails: The Documentary [video]

#42

Post by chris_st »

lagniappe wrote: post #32

sad to see _why the lucky stiff left out, but I suppose it is what he'd have wanted.

Don't remember _why doing any Rails development -- he was really key in Ruby land, but did his own (super-minimal) web thing called Camping. Anything I'm forgetting that he did with/for Rails?

Re: Ruby on Rails: The Documentary [video]

#43

Post by AlchemistCamp »

CPLX wrote: post #18
AlchemistCamp wrote: post #11

One of my biggest mistakes as a dev was not really learning Rails until 2015. I just didn’t know how much faster building web apps could be.

Yeah me too. I am still sad thinking about the number of hours I spend messing with python environments and versions because I was told it was the “quick and easy” option for solving this or that small problem.* Also worth mentioning Michael Hart’s intro course, which is a really shockingly well done way to ramp up from absolute zero, even for someone with very little code experience. * Which, in fairness, it mostly…

His book is what got me up to speed in 2015. I was visiting Chiang Mai and binged through the whole thing over a few days and then spent the next week cloning various personal projects I'd written with JS backends.

In under two weeks of opening Michael Hartl’s Rails Tutorial, I was already more productive with RoR than with the stack I'd been using professionally for 3+ years.

Re: Ruby on Rails: The Documentary [video]

#44

Post by jupp0r »

DoesntMatter22 wrote: post #34
jupp0r wrote: post #20

Earlier quoted context omitted.

I couldn't agree more. There is also a technology aspect to it. Rails is objectively veeeeeery slow. Concurrency support is nonexistent. This is not a good fit for all problems. It also to some degree prevents you from breaking out the parts that would benefit from a different language into their own services (Rails needs to call them, but it's really not good at IO).

Is there a comparable framework that does what Rails does but is somehow 10x faster? I wouldn't use Rails for everything but the fact that plenty of companies like Shopify are serving millions of requests per second with it shows that it's probably acceptably fast for mega scale apps.

Rails does everything. You can build a stateless API gateway with it. Is it great for that particular use case? No. Your question about frameworks with similar capabilities is pointless because my point was that there are use cases where the capabilities of Rails are not a good fit.

Re: Ruby on Rails: The Documentary [video]

#45

Post by jupp0r »

claudiug wrote: post #37
DoesntMatter22 wrote: post #34

Earlier quoted context omitted.

Is there a comparable framework that does what Rails does but is somehow 10x faster? I wouldn't use Rails for everything but the fact that plenty of companies like Shopify are serving millions of requests per second with it shows that it's probably acceptably fast for mega scale apps.

and gitlab, github :)

These two have lots of backend code that's not Ruby. Rails is great at what it does and it's not optimal for many other use cases.

Re: Ruby on Rails: The Documentary [video]

#46

Post by berkes »

larksimian wrote: post #30
berkes wrote: post #17

> if you open up any Rails application, it looks basically the same in structure whether it is the biggest Rails app there is or a new one. I used to love this, untill I started to hate it. I am convinced this is a major contributor to why so many Rails apps turn into an unmaintainable mess over years. Who measures onboarding in hours? It's fine if it takes a day or two to understand the domain. And the framework. An…

You're building CRUD apps. The conventions work and are extensible for teams of 1, 10, 100 and 1000s. You are not special and neither is your product. Companies making millions or billions of dollars have used this framework successfully. This level of bike-shedding is what makes conventions necessary especially when dealing with the typical hyper-pedantic software developer. Just the thought of having to debate wher…

> You're building CRUD apps.

No. "we" are not.

Re: Ruby on Rails: The Documentary [video]

#48

Post by jupp0r »

claudiug wrote: post #36
jupp0r wrote: post #20

Earlier quoted context omitted.

I couldn't agree more. There is also a technology aspect to it. Rails is objectively veeeeeery slow. Concurrency support is nonexistent. This is not a good fit for all problems. It also to some degree prevents you from breaking out the parts that would benefit from a different language into their own services (Rails needs to call them, but it's really not good at IO).

compare with what, in what load?

From my day job:

Stateless API gateway making HTTP calls to other services, which have response times in seconds for various reasons. Rails throughput ~20 requests per second. Golang rewrite throughput: 200k requests per second. Same hardware.

Re: Ruby on Rails: The Documentary [video]

#50

Post by Vayl »

lagniappe wrote: post #31
Alifatisk wrote: post #21

Sounds like from the comments that Rails is gaining a little bit more popularity again instead of being known as the boring robust framework

I probably won't use it again in any projects, but I liked the video because of nostalgia. Rails is a memory of a fun and scrappier me, a different time, appropriate in its own light for my path at the time.

Why wouldn't you use it again and what would you use instead?
Post reply on HN