I added this language to my watch list some time ago and forgot about it, until I got a notification about a new release (0.15) yesterday.
I’m someone who is familiar with system languages (C, Rust) and shell languages (Bash, Zsh, …). But don’t have much experience, at a proficient level, with any languages setting in between.
So I gave Koto’s language guide a read, and found it to be very well-written, and the premise of the language in general to be interesting. I only got annoyed near the end when I got to @base, because I’m an anti-OOP diehard 😉
I hope this one well start to enjoy some adoption.
Alright, then. I’ve read, like, a few Python tutorials. I thought OOP was more of a way to do things if it makes sense to. Like using a for loop vs a while loop, just on like, a language and code structure level. I didn’t realize most people didn’t like it? I hardly even know what it is lol. It’s just that I’ve not heard someone explicitly be against it. I didn’t even consider it a thing people would be pro- or anti- lmao
The context you are missing is that, for a lot of people, OOP was taught as the be-all and end-all of abstraction. I personally have seen some of my less experienced colleagues start to write code to solve a problem and immediately reach for OOP over and over again, even when this made things a lot messier (which ultimately I had to deal with…), because that is how they were told at one point was the “correct” way to do it, so I can completely sympathize with anti-OOP sentiment. On the other hand, I am not personally vehemently anti-OOP because I think that (as you have correctly observed) OOP is a perfectly fine pattern when it fits, and arguably the root problem that my colleagues had was not so much that they used OOP everywhere but that there was a tendency to not think through the consequences of their design choices.