I like Ruby for my own projects because of how descriptive it is for when i come back to code later and need to understand what i did, and it requires possibly

I like Ruby for my own projects because of how descriptive it is for when i come back to code later and need to understand what i did, and it requires possibly the fewest keystrokes of any modern language, which is a plus for my RSI hands. But, for large projects I've learned I don't care for it. Not unless the project, and team working on the project, follow guidelines and conventions. Otherwise it will devolve into a mess, guaranteed. And too many rubyist are hesitant to simply use rubocop to enforce this at a PR or something similar. It's like most of them forgot about `rake` and just having a formatting or linting task. But i digress. I like all these changes, but it's just me (i wouldn't use them on an actual open source project yet). So Matz is right to know the `end` may end ruby (seriously, my students just _hate_ it) but i'm more curious to see if the community will agree and follow along. Also, endwise is a great extension to abstract away most those `end`s being typed anyway.