51–60 of 99 posts
and .... it's buggy try https://www.google.com/search?q=timer+724+years click on start, looses most of the time
..and curiously, with the little speaker icon 'on', it produces no audio alarm for me, (firefox 103.0.2). Whereas this[1] one produces a quite notable sound. [1] https://www.online-stopwatch.com/countdown-timer/
and .... it's buggy try https://www.google.com/search?q=timer+724+years click on start, looses most of the time
Is it really buggy? Is it a feature that you need a timer of 724 years ... in a web browser?
I can absolutely think of a reasons why someone would use this. For example, a DM in a role playing game might pull up a very long timer as a prop to show their players.
I agree that "the number of times you want a 724 year timer to count to zero" is negligibly small, but that is a minor subset of "the number of times you want to show a 724 year timer counting towards zero"
Earlier quoted context omitted.
OP took things a little far, you can make it glitch at the 5 day mark. You may ask why I'd need a timer in my web browser for 5 days, and you be right to do so.
Haha. I'm not even for sure why I need a timer in the web browser at all. However, I will concede it is indeed rather buggy. A Google search of "timer 3 minutes" does nothing for me, as it just performs a normal search with no timer widget. A search of "timer 2 minutes" or "timer 4 minutes" works fine.
How are people supposed to use features like this if they get dropped and re-added from time to time? If I want a convenient timer, googling "set 5 minute timer" has no advantage if I don't know whether it will work or not. Inconsistency is an enemy of convenience.
Your software never has bugs? We definitely had to turn something off before because something didn't line up/someone messed up planning during a bigger tech transition. This stuff happens in big orgs ran by humans, I'm happy that it's back and it's a lot better than the first result in any case.
Earlier quoted context omitted.
Sure, a bug is a bug, but the original remark was that the software was "buggy". I read "buggy" as riddled with pretty obvious bugs. If we're calling software "buggy" for having any bugs, then, I guess, nearly all software is "buggy" (and the word looses its usefulness).
Anything over 100 hours gets recalculated modulo 100, so 101 hours becomes 1 hour. But then the page title, which is meant to show the current countdown in the tab display, gets updated to show the full time, but weirdly formatted. So at least two bugs. Try "timer 101 hours". The page title will (very quickly) show "10:05:9x" where x is the 10s digit of the seconds. While the page itself claims it's a one hour timer…
and .... it's buggy try https://www.google.com/search?q=timer+724+years click on start, looses most of the time
Earlier quoted context omitted.
Your software never has bugs? We definitely had to turn something off before because something didn't line up/someone messed up planning during a bigger tech transition. This stuff happens in big orgs ran by humans, I'm happy that it's back and it's a lot better than the first result in any case.
I know that software is fiendishly difficult, but if you think a parent is ever going to put their child in a software driven car, then the industry had probably better get a bit more serious.
How are people supposed to use features like this if they get dropped and re-added from time to time? If I want a convenient timer, googling "set 5 minute timer" has no advantage if I don't know whether it will work or not. Inconsistency is an enemy of convenience.
Earlier quoted context omitted.
I know that software is fiendishly difficult, but if you think a parent is ever going to put their child in a software driven car, then the industry had probably better get a bit more serious.
This doesn't make any sense. "Software" isn't produced by a single company with a single set of engineering practices and trade-offs. Safety-critical software has been around for decades and decades, and it's not developed and tested using the same practices as a minuscule D-list feature of a web service.