News for hackers. Stuff that matters.
Re:Slack using React Dev Build in Production by usegolang on Tuesday August 01, 2017 @09:39AM (#14900444)
I'm not sure how effective it is but I always liked the idea of forcing engineers to use those 3g speeds 1 day a week so they are more inclined to support those customers. Iirc FB does this to some degree, but I think they have a different lightweight version of FB intended for those audiences
Re:Slack using React Dev Build in Production by k__ on Tuesday August 01, 2017 @09:56AM (#14900608)
Sounds good, but in my experience 3g also varies by an order of magnitude (5 KB/s - 50 KB/s).

When I have 20-50 KB/s stable 3g, browsing the web is a bit slow, but most sites work pretty good. Also messenger aren't a problem.

But working below 20 KB/s is a pain.

Re:Slack using React Dev Build in Production by ed312 on Tuesday August 01, 2017 @11:14AM (#14901526)
Chrome dev tools has a reasonable connection bandwidth simulator. Is there a good one that also simulates variability / packet loss in addition to bandwidth caps?
Re:Slack using React Dev Build in Production by josephg on Tuesday August 01, 2017 @11:10AM (#14901461)
It'd be nice to have a simple way to limit a chrome tab's available CPU in the same way. The computers, tablets and phones most people browse on are an order of magnitude slower than the desktop machines we use to develop.
Re:Slack using React Dev Build in Production by irth on Wednesday August 02, 2017 @07:27AM (#14909647)
You can throttle the CPU in Chrome Devtools
Re:Slack using React Dev Build in Production by atonse on Tuesday August 01, 2017 @10:52AM (#14901216)
Yup – I love this idea. I actually occasionally test my single page apps under 3g connections to see how the loading experience works.