4 ms·
I think the "understands the language and ecosystem better" is critical, but my expectation is that I need to learn a subset of key gems better more than anythi
by josephmosby 14y ago
I think the "understands the language and ecosystem better" is critical, but my expectation is that I need to learn a subset of key gems better more than anything else.
Every hardcore Ruby-ist that I've known has owned a Mac as their primary dev machine. I'm sure that there are plenty of Linux devs out there, but my experience has been that it's heavily Mac-driven. However, by sticking with Linux as my development platform, I'm probably going to learn the guts of gems because I have to get under the hood to make them work on Linux.
Maybe I'll continue to have gem conflicts, but that's okay - I'll know how to hack around them.
- skrebbel 14y agowhy so? Mac is a lot like Linux. I've been having little problems with the vast majority of mature gems even on Windows (especially with ruby devkit around, which automagically temporarily puts a GNU environment in my path to build gems that contain c/c++ code, none of which you'll need to worry about on Linux)
- jhawthorn 14y agoYou will not run into this problem. Linux is almost always used for production servers and is popular for development as well.
- anveo 14y agoWhile many Rubyists may use a Mac I'm confident the large majority deploy those applications on Linux. Cross OS compatibility issues are virtually non-existent, especially on non-development focused gems.
- deleted 14y ago[deleted]
- jayferd 14y agoI've been developing on Linux since I started. If someone makes a gem that you can't install because you're using Linux, you probably don't need that gem :).
- kingnothing 14y agoYou shouldn't hit any issues with gems and linux -- most production Ruby systems use linux.