4 ms·

I'm not quite certain how common it really is. But, in any case, ports are expected to occasionally collide and therefore easy to configure. If port collisions

I'm not quite certain how common it really is. But, in any case, ports are expected to occasionally collide and therefore easy to configure. If port collisions were such a hassle, we wouldn't see anything like a "common" port (i. e. one that unrelated tools choose per default). Good developers can have a pipe in every port, I guess... (valid for development work only, especially those cases where you run some server and it opens the browser for you, port helpfully provided. There is value in ssh on 22 and http on 80, obvsly)

capableweb 5y ago
Judging by that thread in the Apple forums, people are for some reason unable to change the default port their development environment uses, so they blame Apple for using a port they have been using for a long time. Not sure why they are unable to change them, but the typical Apple user isn't directly famous for their willingness to configure their own software (either changing the ports of their development environment, or configure their OS to stop using that port), so I guess it's fairly common to end up with scenarios like this.
- Lhiw 5y ago
  Using whole round numbers like 5000 for public release software is pretty braindead though.