3 ms·
In my opinion, (2) is a feature, not a bug. You never know what kind of connection your users have. Ngrok forces you to consider the "bad connection" factor ear
by paskozdilar 5y ago
In my opinion, (2) is a feature, not a bug. You never know what kind of connection your users have. Ngrok forces you to consider the "bad connection" factor early on in development, which can avoid many pitfalls that occur when network software assumes that latency is zero and bandwidth is unlimited.
- skinnymuch 5y agoIt’s not a feature imo when there are other ways to force a “bad connection”. However with ngrok if latency is bad. You can’t ever change fhat.
- paskozdilar 5y agoThat's a fair point. I suppose latency is important if you use ngrok for something other than development. I use ngrok exclusively for development, so that's where my comment comes from.
- danielvaughn 5y agoYeah I don't fault them at all - what they're doing is going to be inherently difficult from a latency POV. I'm really comparing it against just opening a port to your local network.