Every 5 years the concept of the application port will be re-invented at the higher level of the stack.
Looked like a good idea until you mentioned JavaScript. Bummer.
If you're so against a js client, you could certainly whip one up in another language...
Whoosh...
EDIT: A OpenVPN/SOCKS/WebSocket/HTTP/TCP/IP is a terrible idea and I'm assuming it was meant as a joke. Thus, the addition of Javascript to the comment makes no difference at all. Thus, my comment was intended as a joke since it's irrelevant (again) in which language a bad proposal is implemented.
There, you took all the fun out of it. Happy? ;-)
If it's any consolation, I laughed harder at this than I did at the original joke.
I guess I'm naive and think that comments on HN should try to be constructive, so your sarcasm did miss me.
If the proposed idea is a bad one, don't you think it would have been much more helpful if you added your opinion on that to the convo rather than snark?
My apologies for ruining your fun.
The original "idea" itself was itself sarcasm. Your parent was simply underscoring it. You just failed to identify the original sarcasm, and ended up confused and a bit too serious about it all. It's just some obscure humor, no need to get worked up over it :)
I propose OpenVPN/SOCKS/WebSocket/HTTP/TCP/IP as the new de-facto standard connection protocol. Maybe we can FTP through that VPN connection some time, please wait while I cook up a JavaScript FTP/OpenVPN/SOCKS/WebSocket/HTTP/TCP/IP client.