3 ms·
I'm a rails guy and have run a consulting shop based on rails. But Im actually a bit surprised (and impressed) that you distribute a self-installed piece of sof
by sandGorgon 11y ago
I'm a rails guy and have run a consulting shop based on rails. But Im actually a bit surprised (and impressed) that you distribute a self-installed piece of software based on Rails (yes I have seen Omnibus and all the cool things you do. As I said very, very impressive!)
I have personally lost many a "enterprise" contract because of the Ruby thing. Not just that, but at the end of the day Java is very performant with least deployment effort .
Which is why we became a JRuby shop first (and packaged JAR for distribution) and eventually to Spring Boot and Scala.
I understand the value of Rails (my current startup is also built on that) - but I'm wondering if it makes sense for you guys to bite the bullet and jump to the JVM.
- tangue 11y agoWhy the downvotes ? Rails is a PITA to install, Docker might change that but I've spent too much time fighting rvm, rbenv, old gems
- kbutler 11y agoTry the gitlab installation, and speak to it specifically, rather than to general Rails experience. Gitlab install is fast and easy (though it didn't used to be). Gitlab has had a hugely successful rapid increase in usability/maintainability/installability.
- mjolk 11y agoI agree that there's a lot of worth in having a turn-key solution that's fast, especially if installing dependencies is required anyway (e.g. Ruby isn't necessarily on the user's system, neither is Java, so since you have to install a dependency anyway...). While it's not like the JVM will never be a source of annoyance for Gitlab admins, speed/user-perceived latency is more than just a feature when porting from an offering that's as polished and good as GitHub. This is especially true for people that would have to rationalize cutting over from GitHub to Gitlab in an enterprise environment.