How did the Ruby community go from Great to Garbage?

Only 10 years ago, the Ruby community was great! It was a highly innovative and outside-the-box thinking community that explored ideas independently from the rest of the Software Engineering industry, often innovating novel open-source projects not possible in any languages other than Ruby. Also generally, I was treated with dignity and respect in the Ruby community, and it was the common default that Rubyists would support me in whatever new ideas I explored in Ruby open-source projects. 

So, how did the Ruby community go from great to garbage!?!!

- Many devs entered the Ruby community unethically just for the money or "cool" association factor, cheating clients by not offering them the best Software Engineering work possible in Ruby/Rails.

- Many Rubyists were pushovers that were easy to influence and manipulate by inferior non-Rubyists and fake or unethical Rubyists due to lazy complacency and lacking a backbone to say no when needed. Such Rubyists were often too afraid to address the big elephant in the room.

- The Ruby community has become mean by practicing covert discrimination and open discrimination against certain members of the community that are not deemed part of the "cool crowd" even if they had 100% merit, ethical conduct, great education, smart open-source projects, excellent accomplishments, and valid novel Ruby ideas. This kind of behavior started mostly at companies like Shopify when Shopify started becoming big and evil, and then eventually spread through the rest of the Ruby community. DHH and some members of 37Signals seem to more recently practice that sort of mean behavior and covert discrimination as well.

- Many Rubyists had a selfish attitude of "if this discrimination/hate/meanness doesn't affect me directly, then I don't really care about it even if it affects others! I just care about what I'm getting out of the community!", without caring to realize that some of what they are getting out of the community is coming from pushing some community members down, meaning stolen goods. I've even encountered Ruby/Rails subreddit mods and public speakers who didn't care whatsoever about the discrimination happening in the community by large Ruby shops like Shopify, just because they had friendships with some of the people at Shopify. They didn't even bother to investigate the discrimination or at least show sympathy and ask more about it. I mean if my friends practiced discrimination, they wouldn't be my friends anymore, and I would definitely investigate if they did practice discrimination. This just goes to show that some Ruby/Rails subreddit mods and public speakers are unethical awful people who are part of the problem, not the solution.

- Some leaders of the Ruby/Rails community like DHH simp to non-Rubyists like JavaScript devs while desperately seeking their approval, which doesn't make sense given that their technologies are inferior to Ruby. Instead, such bad leaders should be leading non-Rubyists towards better ways of Software Development using Ruby when Ruby offers the best possible potential solutions in certain areas of Software Development. It doesn't hurt to learn other technologies too, but when it's obvious a technology like JavaScript is inferior to Ruby, using JavaScript would not be using the best potential tool for the job, so it would be unintelligent to desperately seek the approval of its users instead of leading them towards better Software Development approaches in Ruby.

- Some Rubyists have a "my way or the highway" attitude and insist on using one "golden hammer" for all problems. Like, DHH believing everything must be handled by Hotwire and a Monolith instead of having the correct Software Engineering attitude of having many tools in the tool belt to address a spectrum of problems and using the right tool for the job depending on each client's situation and requirements. Devs who believe Hotwire solves everything are just as bad as devs who believe React solves everything. They're not any different or better as they close the door on any potential other innovations that could rival both solutions.

- Ruby/Rails subreddit mods tolerate hate, mistreatment, and unkind behavior towards well-accomplished Rubyists in the Ruby community who have much better ethics and much better accomplishments in the Ruby community than the unethical hateful devs who mistreat them. They also allow in devs who don't pass the minimum bar of respectful conduct for being hired at any respectable business, which makes no sense. Lastly, the subreddit mods practice discrimination against certain members of the Ruby community, treating them as if it doesn't matter at all whether they receive mistreatment, discrimination, or hate. That paints the mods as hypocrites and discredits all their words about stopping hate. If you discriminate in who you stop hate for, you are practicing discrimination and hate, and everything you say about stopping hate is a lie and doesn't have any weight anymore. 

- Some Rubyists betrayed the Ruby community by giving the false privilege of being considered Rubyists to unethical unqualified unintelligent devs who hate Ruby in certain parts of Software Development and don't pass the minimum bar of respectable conduct for hiring even though they don't really get Ruby and actually hate it in certain areas of Software Development while preferring extremely contradictory and dumb inferior technologies to it like React.js. They also betrayed customers who receive 1/2 or 1/4 of the business value they pay for due to Rubyists using React.js and other inferior technologies instead of using Ruby.

- Many Ruby/Rails conferences discriminate against certain topics in Ruby. For example, they reject all talks relating to Frontend Ruby no matter how qualified/upstanding the speaker is, how well-rehearsed the talk is when already given in local Ruby meetups, and how useful the technology is when already in use at a business. Also, some of their organizers are not upfront and humble about the fact they are less qualified in Ruby Software Engineering skills than the speakers they are judging, meaning they either shouldn't be in their position and allow someone better to judge talks or they should accept the expertise of more competent Ruby Software Engineers and accept their interesting novel talks without discrimination. What's most embarrassing is I have encountered some judges at Ruby conferences who were "hurt" by the fact that a Frontend Ruby technology is unseating React.js or some other JS/non-Ruby technology they are strongly attached to, demonstrating they are fake Rubyists and fake Software Engineers who don't put customers first along with the benefits they might receive from superior Ruby technologies, aren't committed to Ruby, and don't really get Ruby's benefits, yet are just shams/frauds that shouldn't be presiding over any conference. 

- Many Rubyists have lack of humility and honesty, especially regarding admitting lack of skills, lack of experience, and/or lack of qualifications in Ruby as to address that effectively. They bluff their way through the Software Engineering industry by mindlessly repeating "intelligent-sounding words" they heard from big names in the industry without truly understanding them, which might trick the untrained eye and gullible Rubyists, but is seen for what it is from a mile away by all competent Rubyists. Some Ruby/Rails subreddit members who have no degrees, no work accomplishments, no open-source projects, no conference presentations, and no ethical conduct act as if they're the gods of Ruby/Rails, which is very laughable.

- Many Rubyists don't respect the excellent accomplishments of more accomplished and/or more senior Software Engineers (sometimes out of unconscious or conscious discrimination). When a Rubyist doesn't respect excellence, that immediately tells everyone that they are NOT excellent. After all, excellent people always appreciate excellence in others, including excellent accomplishments.

- Many Rubyists lack skill in general Software Engineering principles and best practices, often doing Software Development in a Monkey-See-Monkey-Do fashion by following big names in the industry without thinking for themselves. And, they lack Software Engineering curiosity and interest in exploring Ruby in unexplored areas or learning more about outside-the-box novel Ruby open-source projects. More often than not, this is a side effect to not having any university degrees in computing, and instead having very shallow knowledge from reading a few books or going through an insufficient short bootcamp. 

- Many Rubyists do not match their words with actions and often make lame excuses instead of taking responsibility. Some will make a million excuses for not wanting to check out a new novel Ruby open-source project even if it only takes 10 minutes to an hour to check it out and the project won an award and is in successful use in production at a business. Sometimes, this happens out of unconscious or conscious discrimination. Either way, it's bad. It's known that anyone who makes excuses is incompetent by definition. No great accomplishments ever happened through excuses.

- Many Rubyists are unsupportive towards open-source project authors that implement highly novel outside-the-box disruptive ideas either due to closed-mindedness or due to being too attached to older less effective technologies, including ones in other languages, like React.js, instead of correctly being attached to serving customers in the best way possible above all else.