3 ms·
Classic HackerNews " This is so easy and I, a software developer with no actual experience in that area, know the obvious solution that eludes that hundreds of
by freddie_mercury 7y ago
Classic HackerNews "
This is so easy and I, a software developer with no actual experience in that area, know the obvious solution that eludes that hundreds of developers with actual experience in the area. Meanwhile, I take umbrage when my product manager tells me that implementing the next feature will be easy and I'm exaggerating how complicated it is."
- theonemind 7y agoPerhaps so. But, if (not_visible) { suspend_wait_and_stop_consuming_resources } I can imagine that it gets massively more complicated. However, as, say, an executive, this probably indicates that you can lean on your sw dev staff to approach the asymptotic ideal that looks so simple if you really care about the goal.
- icebraining 7y agoOf course, and all major browsers have background tab throttling features[1]. But there are multiple goals and limited dev time. [1] E.g. Firefox added some in version 58: https://developer.mozilla.org/en-US/docs/Web/API/Page_Visibility_API#Policies_in_place_to_aid_background_page_performance https://developer.mozilla.org/en-US/docs/Web/API/Page_Visibi...
- paulintrognon 7y agoReminds me an old boss I had who, when I reported a complicated problem, always came up with: "why don't you just write if (problem) { solution(); } ? Should'nt take long, should it? Well, the difficult part is not writing an if statement...