So since the RFC specifies GMT it is already up to 0.9 seconds wrong?
352 karma · joined March 31, 2015
So since the RFC specifies GMT it is already up to 0.9 seconds wrong?
Anyway, what I missed in your app was a method to use the keyboard to play the drums. Using the touchpad is too slow.
Today I found a bug in the editor of the Commodore 64. It has been there for at least 30 years.
You do not need to buy extra content, controllers, etc to "play the game". But you can spend a lot of money to make it as realistic as you want.
I work for a company with about 40 employees. Our offices are connected to two different ISPs: one by optical fiber and one by VDSL. We have two different telephone operators for our outgoing calls from the offices, and I have two mobile phones with different operators.
During the last five years there have been multiple outages that lasted between minutes and days, but most of the times the redundancy have saved us. But when we lost power (the whole city went dark for hours) we went down when the batteries in the UPS was drained. Having our own generators is too expensive.
Was that intentional?
https://www.youtube.com/watch?v=djV11Xbc914
"Take on me" translated word for word will be "ta på meg" (Norwegian) or "ta på mig" (Swedish), meaning "touch me".
> MySQL’s replication architecture means that if bugs do cause table corruption, the problem is unlikely to cause a catastrophic failure. Replication happens at the logical layer, so an operation like rebalancing a B-tree can never cause an index to become corrupted. A typical MySQL replication issue is the case of a statement being skipped (or, less frequently, applied twice). This may cause data to be missing or invalid, but it won’t cause a database outage.
So, data might be invalid or missing, but it will not cause a database outage...
The author of "Cubase64" (Pex "Mahoney" Tufvesson) has written an interesting explanation of how it is made: https://livet.se/mahoney/c64-files/Cubase64_White_Paper_by_P...
The technique used in the two first links of parent comment, is, as I understand it, based on another work of Pex : https://livet.se/mahoney/c64-files/Musik_RunStop_Technical_D...
The first time I was about 13 years old, and was swimming in the Mediterranean. Me and a friend had swim out to a raft, and when we where swimming back to the beach we made a bad decision to swim against the wind to a floating rope, instead of straight in. After about half the way I was exhausted, but I realized it in time, and turn on my back I yelled for help. My friend didn't notice, but people from the raft noticed and helped me.
The second time was in a lake, and I must have been about 20 years old. A lot of friends was swimming out and I followed, only to realize that it suddenly was too deep to stand on the bottom. I turned around and began to swim back to the beach. This time I felt the panic. I used all my energy to swim back, trying to keep my head above the water. Another friend was on the beach, recording me with his video camera (with zoom). Calling for help was not an option in my head. All energy went to keeping the mouth above the water. I exhaled under water, to maximize the time I had to inhale while the mouth was above water. I remember thinking "Stop filming and help me". Finally I felt the bottom again, and could stand on it. I have never seen that video recording and I don't remember if I ever told him how close he was to record my downing in full color...
(Sorry for errors, English isn't my native language)
In a big budget project, they had implemented a report, like sales per month or something similar. The requirement was to sort the result by month. Any sane person would sort it by the order the months happens in a year, like January, February, March, etc... But not Oracle: April, August, December, February, January, July, June, March, May, November, October, September.
Technically they are sorted... and they requirements only said sort by month. To get it fixed the customer had to pay Oracle more money, since they changed changed the requirements.