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
{{ message }}
Instantly share code, notes, and snippets.
🏠
Working from home
Hiroshi SHIBATA
hsbt
🏠
Working from home
Full-time OSS developer. I'm a member of Ruby core team, RubyGems team and rbenv and ruby-build maintainer.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Our industry has a tendency to follow hypes without backing it with solid constructive claims. Over the past few years, trashing Ruby was one of these hypes, I also find that the so called "Senior Engineers" tend to promote hypes to appear more opinionated without really trying to explain the logical claims behind it, leaving the community beginners and new joiners really confused.
Goals of the project
Solidifying the claims behind the hype (Because I believe it stems from real problems, not just an empty hype) and eventually passing this to Ruby core team as an input from the community.
Explain these problems in a much simpler language to beginners and community new joiners.