What's interesting to me is how, as I've started to really look into things like J or K, I've begun to appreciate the whole "cryptic text" side of programming while rebelling against the more verbose OOP/whitespace delimited code. Sure, initially it might look like some C code started printing out random data beyond the end of an array, but as I've started to study it, it really has started to make more sense to me to use this highly condensed form of programming. I've even begun to toy with the idea that the original creator of K uses wherein he hates scrolling, so all his code is organized into a few small files so that he doesn't have to scroll any of them. At least one of the benefits of this kind of coding are that you can easily see and reference everything that is used, since your eyes only have to move a small distance and you don't have to scroll 500 lines to see the definition of whatever you're trying to look up. I also feel like it promotes a simplicity, due to it promoting dense, terse code, you really need to make sure what you're writing is the simplest possible to fit into a small amount of text.

Anyway, I'm not saying you have to personally like something such as J. If you're productive in C/C++ and Python, by all means create things in those languages. But please don't call J an absolute abomination, as I believe it merely calls coders with a different mindset/aesthetic desire to code in it.