You can thank whoever convinced Dubya that moving the transition date to make the "summer" portion larger would somehow save energy. Not only does it not save energy, it makes things real fun for people writing code for embedded devices that need to work on schedules and automatically adjust DST (without nice comfy NTP sync because the device isn't networked) when you fuck around with DST dates.
I even put a hidden menu in the product I work on to allow changing the DST dates without having to scramble to deploy firmware for a non-networked (as in someone needs to physically do the firmware update) device all over the U.S. on short notice. Punching a few buttons to change a number is much easier to explain and harder to fuck up.
The title contains a pet peeve of mine: it's Daylight Saving Time, not 'savings.' It's not a bank where you deposit an hour and get it back in a 'savings account.'
It's also Daylight Saving Time, not Energy Saving Time. The purpose is to normalize sunrise so that you won't get awakened by sunrise at 5AM in the summer and go to work in the dark at 7AM in the winter. IT DOES NOT SAVE ENERGY ONLY DAYLIGHT, by moving that extra-early sunrise to the end of the day. The last time someone brought that up, Dubya said "Oh yeah we gots to save us some energy!" and he happily went for changing the DST dates.
(I've heard that some of the push was from candy companies wanting sunset later, apparently on the mistaken assumption that people everywhere in the US do their Halloween kiddie stuff before sunset. Here in fly-over country, aka Texas, I've only ever known it to start at sunset. Which means that we now actually have an hour less for the kids to go door-to-door before they have to get to bed. The only real evidence I've ever seen that other places do it before sunset is a Parks and Recreation episode from last year. Yes, seriously.)
But the idea that U.S. television schedules already use two time zones three hours apart is, however, interesting. The time of sunrise would be different in each half, with each half starting work at the same local time as well as UTC time, but DST would still fulfill its function of normalizing sunrise time. (Fortunately we don't have to worry about Canada's Atlantic and Newfoundland time zones. And Alaska could even fit in because Eastern and Pacific are be the centers of the TV time zones.)
(Do they really honestly work 9-to-5 on the east coast, you know, like in that song, including lunchtime? The standard work day is 8-to-5 over here because of lunch.)
To be fair, although there aren't really good reference objects for size in the pictures, it does look like the whole thing is indeed four stories tall. But the individual containers sure aren't 12 meters high, or there would be trouble trying to transport it "by road".
Apparently in this case it was more of a "bystander-rich environment". All those passengers kept getting in the way of his objective of shooting TSA people.
"He saw me. He looked at me with a quizzical look and said, 'TSA?' And I just shook my head. So he moved on," Saryan said.
Isn't this the same LAPD that opened fire on the wrong color and type of pick-up truck a few months ago, putting over fifty holes in it, yet still only managed to have one or two bullets even injure the two people inside?
http://jalopnik.com/meet-the-guy-who-drove-across-the-u-s-in-a-record-28-h-1454092837
Yeah, NINETY-EIGHT MPH average speed. With two extra fuel tanks in the trunk for 800 miles range (the thing reeked of gasoline), and the spare tire was on the back seat next to the third guy (spotter/navigator). They didn't just break the previous record, they shattered it.
When I was much younger, I disassembled the Level II BASIC on my TRS-80. Not bad code at all, and I think I found only 35 bytes or so (out of 12K) worth of not using Z-80 JR instructions and other minor silliness. It's the reason I like to say that Bill Gates taught me assembly language, or at least 8080 assembler.
The code was however strictly 8080 code aside from the JR instructions and maybe a couple of shifts/rotates, and didn't teach me any cool tricks about using the Z80. (Looking at some C compiler generated Z80 code a few years ago really blew my mind in some of the things it did, though it was still mostly rather crappy.)
For instance, Fallingwater: "...the contractor had indeed added reinforcement over Wright's plan; nevertheless, the cantilevers were still insufficiently reinforced." That thing was literally ready to fall into the water.
Though for what it's worth, some of the problems were from him designing beyond the then-known standard engineering principles.
A year or two ago there was an attempt to reboot the S&E show, but it only lasted a season. Right now there's something on PBS called "Just Seen It" which replaces the two thumbs with a "three tickets" rating. Three people give a move a full, half, or zero rating (See It, Stream It, Skip It) which are added up to a final rating.
And intentionally choosing file names for source code such that they depend on a quirk of a small minority of filesystems (allowing case conflicting names) is not shaky sand? Thanks, AC, I would have never guessed!
The "workaround" would have been to choose sensible file names in the first place.
It's probably a good idea to make sure your servers are hosted where there is minimal likelihood of natural disasters
That's one of the reasons why Rackspace started in San Antonio. Too far inland for hurricanes to be a problem, far enough south from Hurricane Alley for tornadoes not to be a problem, not in a seismically active zone, and no large bodies of water to cause storm surge flooding.
You'd be better off still with a good ebook on knots
Oh yeah, and maybe some kind of solar or other charger so you can actually read those ebooks for more than a couple of days when the electric grid is down.
Slashdot Mirror
You can thank whoever convinced Dubya that moving the transition date to make the "summer" portion larger would somehow save energy. Not only does it not save energy, it makes things real fun for people writing code for embedded devices that need to work on schedules and automatically adjust DST (without nice comfy NTP sync because the device isn't networked) when you fuck around with DST dates.
I even put a hidden menu in the product I work on to allow changing the DST dates without having to scramble to deploy firmware for a non-networked (as in someone needs to physically do the firmware update) device all over the U.S. on short notice. Punching a few buttons to change a number is much easier to explain and harder to fuck up.
The title contains a pet peeve of mine: it's Daylight Saving Time, not 'savings.' It's not a bank where you deposit an hour and get it back in a 'savings account.'
It's also Daylight Saving Time, not Energy Saving Time. The purpose is to normalize sunrise so that you won't get awakened by sunrise at 5AM in the summer and go to work in the dark at 7AM in the winter. IT DOES NOT SAVE ENERGY ONLY DAYLIGHT, by moving that extra-early sunrise to the end of the day. The last time someone brought that up, Dubya said "Oh yeah we gots to save us some energy!" and he happily went for changing the DST dates.
(I've heard that some of the push was from candy companies wanting sunset later, apparently on the mistaken assumption that people everywhere in the US do their Halloween kiddie stuff before sunset. Here in fly-over country, aka Texas, I've only ever known it to start at sunset. Which means that we now actually have an hour less for the kids to go door-to-door before they have to get to bed. The only real evidence I've ever seen that other places do it before sunset is a Parks and Recreation episode from last year. Yes, seriously.)
But the idea that U.S. television schedules already use two time zones three hours apart is, however, interesting. The time of sunrise would be different in each half, with each half starting work at the same local time as well as UTC time, but DST would still fulfill its function of normalizing sunrise time. (Fortunately we don't have to worry about Canada's Atlantic and Newfoundland time zones. And Alaska could even fit in because Eastern and Pacific are be the centers of the TV time zones.)
(Do they really honestly work 9-to-5 on the east coast, you know, like in that song, including lunchtime? The standard work day is 8-to-5 over here because of lunch.)
And we'll have more at ten... or is it eleven?
Way to go, eh, CBC?
To be fair, although there aren't really good reference objects for size in the pictures, it does look like the whole thing is indeed four stories tall. But the individual containers sure aren't 12 meters high, or there would be trouble trying to transport it "by road".
Apparently in this case it was more of a "bystander-rich environment". All those passengers kept getting in the way of his objective of shooting TSA people.
"He saw me. He looked at me with a quizzical look and said, 'TSA?' And I just shook my head. So he moved on," Saryan said.
Isn't this the same LAPD that opened fire on the wrong color and type of pick-up truck a few months ago, putting over fifty holes in it, yet still only managed to have one or two bullets even injure the two people inside?
http://jalopnik.com/meet-the-guy-who-drove-across-the-u-s-in-a-record-28-h-1454092837
Yeah, NINETY-EIGHT MPH average speed. With two extra fuel tanks in the trunk for 800 miles range (the thing reeked of gasoline), and the spare tire was on the back seat next to the third guy (spotter/navigator). They didn't just break the previous record, they shattered it.
http://kinja.roadandtrack.com/new-cross-country-record-forget-the-glamor-bring-the-1456737864/@matthardigree
One word: bedpans.
http://jalopnik.com/everything-you-need-to-know-about-afroducks-fastest-ma-1256425384
Afroduck is a perfect example of why most people who do this stuff wait a year for statute of limitations reasons. These guys may have been foolish to announce so soon; we shall see what kind of heat they get for it.
When I was much younger, I disassembled the Level II BASIC on my TRS-80. Not bad code at all, and I think I found only 35 bytes or so (out of 12K) worth of not using Z-80 JR instructions and other minor silliness. It's the reason I like to say that Bill Gates taught me assembly language, or at least 8080 assembler.
The code was however strictly 8080 code aside from the JR instructions and maybe a couple of shifts/rotates, and didn't teach me any cool tricks about using the Z80. (Looking at some C compiler generated Z80 code a few years ago really blew my mind in some of the things it did, though it was still mostly rather crappy.)
Obligatory mention here that PhD stands for "Piled higher and Deeper".
For instance, Fallingwater: "...the contractor had indeed added reinforcement over Wright's plan; nevertheless, the cantilevers were still insufficiently reinforced." That thing was literally ready to fall into the water.
Though for what it's worth, some of the problems were from him designing beyond the then-known standard engineering principles.
And that, kids, is how Spinal Tap became the #1 band of all time.
Fortunately for Android users, many of them won't have upgrade problems because they won't be able to upgrade.
A year or two ago there was an attempt to reboot the S&E show, but it only lasted a season. Right now there's something on PBS called "Just Seen It" which replaces the two thumbs with a "three tickets" rating. Three people give a move a full, half, or zero rating (See It, Stream It, Skip It) which are added up to a final rating.
You don't build a foundation on shaky sand.
And intentionally choosing file names for source code such that they depend on a quirk of a small minority of filesystems (allowing case conflicting names) is not shaky sand? Thanks, AC, I would have never guessed!
The "workaround" would have been to choose sensible file names in the first place.
Woosh. You're not noticing that it can be parsed as ((third world) war)
Huh? But we've had plenty of war in the third world! Iraq, Afghanistan, Libya, Syria...
Not sure, but she could immediately post it on her Google+ page...
FTFY. The Google Re-education Squad will visit you shortly.
So if someone wearing Google Glass was from Massachusetts, would they be a "glassmasshole" or a "massglasshole"?
4chan would have flayed him alive for being hipster enough to use a hashtag. He probably even read it while saying "hashtag" out loud.
It's probably a good idea to make sure your servers are hosted where there is minimal likelihood of natural disasters
That's one of the reasons why Rackspace started in San Antonio. Too far inland for hurricanes to be a problem, far enough south from Hurricane Alley for tornadoes not to be a problem, not in a seismically active zone, and no large bodies of water to cause storm surge flooding.
You'd be better off still with a good ebook on knots
Oh yeah, and maybe some kind of solar or other charger so you can actually read those ebooks for more than a couple of days when the electric grid is down.
You could get invaded by California, I guess. (Except that I'm sure you already are being invaded very slowly by them.)
DUDE! You bought Dell!
So places like DailyKos and Infowars? Except of course those two don't get stuff from each other.
Also, the Brits have 3chan.
A server can also be in a dark corner if someone builds a wall around it.