heroku-buildpack-ruby

I'm sorry but the article seems pretty biased, and doesn't really give any argument for why what happened would be in any way justified. Author keeps adding their own interpretation to Github comments and events, which — just by looking at the contents — are needlessly negative. For example [1] where commit message states > We've been continuing to backport bugfixs to the 1.7.x series just for Heroku, but unless Heroku joins Ruby Together I don't have enough time available to make sure that continues to happen. but OP claims it > was interpreted as leveraging his control over Bundler as a pay-to-play scheme I'm sorry but not supporting outdated versions of an open-source tool for a business is perfectly reasonable. Similarly, [2] was again is described as "was interpreted at the time as indicating the feature would be withheld from Bundle

I'm really glad to see Heroku focusing on these types of optimizations. We've been using similar optimization strategies internally at my Rails consultancy for over a year [1], and it's amazing how much fun it is to ship features when you can add a small feature, check your test suite via CircleCI, and be live quickly thereafter. I remember the pain of deploying Huckberry [2] on Rails 3 a couple of years ago. Each deploy took ~6 minutes, and it'd drive us crazy. A whole lot of "Compiling!"-type [3] moments. (Back then, the Asset Pipeline compiled all of your assets twice: once with the real filename, once with the digest-filename: 'filename--f74c093df554be59d45d3c87920eba1f.js'. As you can imagine, this was quite slow.) This is one of the reasons I really love Heroku as a development platform. We're a 4-person shop—we can't spin off a r

I got started with React on a project last week. It's magic when it works, but initially it takes some thinking to figure out how all the components should fit together, and where the interactions should take place. It took me a while to figure out that my interactions on one component might trigger a method that should belong on a parent component a few levels up, and to have to pass that method down in the props for the child to call. React provides a syntax called JSX that looks a lot like regular HTML, but is transformed into native JS before it hits the React engine. It's brilliant, but requires node somewhere along the line to do the transformation. I got stung by this — building a Rails app, and Rails on Heroku ships with an ancient version of Node that causes the transformer to error out. Solution in the works (https://github.com

Do you use PostgreSQL with your app on Heroku? I seem to run into problem with it: https://github.com/heroku/heroku-buildpack-ruby/pull/93