• Chris (unregistered)

    How is the watchOS update a WTF? Those slightly sloppy update notes were written by a human, no code and no bugs were involved here.

  • David Hemming (unregistered) in reply to Chris

    Perhaps the URL is cut off in the original too?

  • dusoft (unregistered) in reply to David Hemming

    I also don't get it.

  • (nodebb) in reply to Chris

    Yup!

  • (nodebb) in reply to dusoft

    "not getting" atrial fibrillation is a GOOD thing <wink>

  • Andrew Miller (unregistered)

    Maybe they are hoping one of Marty McFly's kids might apply for their College Program?

  • richarson (unregistered) in reply to Chris

    Is it an April's fool joke on us, maybe?

  • tbo (unregistered) in reply to Chris

    I think it's that it's available where it's available? But I'm pretty sure it's trying to say that the updates are available in regions where afib detection is available.

  • express(vpn) my condolences (unregistered)

    So is the simple work around for people who want a feature that's not in their region to simply use a VPN to get it? I wonder if it's automatically disabled as soon as you enter another jurisdiction (read: stop using the vpn server).

  • markm (unregistered)

    The "up by 0" is probably from the careless use of floating point comparisons and rounding off. The change is probably more than 0.0 but less than 0.5. In floating point, even if a difference should be zero, it usually is not exactly zero, so this code will often fail:

    if(change > 0.0) printf("Up"); else if (change < 0.0) printf("Down"); else printf("No Change");

    Even when the change was mathematically zero, rounding errors in the calculations will generally make it a tiny bit positive or negative so "Up" or "Down" will randomly come out when "No Change" was expected. One fix is to define a constant for how much difference from 0 will count as not zero, say tol = 0.01, and test it like this:

    if(change > tol) printf("Up"); else if (change < -tol) printf("Down"); else printf("No Change");

    In this case, tol is 0.5, and a more reliable way is to round 'change' to the nearest integer first, then test the rounded number. This ensures that "Up", "Down" or "No Change" case will always match the displayed change.

  • Loren Pechtel (unregistered)

    The air conditioner is just spellcheck or autocorrect, not WTF level.

  • (author)

    The commenters who insist that autocorrect errors, spelling errors, and human language errors are not strictly software bugs are, of course, completely correct (possibly excepting some kinds of autocorrect errors). It doesn't matter, though. They are a kind of error, they're at least mildly amusing or irritating to this editor, and that's all that is required to clear the incredibly low bar to inclusion in this column. Truly epic errors are fortunately scarce.

  • (nodebb)

    No one's asking Paul to debug the code. Just to copy&paste some not too hard to find text.

  • Flinx (unregistered)

    Nah, diving into any kind of source code is definitely not a task for the average Joe User. Exactly that's why it's called "Developer Tools" in the first place. Most of the users don't even know about this web browser feature and became instantly afraid of just having broken "The Internet" when accidentally hitting F12.

    If one really needs any client-side output, one should provide a neat javascript procedure together with a nice and shiny button named "Report this error" that automatically collects and sends all the required log data back to the server. For extra credits (as in privacy and transparency) one may provide the collected data (and nothing more) to the user and ask for a final confirmation right before submitting.

  • (nodebb) in reply to Flinx

    Depends on the website, but yeah, it could and should have been done better. It just ain't debugging.

  • IChrisI (unregistered)

    The Javascript error console seems to be a WordPress thing, not a Bugsnag thing. There's an article about it on wordpress.org.

  • dereferenced null pointer (unregistered)

    Oh, that date selector ends in 2032; I wonder if its possible to select a day/month combination after the Epoch and see the application burn?

  • ichbinkeinroboter (unregistered) in reply to TheCPUWizard

    The text is about updates to atrial fibrillation NOTIFICATIONS. Like it improves the detection or the notifications ( I read it as the latter). Unless I misread it? It makes total sense to me.

  • ichbinkeinroboter (unregistered) in reply to TheCPUWizard

    The text is about updates to atrial fibrillation NOTIFICATIONS. Like it improves the detection or the notifications ( I read it as the latter). Unless I misread it? It makes total sense to me.

  • (nodebb)

    The iOS post reminded me of a recent exchange with someone regarding Headphone Safety notifications. This person was in the UK and was complaining about not being to turn them off in settings. I had shared screenshots with them how, but they sad it wasn't available where they lived. But they checked again, and lo and behold, they were able to. After a big of searching - it turned out that was an EU regulation, and now that the UK left the EU, he was able to turn off the notifications. We were very amused by this fact.

Leave a comment on “Time's Up”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article