Reading articles like this has the surprising effect of making me wish for something analogous to the Java Community Process. Improvements to the language can b

Reading articles like this has the surprising effect of making me wish for something analogous to the Java Community Process. Improvements to the language can be proposed by organizations or individuals. Here, Chris (or -- more likely -- Shopify) could introduce object shaping as a proposal. This would trigger a set of steps [1] that would allow for the proposal to be more carefully studied, an initial implantation put into place, and eventually have it become part of core. As things currently stand in Ruby-land, however, Matz and DHH rule the roost. This has given rise to split implementations. For example: Sorbet (created by Shopify) and RBS (created by Square) are means to add static typing to Ruby. I am sure each has strengths and weaknesses. The larger point is, however, that there shouldn't be two implementations of something so funamental, even if they are mutually compatible. When generics were introduced to Java you didn't have one flavor from IBM and one from, say, JetBrains. There was just generics. tl;dr: Ruby (and Rails) would benefit from having a structured, democratic process to introduce changes. [1] https://jcp.org/en/jsr/stage https://jcp.org/en/jsr/stage