3 ms·
In the case of Flask: It would be incredibly inconvenient to restart your development server and have it show up on a random port every single time. The only t
by jorams 5y ago
In the case of Flask: It would be incredibly inconvenient to restart your development server and have it show up on a random port every single time.
The only time fixed port numbers are inconvenient is when they conflict, but otherwise they're much easier to work with.
- Joker_vD 5y agoYes, "worse is better", the ultimate reason of why inferior technical decisions get universally adopted :/ Of course, one day the technical inferiority finally shows itself (e.g., the ports do conflict), and then people start to heroically overcome the obstacles they've created for themselves, showing outstanding feats of ingenuity. Just google "port allocator"! Every company inevitably writes their own home-grown one because everyone's deployment/integration pipeline is unique.
- macintux 5y agoYou could always launch once using that scheme, stash the port that you’re offered, and re-use that until it stops working. It’s likely that the port will be available indefinitely.