<story><title>Sick of Ruby, dynamic typing, side effects, and object-orientation (2014)</title><url>https://blog.abevoelker.com/sick-of-ruby-dynamic-typing-side-effects-object-oriented-programming/</url></story><parent_chain><item><author>lucaspiller</author><text>I switched from Ruby (after ~8 years) to JavaScript at the beginning of this year, and Ruby is a dream in comparison:&lt;p&gt;- Thanks to the proliferation of Rails and similar frameworks, most Ruby apps at least have something that resembles an MVC structure. With JavaScript, once you move past the basic TodoMVC examples you are pretty much on your own. It gives you enough rope to hang yourself, all you colleagues, and everyone in the building next door.&lt;p&gt;- The expect vs should change in RSpec is nothing compared to how fast things are changing in JavaScript. I think there are now 7 different ways of just defining a module.&lt;p&gt;- The stdlib of Ruby is pretty sensible. JavaScript has many inconsistencies (take Array.slice vs Array.splice - one modifies the original array, and the other does not), and you usually need to rely on third party libraries, or write the code yourself, to do pretty basic operations.&lt;p&gt;- The JavaScript community seems to have the opposite of NIH syndrome, so that even basic functionality is offloaded to a third-party modules (see leftpad). The project I&amp;#x27;m working on has over 1000 modules in it&amp;#x27;s dependency tree.</text></item></parent_chain><comment><author>jbreckmckye</author><text>&amp;gt; With JavaScript, once you move past the basic TodoMVC examples you are pretty much on your own.&lt;p&gt;This is a big problem that&amp;#x27;s addressed quite rarely. There&amp;#x27;s very few open JS codebases that cover the sorts of concerns most web developers face. There are open codebases for build tools, codebases for graphics editors and web frameworks, but few relevant to writing a typical frontend app and frankly few that are well written.&lt;p&gt;As a JavaScript developer myself I often wonder if there&amp;#x27;d be demand for a &amp;#x27;boring webapp&amp;#x27; open codebase, something that could showcase perhaps two or three different ways of writing garden-variety JS applications.</text></comment>
<story><title>Sick of Ruby, dynamic typing, side effects, and object-orientation (2014)</title><url>https://blog.abevoelker.com/sick-of-ruby-dynamic-typing-side-effects-object-oriented-programming/</url></story><parent_chain><item><author>lucaspiller</author><text>I switched from Ruby (after ~8 years) to JavaScript at the beginning of this year, and Ruby is a dream in comparison:&lt;p&gt;- Thanks to the proliferation of Rails and similar frameworks, most Ruby apps at least have something that resembles an MVC structure. With JavaScript, once you move past the basic TodoMVC examples you are pretty much on your own. It gives you enough rope to hang yourself, all you colleagues, and everyone in the building next door.&lt;p&gt;- The expect vs should change in RSpec is nothing compared to how fast things are changing in JavaScript. I think there are now 7 different ways of just defining a module.&lt;p&gt;- The stdlib of Ruby is pretty sensible. JavaScript has many inconsistencies (take Array.slice vs Array.splice - one modifies the original array, and the other does not), and you usually need to rely on third party libraries, or write the code yourself, to do pretty basic operations.&lt;p&gt;- The JavaScript community seems to have the opposite of NIH syndrome, so that even basic functionality is offloaded to a third-party modules (see leftpad). The project I&amp;#x27;m working on has over 1000 modules in it&amp;#x27;s dependency tree.</text></item></parent_chain><comment><author>gkya</author><text>Rails is crazy.  If you know it well maybe it&amp;#x27;s useful but it&amp;#x27;s very unapproachable.  A new project, empty, involves tens of directories and files and at least two languages (coffeescript).  That&amp;#x27;s been off-putting for me.  But Ruby the language is quite pleasant IMO.  I guess people confound their experiences of Rails and some other Ruby tooling with the language itself.</text></comment>