Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The prevailing sentiment is that once you hit scaling issues with frameworks like Rails or Django you should have enough resources to simply throw money at the problem either in the form of more hardware, cloud computing, or better software engineers that can identify bottlenecks and optimize them.

Since most websites will never scale past the limitations of these frameworks, the productivity gains usually make this the right bet to make.



If Shopify or Github can handle scale with Rails, maybe it’s not a framework problem.


Github can be horribly slow sometimes (tested from different machines and through different ISPs) and difficult to tell if that is down to the framework used to render the pages or any other parts of the system.


A few years ago it started a transition to react. It has been less snappy ever since to me.


Agree, the new code viewer is horrid. Also breaks right-click navigation between files for no reason. Not once have I triggered the interactive editor mode on purpose, but happens all the time accidentally, trying to select / hightlight a line. So frustrating…


Hard disagree on this. I went with this sentiment and deeply regret it. With LLM assisted coding it's very fast and easy to write a Go or even a Rust server. They have less bugs and can actually do things like threads that you end up working around in python/ruby.


Giving an existing Rails codebase to an LLM and effectively asking it to rewrite it in Go is going to result in a shitstorm of epic proportions.

At least it’ll make for an interesting post mortem blog post.


I am not sure why people are comparing a web framework with writing your own code in another programming language.

How many CVEs have you had reported yet against your custom code for probably the middleware you wrote to get a request with params available to use them (the params) in an SQL query?

Of course if you are good at this and have a lot of experience than even using an LMM I am sure your code is more than fine. But on average I think it is safe to say that any middleware or library code to deal with HTTP requests and make the information available for business logic generated by an LLM has probably a lot of bugs (some subtle some very visible).

For me the power of Rails is that if you do CRUD web apps it is battle tested and has a long history of giving you what you need for fast building business logic for that CRUD app. Is it the knowledge that is put into designing a web framework that works for 90% of the operations you need to write your custom business logic.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: