You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd appreciate a PR that makes the readme say what you want to say. (Or solves the problem you're having).
Here was the thinking behind this project:
reporting vulnerabilities in the interpreter itself (not many vulnerabilities anymore, Ruby is usually packed or deployed in buildpacks that take care of vulnerabilities)
encouraging people to migrate away from Ruby 1.8, so open source developers don't waste their lives slaving away to backport all new code to Ruby 1.8, just because some corporation doesn't want to spend any money and wants free support (those companies should've gone with Java or COBOL instead, and not manipulate the Ruby open source community to pay for their own business incompetence)
finding a way to have the reporting be part of the gem development process (which didn't work out well, because it was a "chicken and egg" problem)
I appreciate you all for caring about Ruby 3.0 support! It's people like you who helped made this project obsolete and I'm happy for it!
Activity
anatol commentedon Apr 15, 2021
Yeah, it does not work with ruby 3 :(
e2 commentedon Apr 15, 2021
I'd appreciate a PR that makes the readme say what you want to say. (Or solves the problem you're having).
Here was the thinking behind this project:
reporting vulnerabilities in the interpreter itself (not many vulnerabilities anymore, Ruby is usually packed or deployed in buildpacks that take care of vulnerabilities)
encouraging people to migrate away from Ruby 1.8, so open source developers don't waste their lives slaving away to backport all new code to Ruby 1.8, just because some corporation doesn't want to spend any money and wants free support (those companies should've gone with Java or COBOL instead, and not manipulate the Ruby open source community to pay for their own business incompetence)
finding a way to have the reporting be part of the gem development process (which didn't work out well, because it was a "chicken and egg" problem)
I appreciate you all for caring about Ruby 3.0 support! It's people like you who helped made this project obsolete and I'm happy for it!