i've been kinda slaggin them off forever on this. they pretty much make money off how inefficient RoR is plus a bunch of vendor lock-in. I switched to Java and

i've been kinda slaggin them off forever on this. they pretty much make money off how inefficient RoR is plus a bunch of vendor lock-in. I switched to Java and work for enterprise now so we have our own servers but for the next hobby project I doubt it'll be on Heroku. The thing that pisses me off most is that Heroku's policies on error/performance/updates are shaky, but their add-on makers (who are charging HIGH premiums) are far worse. I've had such a shoddy experience with WebSolr for example. Every few months all their stuff breaks, then when you follow their instructions to spin your instance back up you find that the client API or instance type you use is no longer supported and have to debate which parts of your codebase to upgrade just to get back to where you started. That's why I think the Heroku ecosystem is trash -- after 1-2 years of forced upgrades and code refactoring you get so tired of it. "Oh another email saying if I don't change ___ in 6 months my app will die." "Another slew of unexplained errors followed by Googling eventually leading to 1 tweet about how this add-ons service is temporarily fked". Seriously, just learn Java or some hipper JVM lang and spin up a Tomcat or Glassfish container somewhere, then connect to 3rd party services directly rather than through an extra "add-on" layer that supposedly provides convenience by forcing you to jump through one more hoop. Most of the add-on companies seem to have non-Heroku offerings that are much more flexible to integrate.