4 ms·
Ruby on Windows is hell and it isn't Ruby's fault. I finally ditched a project I had written with Ruby on Windows and opted for Node which has fewer problems co
by ryanmarsh 12y ago
Ruby on Windows is hell and it isn't Ruby's fault. I finally ditched a project I had written with Ruby on Windows and opted for Node which has fewer problems compiling native modules. Ruby out of the box runs fine, trying to get thin or Nokogiri to build was worse than trying to get X.org configured to work with vendor video drivers on linux in the 90's
- FooBarWidget 12y agoHow did Node.js solve compilation problems on Windows? Doesn't Node.js suffer from the same problems? Do they provide a devkit that includes a compiler or something?
- ryanmarsh 12y agoi don't know how Node does it better but I have compiled several native extensions on windows just fine. I think the difference is people about Windows in the node community.
- adrianlmm 12y agoI feel your pain, I have the same problem, Ruby installs fine, but building dependencies is a gamble, I cannot install thin on Ruby 2.2 on Windows, so I'm stuck to Ruby 1.9.3, there are bug reports, but nobody cares, I don't thing this project will change that.
- giblaz 12y agoOof, why not try something like setting up a Vagrant machine running Linux instead of rewriting the entire project? Seems a lot simpler and way better for the project.
- ryanmarsh 12y agoIt's for a Microsoft shop. Their IT wouldn't let me have a Linux VM because they didn't want to be on the hook for supporting it. This is typical stuff for Fortune 500 IT consulting. I swear IT depts are making themselves irrelevant.