Just providing readers with a different take on things: I've been coding in K professionally, after coming from a C-heavy (not functional-programming!) backgro

Just providing readers with a different take on things: I've been coding in K professionally, after coming from a C-heavy (not functional-programming!) background, for about three months. It only took a few hours with the language to have the apparent line-noise make sense, and after a few weeks I could decipher the function of most snippets I see. There are great reasons why a dev team might not want to switch over to K for its operations (or switch languages at all, really), but seeing K in action, I have to respectfully disagree that readability and maintainability are those reasons.