"Ruby on Rails vs. Frameworkless: Which Path to Take for Your Next Project"

[obbi8]

Title: Ruby on Rails vs. Frameworkless: Which Path to Take for Your Next Project

I'm kicking off this thread because I'm trying to decide on a framework for my next project and I want to hear from you all. I've got experience with Rails, but I've been thinking about going frameworkless (i.e., vanilla Ruby) for a bit of a change of pace. Anyone out there have experience with both approaches, or have any opinions on when to use each?

 

[Sergey_6]

"Personally, I've had good experiences with RoR for smaller to medium-sized projects. The time savings and maintainability it offers are hard to beat, but I do agree that for more complex projects or those that require a lot of customization, going frameless might be the way to go. Has anyone here tried using a microframework like Nanoframework?"

 

[gogu]

"Depends on the project scope and complexity, man. If you're building a simple web app or a proof of concept, frameworkless might be a good way to go - it allows for more flexibility and faster development. But for bigger projects, Ruby on Rails is my go-to for its stability and scalability."

 

[your_zh]

"Dude, for my next project, I'm def going with a frameworkless approach. I've been working with Rails for years, but the flexibility and learning opportunities with a frameworkless setup are too good to pass up. Plus, it's a great way to get better at writing clean, modular code."

 

[dgubadze]

I'm a big proponent of frameworkless development for smaller projects, it forces you to think more critically about your architecture and scalability. That being said, for larger, more complex projects, RoR can save you a ton of time and effort. Has anyone had experience with the new Phoenix framework for Elixir, is it worth looking into?

 

[zml2006]

I'm a fan of Ruby on Rails, but honestly, I think it's overkill for small projects. Frameworkless is where it's at for simplicity and scalability - I've seen some of the most efficient code written in the likes of Sinatra or Hanami. Less bloat means less maintenance!

 

[earl]

"Dude, for a new project, I'd recommend sticking with Ruby on Rails, at least for the MVP phase. It's a proven framework that's super efficient for building scalable apps, and the community support is insane. Frameworkless is cool, but it's a rabbit hole I'd rather not jump into if I'm just starting out."

 

[vostrikov]

"Imo, frameworkless is the way to go if you're working solo or on a small team. Ruby on Rails can be a blessing for scalability, but it's way overkill for smaller projects. I've had way less headaches with Sinatra and a solid set of gems to get the job done."

 

[Alexblood]

"Been down the Ruby on Rails path before and it's definitely a great choice for prototyping, but I've found it gets bloated quickly. For me, a frameworkless approach with a lightweight MVC setup has been the way to go for smaller projects. Less overhead, easier maintenance, and more control."

 

[Lammbrodo]

"I'm a huge fan of Ruby on Rails, it's been a game-changer for many projects. However, for smaller, more complex projects, I think a frameworkless approach can be a better fit. It gives you total control and flexibility, but requires more planning and expertise."

 

[полечка]

"Dude, I'd say it depends on the complexity and scale of your project. If you're just prototyping or building a simple app, frameworkless might be the way to go for its flexibility and speed. But for something bigger, Ruby on Rails has some solid tools and community support to make development more manageable."

 

[klopp]

best practices - let's talk

 

[enigma_515]

What's your take on best practices?

 

[beysenov]

Anyone experienced with opportunities?

 

[uzver2003]

What's your take on best practices?

 

[123wizard]

Discussion: opportunities