4 ms·

So Engine Yard ends their support of JRuby in 2012. Then, just a few weeks ago, they end support for Rubinius. Now, they'll be ending support for RVM next week.

So Engine Yard ends their support of JRuby in 2012. Then, just a few weeks ago, they end support for Rubinius. Now, they'll be ending support for RVM next week... A shift in strategy? Financial troubles? Either way, it seems they need to update their "Engine Yard Loves Open Source" page: https://www.engineyard.com/community/open-source https://www.engineyard.com/community/open-source

nonchalance 13y ago
Strictly speaking, they wrote: > We are proud to employ and support contributors to such projects as Lithium, Travis CI, Rubinius and RailsInstaller. Check out the comprehensive list of open source projects we’re involved in below. That fact hasn't changed (at least, not until they start firing people)
- TylerE 13y ago
  It could easily mean they're no longer letting them work on their projects on the clock, though.
- kisitu 13y ago
  it could also mean that the project maintainers focus on their day jobs... the way Googlers hardly use their 20% time.
oconnore 13y ago
Oh how fickle you are. A company that supports an open source project out of pocket for two years now doesn't love open source because they have moved onto other things? Over time, technologies change, stabilize, and/or become obsolete, expecting them to support one project forever is silly and boring. How about: dear Engine Yard, thanks for 730 days of open source love, can't wait to see where you invest your time next.
- patcon 13y ago
  amen.
- jballanc 13y ago
  I don't disagree, which is why I'm wondering if this is a case of not having enough money to continue supporting these projects, or a case of seeing the momentum or the need for support in open source changing to something new. So far, though, I've only seen Engine Yard drop support for projects. If, tomorrow, they announced that they were starting to support a handful of Go or node.js projects, then I think we'd all have a much different view on this news.
- davidw 13y ago
  They should certainly be thanked, but it points to the larger problem that funding open source software in a stable, predictable way is hard. When it's basically a charity, then it's probably going to get the axe pretty early on when there are financial troubles.
deleted 13y ago
[deleted]
EamonLeonard 13y ago
I'm Eamon Leonard, I work at Engine Yard. We have a long history of supporting and investing in Open Source projects, especially those that can benefit our customers and the different OSS communities we participate in. Like all companies, we have budgets for all sorts of activities, and sponsoring open source software is no exception. Also, like every other company, we review on an annual basis, where we allocate our budgets. The decision to stop financially supporting any project is down to our assessment of what we've been able to help that project to achieve, and if there are opportunities to invest in other projects that are at a different stage in development, or if it relates to a specific customer need. As has been pointed out elsewhere in this thread, the Engine Yard platform now supports Ruby, PHP and Node JS, and will soon be supporting Java, as well as a number of different databases. Engine Yard has always contributed to the communities that its customers come from, and adding platform support for these languages and databases means that we need to consider open source projects in those communities as beneficiaries of our financial support.

nonchalance 13y ago

Strictly speaking, they wrote: > We are proud to employ and support contributors to such projects as Lithium, Travis CI, Rubinius and RailsInstaller. Check out the comprehensive list of open source projects we’re involved in below. That fact hasn't changed (at least, not until they start firing people)

TylerE 13y ago
It could easily mean they're no longer letting them work on their projects on the clock, though.
kisitu 13y ago
it could also mean that the project maintainers focus on their day jobs... the way Googlers hardly use their 20% time.

oconnore 13y ago

Oh how fickle you are. A company that supports an open source project out of pocket for two years now doesn't love open source because they have moved onto other things? Over time, technologies change, stabilize, and/or become obsolete, expecting them to support one project forever is silly and boring. How about: dear Engine Yard, thanks for 730 days of open source love, can't wait to see where you invest your time next.

patcon 13y ago
amen.
jballanc 13y ago
I don't disagree, which is why I'm wondering if this is a case of not having enough money to continue supporting these projects, or a case of seeing the momentum or the need for support in open source changing to something new. So far, though, I've only seen Engine Yard drop support for projects. If, tomorrow, they announced that they were starting to support a handful of Go or node.js projects, then I think we'd all have a much different view on this news.
davidw 13y ago
They should certainly be thanked, but it points to the larger problem that funding open source software in a stable, predictable way is hard. When it's basically a charity, then it's probably going to get the axe pretty early on when there are financial troubles.

deleted 13y ago

[deleted]

EamonLeonard 13y ago

I'm Eamon Leonard, I work at Engine Yard. We have a long history of supporting and investing in Open Source projects, especially those that can benefit our customers and the different OSS communities we participate in. Like all companies, we have budgets for all sorts of activities, and sponsoring open source software is no exception. Also, like every other company, we review on an annual basis, where we allocate our budgets. The decision to stop financially supporting any project is down to our assessment of what we've been able to help that project to achieve, and if there are opportunities to invest in other projects that are at a different stage in development, or if it relates to a specific customer need. As has been pointed out elsewhere in this thread, the Engine Yard platform now supports Ruby, PHP and Node JS, and will soon be supporting Java, as well as a number of different databases. Engine Yard has always contributed to the communities that its customers come from, and adding platform support for these languages and databases means that we need to consider open source projects in those communities as beneficiaries of our financial support.