#webdev tip: do all of your browser testing in 2G. everyone wins.

@jalcine @mishari Where can I use 2G?

@veer66 in the simulator. The point is to keep the code tight. @jalcine

@mishari @jalcine Wouldn’t it be too tight?

@veer66 What is too tight? If your software/site flies on 2G; it'll be an amazing experience for those on 2G and highers. The lesson here is that to have a stellar experience, designing and testing in the most common (and usually overlooked) parameters can lead to great results. @mishari

@jalcine @mishari Too tight means testing on too slow network e.g. 2400 bps modem. This leads back to my first question. I will rephrase it. Where do people still use 2G?

@veer66 I use VIM so 300bps works perfectly ok for me. @jalcine

@mishari @jalcine Do you still use 300bps modem?

@veer66 @mishari No lie, I haven't responded for a few reasons:

1) There's no strong case against testing in low speed environments: it literally helps you improve speed times when testing code

2) This "request for evidence" is something you can handle as easily and in the same amount of time you've requested it over here: http://bfy.tw/LeDr

@jalcine @mishari Maybe problem isn't about 2G.

@veer66 the point is not 2G the point is constraints force you to implement better design. @jalcine

@mishari @jalcine I agree with limiting connection speed to test the web. However, with 2G speed, I have to exclude podcast, video, etc. And I have no information that any potential target still use 2G.