<story><title>Learning Ruby: Things I Like, Things I Miss from Python</title><url>https://medium.com/workpath-thewaywework/learning-ruby-2-things-i-like-2-things-i-miss-from-python-6f60af8ed16c</url></story><parent_chain><item><author>mparramon</author><text>I would love to find an MVC framework with the extense library support of Rails but for Javascript. Being able to simply `gem &amp;#x27;devise&amp;#x27;` and have full authentication at your hands (including views, email templates, etc) is a godsend.&lt;p&gt;At many places where I&amp;#x27;ve worked at this paradigm is exactly what is needed, but people know and want to use JS. If we choose to go that way then, we need to write a lot of glue code and think about setting up architecture standards, folder and naming conventions, ORM support, authentication, job queues, etc; all of this comes by default with Rails and makes life so much easier.&lt;p&gt;Lately some options seem to be gaining steam:&lt;p&gt;* RedwoodJS [1]: by Tom Preston-Werner (founder of Github), comes with React and GraphQL baked in, pretty new project though&lt;p&gt;* Next.js [2]: brings a lot of nice conventions to the frontend, but still some things missing on the backend side&lt;p&gt;* SailsJS [3]: similar to Rails, but small community&lt;p&gt;* Strapi [4], hapi [5] et al: plenty of backend functionality, but frontend agnostic.&lt;p&gt;Has anybody had experience with any of these (or others) and can report back?&lt;p&gt;[1] - &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;redwoodjs.com&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;redwoodjs.com&amp;#x2F;&lt;/a&gt;&lt;p&gt;[2] - &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;nextjs.org&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;nextjs.org&amp;#x2F;&lt;/a&gt;&lt;p&gt;[3] - &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;sailsjs.com&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;sailsjs.com&amp;#x2F;&lt;/a&gt;&lt;p&gt;[4] - &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;strapi.io&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;strapi.io&amp;#x2F;&lt;/a&gt;&lt;p&gt;[5] - &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;hapi.dev&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;hapi.dev&amp;#x2F;&lt;/a&gt;</text></item></parent_chain><comment><author>nickjj</author><text>I think this is a very uphill battle because JS and most other languages are missing a key ingredient that Rails has had for 10+ years. It&amp;#x27;s having a long running large real world SAAS app that Rails is extracted from.&lt;p&gt;That means every feature of Rails is derived from a practical use case, and then it&amp;#x27;s well tested in that app before it&amp;#x27;s pushed out to the community. That&amp;#x27;s tested from an API and functionality point of view. By the time end users start to use it, the feature has likely been running in production for 6+ months. Maybe even serving billions of page views through it if you factor in Shopify and GitHub also running off Rails master.&lt;p&gt;It&amp;#x27;s all constantly in use, kept up to date and iterated on as a whole.&lt;p&gt;Creating a starter kit &amp;#x2F; boiler plate of libraries and opinions in another language &amp;#x2F; web framework is not the same. I think this is why even after 10+ years there&amp;#x27;s only a handful of popular Rails alternatives in other languages.</text></comment>
<story><title>Learning Ruby: Things I Like, Things I Miss from Python</title><url>https://medium.com/workpath-thewaywework/learning-ruby-2-things-i-like-2-things-i-miss-from-python-6f60af8ed16c</url></story><parent_chain><item><author>mparramon</author><text>I would love to find an MVC framework with the extense library support of Rails but for Javascript. Being able to simply `gem &amp;#x27;devise&amp;#x27;` and have full authentication at your hands (including views, email templates, etc) is a godsend.&lt;p&gt;At many places where I&amp;#x27;ve worked at this paradigm is exactly what is needed, but people know and want to use JS. If we choose to go that way then, we need to write a lot of glue code and think about setting up architecture standards, folder and naming conventions, ORM support, authentication, job queues, etc; all of this comes by default with Rails and makes life so much easier.&lt;p&gt;Lately some options seem to be gaining steam:&lt;p&gt;* RedwoodJS [1]: by Tom Preston-Werner (founder of Github), comes with React and GraphQL baked in, pretty new project though&lt;p&gt;* Next.js [2]: brings a lot of nice conventions to the frontend, but still some things missing on the backend side&lt;p&gt;* SailsJS [3]: similar to Rails, but small community&lt;p&gt;* Strapi [4], hapi [5] et al: plenty of backend functionality, but frontend agnostic.&lt;p&gt;Has anybody had experience with any of these (or others) and can report back?&lt;p&gt;[1] - &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;redwoodjs.com&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;redwoodjs.com&amp;#x2F;&lt;/a&gt;&lt;p&gt;[2] - &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;nextjs.org&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;nextjs.org&amp;#x2F;&lt;/a&gt;&lt;p&gt;[3] - &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;sailsjs.com&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;sailsjs.com&amp;#x2F;&lt;/a&gt;&lt;p&gt;[4] - &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;strapi.io&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;strapi.io&amp;#x2F;&lt;/a&gt;&lt;p&gt;[5] - &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;hapi.dev&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;hapi.dev&amp;#x2F;&lt;/a&gt;</text></item></parent_chain><comment><author>gls2ro</author><text>I don&amp;#x27;t have a recommendation, but here is a quick test I use when looking for a replacement for Rails:&lt;p&gt;How quick can I create a minimum simple SaaS like application that has the following functionalities:&lt;p&gt;- User management (Signup&amp;#x2F;Login&amp;#x2F;Reset password&amp;#x2F;Confirmation...)&lt;p&gt;- Simple payment processing (like have on single plan, one time fee, and after paying the user will see some other default page then not paying)&lt;p&gt;- Sending emails in HTML and plain text (for user management and after payment is processed)&lt;p&gt;- Use slugged&amp;#x2F;permalink like URLs&lt;p&gt;- Processing some task in async queue&lt;p&gt;And so far there are a lot of alternatives out there but for me Rails provides the easiest experience to have this up and running quickly as there are already battle-tested gems for almost all these functionalities.</text></comment>