DEV Community

Discussion on: Fast way to build CRUD app?

Collapse
 
ben profile image
Ben Halpern

I haven't yet found anything better than Ruby on Rails for zero-to-sixty on a basic CRUD app. The generators can get the job done pretty quickly, and perhaps along with an admin panel like Administrate

But I don't think anything can be that much better than the others. I'd definitely like to hear about other options. I definitely see non-devs using tech like Airtable to speed run the process, though nothing ends up being just the right choice. It's what you didn't know you needed on day one that always causes the problems.

Collapse
 
6temes profile image
Daniel

Completelly agree that RoR allows to create CRUD apps really fast.

But Ruby on Rails is not easy. There are a lot of implicit conventions that the developer needs to know, several gems that she need to understand well, and a lot of magic that is extremelly useful but that may be confusing for a beginner.

I think that this is one of the reason why some people is disapointed with Rails. They are told that it is easy and fast, but nobody tells them that Rails is easy and fast after you have been using it for more than one year.

Collapse
 
ben profile image
Ben Halpern

No disagreements here.

Collapse
 
spidergears profile image
Deepak Singh

Agreed. Ruby has lot of hidden tricks and magic.
I have been a RoR dev for more than four years now, then one day I decided to take a look at Phoenix. I am amazed how everything is more explicit, more verbose.

Thread Thread
 
6temes profile image
Daniel

In any case, I never said that this implicitness (magic) is bad. Once I built several sites, I realized that there are many things on the stack that are always the same, so there's no need to configure every single detail of every app I build.

In Rails, many things just work out of the box. But it is important to learn not to fight against the framework. And it takes some time to learn that.

Thread Thread
 
spidergears profile image
Deepak Singh

Magic is not bad at all. Love RoR everyday.
It is also super easy to alter these magical pieces to play nice with any of the customisation. And yes, it take time to learn that, figure out these hooks.

Problem I think is discovery, where is this magic happening?

A little example, both Rails and Phoenix have a pluggable architecture but how do you know what stuff is plugged in.

RoR rake middleware is the magic phrase

rake middleware

use Airbrake::UserInformer
use Rack::Sendfile
use ActionDispatch::Static
use Rack::Lock
use #<ActiveSupport::Cache::Strategy::LocalCache::Middleware:0x007f9aababbc40>
...
...
use ActionDispatch::ParamsParser
use Remotipart::Middleware
use Rack::Head
use Rack::ConditionalGet
use Rack::ETag
use Warden::Manager

Phoenix, this is explicitly mentioned in the generated routes file.

pipeline :browser do
    plug :accepts, ["html"]
    plug :fetch_session
    ...
    ...
    plug :protect_from_forgery
    plug :put_secure_browser_headers
  end

  pipeline :api do
    plug :accepts, ["json"]
  end

  scope "/", HelloPhoenix do
    pipe_through :browser # Use the default browser stack

    get "/", PageController, :index
    get "/hello", HelloController, :index
    get "/hello/:messenger", HelloController, :show
  end

  # Other scopes may use custom stacks.
  # scope "/api", HelloPhoenix do
  #   pipe_through :api
  # end

Aside: Too much verbosity is an overkill too.