i made an update to specify ports like these. You can check.

To me, 8xxx is for proxy servers.

Nice. I have this too. I wanted something more visual and expansive.

Yeah, I have a function `whoseport` which is just your subcommand. I usually manually type kill or whatever I want with `$(whoseport 3000)`

The README already has a rather repugnant LLM-ish feel to it; lots of lists and verboseness, while saying very little.

Also, this is a perplexing choice (which also serves to illustrate the above point regarding verboseness):

    White background with red center: 1-9 processes (some development servers) 
    White background with orange center: 10+ processes (many development servers)

the ascii tree in "Project Structure" is a dead giveaway that AI is used in this project

Why would you need to do that?

It's just a tool I built for myself. There's no business case. It just helps me

can't a guy just create something anymore? :D They have to have a business model or a grand plan ?

> Such a big readme and no introduction to why I should be interested in this tool.

This.

Why in the hell would anyone want to kill random processes that open a port in the tange 2000-6000? And why is this need so pressing as to require a full blown monitor integrated in a task bar?

Without context, this sounds like a complete random silly project that makes no sense and serves no purpose at all.

What’s FSL?

Not sure I can add images here, but if you check the repo, I'll be adding one shortly.

a couple of prompts of claude code gave me this, works well enough, but while I agree that this is sometimes useful, it may indeed better served by a couple of aliases in the terminal ``` #!/bin/bash

# SwiftBar Port Monitor # Monitors processes on TCP ports 2000-6000

# Menu bar title echo " Ports" echo "---"

# Get processes listening on TCP ports 2000-6000 processes=$(lsof -iTCP:2000-6000 -sTCP:LISTEN -n -P 2>/dev/null | awk 'NR>1 {print $2 "|" $1 "|" $9}' | sort -t'|' -k3 -n)

if [ -z "$processes" ]; then echo "No processes found on ports 2000-6000" exit 0 fi

# Process each line while IFS='|' read -r pid name port_info; do if [ -n "$pid" ] && [ -n "$name" ] && [ -n "$port_info" ]; then # Extract port number from format like :3000 port=$(echo "$port_info" | sed 's/.://')

        # Menu item with port and process name
        echo "[$port] $name | color=blue"
        
        # Submenu items
        echo "--Kill (TERM) | shell=kill param1=$pid terminal=false refresh=true"
        echo "--Kill Force (KILL) | shell=kill param1=-9 param2=$pid terminal=false refresh=true"
        echo "--Process Info | shell=ps param1=-p param2=$pid param3=-o param4=pid,ppid,user,command terminal=true"
        echo "-----"
    fi

# Refresh option echo "---" echo "Refresh | refresh=true

Complaining about the number of dependencies is completely meaningless if you don't take into account what those dependencies do, and what the ecosystem looks like.

For example, `tray-icon` looks pretty useful for a lightweight app which basically is a tray icon: rewriting that library from scratch would be a massive waste of time.

On the other end of the spectrum, `log` and `serde` provide basic functionality which most languages will have in their standard library. Rust intentionally keeps a small standard library to avoid ossifying potentially bad ideas. The crates have tens of millions of users, rewriting that yourself would be stupidity.

It's very easy to criticize the length of their dependency list, but could you point to a specific one which you deem unnecessary? Which one do you consider to be a "leftPad", and what trivial code fragment would you replace it with?