Nice flex but what about every other person that is not a sysadmin?

They don't find themselves in the situation of sitting before a terminal emulator needing to kill a process by port in the first place?

Developers find themselves in tnis situation sometimes and are not sysadmins. I had this situation before, and I would need to google to know what lsof does and how to use it. And so do many others that are commenting positively here.

Experienced users (developer or otherwise) of unixy systems already know what lsof is. Inexperienced developers only need to learn it once, then they join the ranks of the aforementioned. Using these sort of systems for any length of time in the capacity of a developer or even just a hobby enthusiast will effectively make you a 'sysadmin', at least w.r.t. knowing the basic standard tools. Not least because lsof is useful for many sort of tasks (like figuring out which program is using a drive you're trying to umount), so chances are high that people in these situations already know about lsof.

And besides having to learn that lsof exists, you'd also have to learn that this even more obscure tool exists. And what happens if you prefer for the program to terminate itself gracefully, cleaning up whatever mess it might have made, instead of sending SIGKILL? Now you have to look up the PID or program name anyway, probably using lsof..

I'd say it's a toss-up whether the stackoverflow/chatgpt query is slower than remembering the name of the alternate tool.

Get TLDR, the examples it gives almost always save me from man or google. So handy!

Meanwhile other people are developers who only occassionally need to do this kind of thing. So they/we forget.