Are there any potential disadvantages in using a Ruby framework other than Rails? -


I want to use lighter structure than rail (Sinatra / Ramez / camping) but I am worried that I can not be able to use many shared libraries as plugins. Is it a big concern or is it useful in most of these plugins, in various Ruby frameworks?

Is there any other possible pitfall in using any Ruby Framework other than Rail?

You can still use it in all the frameworks mentioned, so a ton of luggage is reusable Want to swap into a new ORM, no problem, want to highlight a fancy shmacy syntax, no problem. To use tracks especially to use gems, a huge push is moving away from the old plugin model

If one of the other settings fits better to your needs then its Use the. Keep in mind that when it comes to documentation and samples rail, it is more.

If I was learning Ruby and wanted to try a web framework then I would probably like to go with the rail because it is not better, but because it has better tooling and documentation.

/ html>

Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -