4 ms·
I wouldn't. I'd go with something with a definitive support life and paid support if you need it. Either that or something simple enough you can run your own
by kryten 13y ago
I wouldn't.
I'd go with something with a definitive support life and paid support if you need it.
Either that or something simple enough you can run your own fork.
- steveklabnik 13y agoRails has a definitive support life: http://weblog.rubyonrails.org/2013/2/24/maintenance-policy-for-ruby-on-rails/ http://weblog.rubyonrails.org/2013/2/24/maintenance-policy-f... And this article is about paid support if you need it. ;)
- kryten 13y agoIt does but commercial offerings that we have are still supported from their implementation in 2001. Paid support by the vendor?
- steveklabnik 13y agoIf you require paid support by a vendor, you're not really using very much open source. Which is fine, but it's a very different world than mine.
- saryant 13y agoI disagree with that. Paid support is arguably the most popular monetization model for open source software. Redhat is a prime example of that.
- steveklabnik 13y agoRight, hence why I said 'much.' Red Hat is big, but it's one project of many.