I disagree.
inetd is a port monitor that launches particular daemons on particular ports, security options checked, on a need be basis. The difference between, say, telnetd and in.telnetd is simple. One runs always, the other opens a process each time it's requested on the configured port. Which does the package your installing setup easier for? You don't want to spend time. What does the software author say is preferred?
There are many subtle differences. Can telnetd handle multple logins? No. Can in.telnetd launch multiple instances, maybe use new ports? If it can't maybe some in.server can. In general it's more sane to use inetd, it does security and limiting and uses less memory and it's easier to know when servers are being used remotely when.
On the other hand if it's a daemon that gets highly frequently queries (maybe mysqld) then waiting for inetd to open and close it might be slow.
The idea "every one uses portmap and 100 servers and has no idea which service always running will be which port" and no one has in.anything is just not true. Many like simplicity.