Same goes for Laravel which also includes laravel Boost for even more assistance for idiomatic code generation and the forthcoming Laravel AI SDK for agentic app development the Laravel way

Startups need to move fast to quickly validate their assumptions. Full stack batteries included frameworks like rails, Laravel and Django are much better suited for this with integrated background jobs, mailers, authentication and authorization, caching, queuing, notifications, active record style ORMs and broadcasting systems all baked in and designed to work together not to mention a common project structure for all apps and built in unit, feature and integration testing infrastructure. Add to that a huge ecosystem of packages designed to integrate with the framework and a large community.

I personally use Laravel for my side projects and but have been a long time asp.net user at work where working with multiple teams on large projects is more of a concern.

>Full stack batteries included frameworks ...

You have just described here .NET (ASP.NET)?

For web apps there is nothing that is the equivalent of rails or Laravel with batteries included for solo devs or small teams to rapidly build their ideas. I’m saying this as a .net enterprise dev that has worked with C# and ms web frameworks starting from web forms all the way to minimal apis that uses Laravel for personal projects

Agile web development with rails by Sam Ruby is a great intro to Ruby and rails.

The Ruby on rails channel on YouTube has a playlist explaining all the new components of rails 8 called rails 8 unpacked. Things like solid queue/cache and propshaft.

Great advice. I’d follow up with Sustainable Rails[1] once yiu get the basics.

The Polished Ruby book is also really good IMHO[2].

1. https://sustainable-rails.com/

2. https://www.packtpub.com/en-us/product/polished-ruby-program...

If you had to choose one to start would it be Sustainable Rails or Agile Web Development with Rails 8?

Hmm, good question. I think I'd probably start with Agile Web Development with Rails 8.

It's the book I learned originally Rails with more years ago than I care to remember (pre version 1!).

Sustainable Rails is really more about how build bigger projects over the longer term.

i.e. good practice for reducing the churn on model files when you have a larger teams or how to do things with a miniumum of external dependencies.

It's great stuff but you can probably pick that up later if you want to.

BTW I just saw this in browser tutorial from learning Rails[1]. I've not run fully through it but it looks really promising to me.

1. https://news.ycombinator.com/item?id=44574654

All you need is to have php and composer installed on your system to get started. Any additional services like MySQL, Redis or a mail server you can run in docker but with the latest Laravel releases you can use its default SQLite setup as database and queue.

Alternatively you can run everything in docker using Laravel sail and not worry about installing anything on your system.

All the other tooling and packages like breeze are just conveniences that give you additional capabilities

David sacks’ glueai app uses ragie.ai under the hood

try to take a short nap after you get home before working on your project and then try to work just one hour on the project afterwards consistently monday through friday. try to increase to two hours per day. focus on just one task per day. Also try to do four hours each day on sat and sunday. finish one feature completely before moving onto the next feature to get the feedback of having accomplished something. reduce the scope of each feature so that you have a chance of completing a feature about every two weeks. try to get user feedback as soon as you can for the completed features for further motivation. setup a kanban board for your project and move the highest priority feature through the lanes before starting the next highest priority feature. Good luck

Try out the pythonmldaily YouTube channel

If you just want a simple informational landing page with maybe click through to other static pages to measure seo analytics then simple html/css pages will suffice. If you also want to capture email addresses then you need some sort of back end which you can build with something like rails or Laravel. But in that case I would go with an e-mail marketing platform like convertkit which has built in analytics. However it looks like you want the ability to build quick interactive prototype of your startup idea to validate the idea, in which case I would go with rails or Laravel which allow for quick prototyping and iterating on your idea. You could use htmx with both those frameworks to avoid a full blown JavaScript front end, but rails offers Hotwire and Laravel offers livewire which are packages that are integrated with the respective frameworks