|
Steve Raw wrote: Sure, it's a complete UI violation
Also, every website it the late 90's/early 00's had this 
|
|
|
|
|
Back to how it should be | CommitStrip[^]
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Gotta love it when people pretend they did something themselves when the pros know it was a copy and paste situation.
Jeremy Falcon
|
|
|
|
|
I remember this effect. We all probably ripped it off from the same source. Don't forget to quote your sources.
Jeremy Falcon
|
|
|
|
|
I think I prefer the original... With falling asterisks instead of amorphous blobs.
Found it on a webpage around 2000-ish, couldn't (quickly) disentangle the script from the page, so rolled my own.
|
|
|
|
|
|
mmm "retired author?"
that's new.
@sean-ewington wanna have a look?
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Weird. All fixed.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
I really don't understand this one, I have solved this kind of problem multiple times in different languages on different platforms.
|
|
|
|
|
Julian Ragan wrote: I have solved this kind of problem multiple times
Really? Did you account for all possible issues:
- are T1 and T2 in the same time zone?
- did Daylight Saving Time occur between T1 and T2?
- did rules for DST changed between T1 and T2?
- where any leap second jumps between T1 and T2?
Randall knows best
Mircea
|
|
|
|
|
Oh dear, seems I have never needed that much accuracy after all. And in some cases such deliberations would not be possible on target platform.
|
|
|
|
|
Don't forget
Are T1 and T2 in the same relativistic frame?
|
|
|
|
|
And how many commercial breaks were there during that period?
|
|
|
|
|
|
Always interchange and compare dates/times in UTC.
I wouldn't bother with leap seconds unless you need to know the seconds, and you generally don't.
|
|
|
|
|
I agree with you, but I know some people in the lounge were arguing for using local time. Go figure!
Mircea
|
|
|
|
|
Say it ain't so.
Probably the sort who wear digital watches and read off the exact time to the second. 
|
|
|
|
|
At some point it is not possible to generalize this sort thing.
I worked on a system where a work flow needed to be resolved within '3 business days'.
So a casual developer is going to look at that and perhaps understand it means 'skip the weekends'
But in fact it is quite a bit more complex.
- A business day consisted of 8 hours.
- Holidays were not business days. (This of course required adding a complete sub-system to allow them to specify holidays.)
- A work flow could be started in California but would be viewed and acted upon in New York. So obviously time zones were relevant.
Also consider the complications for the following sort of report
- Company operates brick and mortar stores across the country
- Company has an online site to order products
- VP asks for a report that summarizes sales during the 'lunch hour'
|
|
|
|
|
From the CP newsletter
AMD says overclocking blows a hidden fuse on Ryzen Threadripper 7000 to show if you've overclocked the chip, but it doesn't automatically void your CPU's warranty | Tom's Hardware[^]
"Per AMD’s standard Terms of Sale, the warranty excludes any damage that results from overclocking/overvolting the processor. However, other unrelated issues could still qualify for warranty repair/replacement"
Anyone with more hardware experience care to speculate on what might stop working on a single overclocked chip that AMD would not claim it was due to that?
I was thinking if someone discovered a bug in all of the chips, they would probably agree that the overclocked ones failed in same way.
But other than that it would be up to the buyer to prove, somehow, that it wasn't due to overclocking.
Perhaps related question - does anyone really warrant chips that are overclocked? Seems like if they could demonstrate that overclocking was always successful then why wouldn't they just sell it for that speed?
modified 14-Dec-23 11:13am.
|
|
|
|
|
Maybe to protect against false-positives? The fuse could fail even if the chip hadn't been overclocked?
|
|
|
|
|
It really relates to yields. The higher the clock speed the more voltage, heat and capacitance leakage occurs internally. This lowers the yield of good to bad CPU chips. The manufacturer wants to keep the yield as high as possible while still meeting the minimal clocking goals.
|
|
|
|
|
jschell wrote: Perhaps related question - does anyone really warrant chips that are overclocked? Seems like if they could demonstrate that overclocking was always successful then why wouldn't they just sell it for that speed?
I'm pretty sure you can tune Intel's K and X chips without voiding the warranty, but don't quote me on that. They do market it and charge extra specifically for those features.
That being said, there's limited value to overclocking these days, as most x86 based chips these days are clocked to within an inch of their life from the factory (at least under load). Also the high end chips already virtually require liquid cooling, so you're not going to improve the situation much even with liquid on those chips.
The hot ticket these days is undervolting rather than overclocking, at least on Intel. I don't follow AMD, because I won't buy them right now for desktops.
I'm not sure about undervolting an AMD, or if that would blow a tattle fuse, but I can almost see why they'd have one for overclocking, due to the above.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
honey the codewitch wrote: I'm pretty sure you can tune Intel's K and X chips without voiding the warranty, but don't quote me on that.
I have a few machines with Intel CPUs with the "K" suffix to their names, and was specifically told those were intended for the "enthusiasts" market (their term, not mine) who like to tinker with overclocking. Not that this was something I ever asked for, as (IMO) overclocking = more voltage = more heat = more problems = not worth my time.
I laugh at gamers who spend more time tinkering with endless overclocking settings than playing actual games, and complain that so-and-so doesn't know how to optimize code when they themselves would have a hard time putting together a functional for loop...
|
|
|
|
|
The only "overclocking" i do on my desktop is I run my RAM at 6000/CL32, which it's rated for and I bought it for. It's basically a factory overclock as they tested it at that speed and prepared an XMP profile for it, which I use.
On my laptop I undervolt. My settings reduce my CPU performance, but keep it under 90C which is what I like.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
honey the codewitch wrote: keep it under 90C which is what I like
 I think most people would like to keep their system running under 90C.
If you weren't underclocking, how high would it otherwise get? That's not normal...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
