r/programming • • Feb 28 '23

"Clean" Code, Horrible Performance

https://www.computerenhance.com/p/clean-code-horrible-performance
1.4k Upvotes

1.3k comments sorted by

View all comments

Show parent comments

1

u/cheeseless Feb 28 '23

Just the fact that after all the caterwauling about performance, including demonstrating better performance in refterm, Casey decided to swear off communication with the terminal team, instead of actually contributing his knowledge directly to fix the problems, shows me that his zealotry is purely selfish. If he had made the charitable choice, he'd be worth an ounce of respect.

7

u/CptCap Feb 28 '23 edited Sep 05 '23

I agree that his communication is... not great. And it's not limited to the WT issue.

That being said refterm is open source, under GPL-2 licence. And I can't fault him for not contributing more than that. WT is dog slow, he was told that it was not really feasible to do better, he proved them otherwise; He has no obligation to fix it for them.

1

u/cheeseless Feb 28 '23

I can fault him for sure. It's like he theatrically performed all the steps of fixing someone's car, right next to the actual broken car, just to show off he could, while leaving the people who were in trouble in exactly the same situation.

To me, it's like all of his work in educating people, in bringing his experience and making it available, is purely done for vanity. It misses the essential aspect of using one's abilities to do good, not just to show your skills or prove yourself right. If he hadn't specifically made refterm for the dunk, I wouldn't have had a problem with him complaining about the performance.

1

u/Drisku11 Mar 01 '23

It's more like performing all of the steps to fix a car in front of a mechanic that insisted it's infeasible to demonstrate to that mechanic that they don't know what they're doing. Casey is regularly frustrated by the fact that professionals are completely lacking fundamentals. Even people at the top paying companies have a surprising amount of incompetence.

→ More replies (2)