Ruby

“have deployed Ruby with jemalloc in prod. There's a huge noticeable speed and memory efficiency.”

“I've work as a consultant for a few different tier 2 Ruby organizations and many startups myself”

“what I have done successfully here ... is to install a TracePoint which immediately throws, and then call the method.”

“I spent 5 years building a roguelike game in pure Ruby (no game engines)”

“I was part of a small team that built a $300M company on Ruby and MySQL that made every scaling mistake you can possibly make.”

“the one time I was able to get even basic debugger support into a production Ruby app, it made fixing certain classes of bug absolutely trivial”

“I don't tend to do it any more, because it's harder to debug. More often these days, I write things like this”

“using a library with the same API as the Ruby gem we had used.”

“I need to loop 16 times (`0xF.succ`) and then within that loop divide things by 256 (`0xFF.succ`)”

“packaged Ruby and Python CLIs that runs commands. The runtime was k8s.”

“components that have been in production for 3 years and haven't been substantially touched aside from Ruby upgrades”

“I have a ruby transient which provides a single UI for my favourite refactoring functions”

“Wow, I've been using Ruby for a decade and have never run into this.”

“I think json serialization is notoriously slow in ruby so I was hoping yjit would speed it up.”

“My team is usually view components in our application. Basicslly ruby erb renders the view component in a turbo frame.”

“I worked at a very large Ruby shop where errors in production were very expensive.”

“20 years of muscle memory writing bash / python / perl / awk / sql / ruby / JS / CSS selectors”

“use a little ruby script I wrote to push them from postgres to Dynamo with batch_write_item”

“I have a story of rewriting part of our production code as Rust extension, which turned out to be 3-4 times faster”

“had the official wasi cruby been available we could have stuck with Ruby for that project.”

“I've used each of those languages and also use Kotlin both on the JVM and in the browser.”

“Coming from ruby this kind of indirection was very hard me for quite some time.”

“I'd argue that the setup process for Ruby/Rails in 2006 was not all that much worse than other web stacks at the time”

“still stuck with Rails 4.2 and Ruby 2.5 (eehh)”

“I´ve worked with rake tasks when using ruby, and many times in java, with flyway and my own system.”

“We have functions written Ruby and JavaScript where we move the vendor Gems or node_modules into a shared Lambda Layer”

“we are a predominantly ruby shop actively using JRuby in production for a number of years”

“running strace on MRI Ruby with rubygems enables and lots of gems pulled in is a good way of seeing that in action”

“as a proffessional Ruby engineer of 6 years and an Elixir hobbiest of 3”

“It was a pastime that I knew nothing about until I started working at a Ruby shop about three years ago.”

“We switched Ruby -> Scala, and it took considerable training effort and some years before everyone was comfortable.”

“I have been using Ruby pretty much every day for work since 2005, and haven't done any rails since 2009.”

“At my company, we use Ruby for web backend and system administration.”

“I have a linux laptop I cannot develop on because I cannot install a recent version of ruby.”

“I've also written Perl and Ruby in production too.”

“My experience across ruby, python, and js codebases”

“I currently work on a rather large Rails app for a site that most of us here use.”

“back when I used to take advantage of existing libraries in Ruby/Rails”

“I've edited PHP or Python or Ruby files directly.”

“Our apps are mostly Ruby but we have been rewriting services in Crystal.”

“Groupon still used it even after they ditched Ruby for node.js (and lost a whole bunch of engineers that wanted to continue using Ruby).”

“we used a project called fog to write infrastructure code in Ruby.”

“was basically just servicing a shitty monolith built in Ruby.”

“going back to that from using Python, Ruby, and even PHP was a shock.”

“The stack, if it matters, was ruby on rails with jQuery.”

“my brief but romantic foray into Ruby a few years back gave me some perspective and nostalgia.”

“we were a heavy PHP/MySQL shop with a smattering of Ruby”

“so we are a fairly significant deployment of Sinatra/ruby.”

“having worked through moving a couple of large codebases to surviving strict taint checking in prod”

“My app is Ruby so deployment time is nearly nil, but we have a regression suite”

“When we migrated Parse from Ruby to Go, we started with two parallel efforts”

“keep the streamed data away from the Ruby garbage collector, since it gets a bit emotional if it has to clear out hundreds of MBs every second”

“we have switched to python for our FaaS but only because of lack of Ruby support from AWS lambda.”

“Ruby started focusing on optional typing but JS left that up to TypeScript which seemed like a better way”

“Even our Ruby projects didn't consume as much.”

“scraping a few sites using Ruby & Nokogiri, which isn't actually in production yet.”

“a traditional Ruby/PostgreSQL/REST api back-end.”

“Earlier in my career we moved to Ruby over PHP because Ruby was "cool" and PHP was not.”

“when I have to work on that system that is still in production on PHP Current-1 or Ruby-1”

“we use Ruby, Go, and elastic search”

“I've been looking for my next programming language of choice after Ruby for almost 2 years now.”

“The graphql-ruby is a gem. Also the community is super helpful.”

“Read: opposite of most enterprise Ruby apps”

“We run a little Ruby thing and we tried benchmarks on like 10 different places 2 years ago”

“one service requires a different version of a ruby gem than another for example”

“From my experience (moved 2 high load projects to Jruby) transition to JRuby from Ruby is not just changing Ruby version.”

“rails c takes 25 second to give a prompt vs 10 on with Ruby 2.2.2”

“FI was JRuby; as part of the naming switchover and product overhaul ... we switched it over to MRI in late 2011.”

“Learning ruby, rails, and django”

“As a Ruby developer I regret that didn't "pull a HHVM", would have made my life easier”

“If I'm writing something for my own purposes, I use Ruby.”

“Ruby, PHP, NodeJS, Apache...it's all there.”

“We could make do with just one (probably rake since we do mostly ruby coding)”

“Aaaah, I've been using Ruby for 5 years.”

“I introduced it at work recently, and everyone got the hang of it in about 20 minutes.”

“my production skill set includes php, c, c++, python, ruby, erlang, scheme, javascript, scala”

“Interfacing with Ruby via its C APIs, we are able to do some pretty crazy stuff”

“we use the axlsx gem for our Ruby app”

“We maintain legacy code that has been in production for more than 8 years and write new fully unit and integration-tested code in Groovy/Grails, Ruby/Rails, Java, and Angular.”

“I have been using the brightbox packages, but they are no longer updating 1.9 or 2.0”

“Being able to easily swap rubies in production gives a lot of flexibility.”

“8 or so years with Ruby, writing libraries with over 4 million downloads”

“even if I can still use simplecov with MRI thanks to conditionals”

“I've written a ruby gem to interface with it's API called Diplomat”

“the multi-tenancy and RBAC system remained in Ruby and on CouchDB”

“the results put that JRuby+Rails combination slightly slower than plain Ruby+Rails”

“Having learned perl, ruby and python (these are all incredibly similar), and then Clojure”

“You should, however, use system Ruby because using RVM / Rbenv in production vastly increases complexity”

“I had no Ruby experience, but in an hour I was able to build an app which read the data from an HTTP stream”

“I'm using MRI with rails 4.0.1 and I have not done any tweaking.”

“I've been using RethinkDB for a couple of weeks now and it's fantastic, the Ruby drivers work great.”

“had I had it when I tried to play with Ruby on Windows 7 three years ago”

“we have our design team maintain Ruby models of the h/ware modules”

“I wrote implementations of the Knuth-Plass line breaking algorithm in ruby [1] and clojure [2].”

“The biggest problem with RVM1 is that it is written in shell and even if there are people from Ruby community”

“I don't want to wait for os packaging to use a new ruby release”

“even if you're not going to use them in production (I don't).”

“when we upgraded from Ruby 1.9 to 2.0, we installed 2.0 via RVM, ran our staging environment on 2.0 while production ran on 1.9.”

“I know Ruby well, (bc I knew Perl very well)”

“we develop them with plain MRI Ruby.”

“we teach folks Ruby first, then the general web concepts (HTTP, HTML, etc)”

“I've dabbled in Fortran/PHP/Ruby/Haskell/Scala/Clojure but they become hazy after a while.”

“and I am a Ruby guy we are trying to figure out the best way forward”

“I've lately preferred working with Node.js, and Ruby before that.”

“even though at work we use Java and Ruby”

“I got tired of patching string.rb with "#encoding: UTF-8" whenever I was installing the gem someplace.”

“We wrote our script in Ruby because it's what we know and have the most expertise with”

“We only run one version of Ruby, but we install it to a location that a "stock" environment supports well.”

“Here is the bash alias I have been using for CLI JSON formatting”

“I played with this [1] when I first started programming in Ruby.”

“I work at a company in Chicago where we run our sites and apps on either Java, PHP, or Ruby.”

“The original version was written in 2007 in Rails 1.2.x and Ruby 1.8.6. Early this year we migrated the app to 1.9.3/3.2.x.”

“I used some ruby server-side scripting for my previous employer.”

“Our team was mainly Ruby and web front-end guys”

“I do a lot of work in CodeIgniter as well as Rails (w/ Ruby 1.9.2 in production)”

“Sure, I came with experience in ruby and python, so learning coffee script was just one happy afternoon”

“So, my own ORM is just a database superclass with em-connection-pool, configuration, openstruct”

“I can find a smattering of things in other languages in our code bases, including Ruby and Erlang”

“MRI took about 225MB, about half the memory.”

“Written in Ruby, based on FFmpeg + ImageMagick, handles both video, audio and photos”

“We run multiple Ruby processes per CPU so that when one process is waiting for the db or memcache, another can be doing useful work”

“we run multiple Ruby processes per CPU so that when one process is waiting for the db or memcache, another can be doing useful work”

“I have to use rvm in production because debian/ubuntu install ruby 1.8 and I need 1.9.2 for rails 3.”

“Sometimes you want to have multiple ruby versions (e.g. MRI for app and JRuby for memory heavy script)”

“when I deploy, I pick a Ruby version and stick with it unless there's a security issue”

“All that code I have running in production must be a FIGMENT OF MY IMAGINATION! SAVE YOURSELVES”

“We're using a combo of the PHP version and the Ruby version and it's been working great for us”

“I still do this when switching back from longer JS / Ruby development periods.”

“I worked on something similar a year ago but for the Ruby world.”

“Ruby 1.9.2: It was time to move up from 1.8.7.”

“moved my Ruby code to the Google App Engine.”

“we use Java for 90% of our platform codebase, with Ruby acting as a glue.”

“major languages we use like PhP, Python, Ruby, Java”

“ODBA is written in Ruby.”

“plus a mix of Java, Ruby, Python, and whatever else will get the job done.”

“I had stuff break because they decided to upgrade from Ruby 1.8.6 to 1.8.7.”

“automated QA tests through Cucumber / Capybara / Selenium in Ruby.”

“so writing them in Ruby is nice too.”

“Bindings (for ruby) at the time really sucked, and were not clear which ones to use.”

“Ruby for one set of management panels and Python for one of our other systems.”

“You've got two options for integrating C code in any Ruby application”

“It's not until I've got work within the Ruby field, I've had the need for it.”

“ruby is a fun language and rails is a fun magic framework suitable for pet projects”

“I've had more eye opening experiences programming in Clojure than in any language I learned before it. (C, C++, Java, Python, Ruby, common lisp)”

“194 of them are written in PHP (1 is Java, 2 are .NET, 1 Ruby, 2 Coldfusion)”

“Right now I'm running a Rails site in production with multithreading enabled”

“an app that currently runs in production on ruby 1.8.7 + rails 2.3.5”

“Most of the systems are built using combinations (pick two) of PHP, JSP, Ruby, Perl, MySQL and Oracle.”