This is what I was saying when I asked if he had spent money for redundant refrigeration and cooking for his own use; sadly, all the ACs chose to misunderstand me.
I assume your house has a backup refrigerator and stove in case one of the primaries goes down:) Seriously, our grid is in far more danger from a CME taking it out. The chances of multiple, coordinated, successful terrist attacks blacking out the country are miniscule. Chalk this story and its ilk up to security theatre industry's version of sabre-rattling.
You're skipping the part where the project was understaffed in the first place, requirements were ill-defined and ever-changing, and the final arbitrary, unrealistic, pie-in-the-sky delivery deadline date (the ONLY immutable thing in the whole goddam project) was pulled out of someone's ass. Oh. And the devs got pulled away on occasion to fix hair-on-fire bugs in projects they worked on previously (or even better: had no experience with).
I really don't understand why TFS starts with "A new bug in Outlook..." - after all, it's the SAME bug in Outlook -- since about 1997. Looks like the marketing department at Microsoft, in their endless desire for yet more whizzo shit has (potentially/inevitably) won yet another Pwnie Award.
Whenever I see someone with a palm-shaped bruise on their forehead, I know they're a Windows sysadmin. This one reminds me of that Windows Explorer bug that executed arbitrary code from inside image (picture) files when you opened the directory they were stored in.
"As if millions of voices cried out 'DUH!!!' and were suddenly silenced."
Myself, I'm a long time customer of the nice Jewish boy who owns the local pawn shop. Gotten some great deals there, especially on the second purchase of the day. Donald Trump is right, "those people" love to haggle:-D
The problem with diamonds (for us little folks, at least) has always been that you buy diamonds at retail, but sell them at wholesale. So that pretty much rules them out as "investment grade" anything.
The early (at least through OS/2) Microsoft developers and "architects" were VMS guys, which used the forward slash to pass command line arguments. This is how you ended up with, for example, linker arguments like/NODEFAULTLIBRARYSEARCH which could be abbreviated as/NOD. By the time heirarchical directories came around, (and they had seen UNIX) as you say, the slash was already in use, and so the backslash (the UNIX literal escape character) was used instead. A similar thing happened with CR/LF vs LF. As a result of the two, much hilarity has ensued, lo, even unto the third generation of users.
Yeah, it's on my shelf, too. Thing is, had it come out a few years later, the world would probably be running on it today. When the book came out, there WAS no "internet" as we think of it today; not for individual users. By the time Linux came out (from Minix), there was enough internet infrastructure in place so that people all over the world could form a virtual community to work on the source together.
How about instead we pound a wooden stake through its heart, burn the body, salt the ashes, apply holy water, weld it into an iron urn covered with runes and annointed with the boold of seven virgins and bury it at a crossroads under a full moon?
From TFP: In the 4 months since first detection, ASASSN-15lh radiated (1.1 +/- 0.2) * 10^52 ergs.
If my math is right, that's 10^38 Joules/sec. or 10^35 kWh.
Conversely, I do have a lot of electrolytes - it's what plants crave.
I wonder what happens when you pump 1.21 gigawatts into one.
Nah. If you want to get upskirted by a database, you're gonna have to go with Squeel Server.
This is what I was saying when I asked if he had spent money for redundant refrigeration and cooking for his own use; sadly, all the ACs chose to misunderstand me.
while (isUsingAppleProduct())
;-D
return (lookOf(DISMAY));
Silly-ass Slashdot <code> block ignores leading spaces. Good Thing (TM) I'm not using Python
I assume your house has a backup refrigerator and stove in case one of the primaries goes down :) Seriously, our grid is in far more danger from a CME taking it out. The chances of multiple, coordinated, successful terrist attacks blacking out the country are miniscule. Chalk this story and its ilk up to security theatre industry's version of sabre-rattling.
Here you go.
You're skipping the part where the project was understaffed in the first place, requirements were ill-defined and ever-changing, and the final arbitrary, unrealistic, pie-in-the-sky delivery deadline date (the ONLY immutable thing in the whole goddam project) was pulled out of someone's ass. Oh. And the devs got pulled away on occasion to fix hair-on-fire bugs in projects they worked on previously (or even better: had no experience with).
Sorry, didn't realize it was a Jenna Marbles "Thanks, Obama!!"
Actually, this whole asset forfeiture thing was an invention of George H.W. Bush's War On Drugs, but don't let facts get in your way.
FTFY
I really don't understand why TFS starts with "A new bug in Outlook..." - after all, it's the SAME bug in Outlook -- since about 1997. Looks like the marketing department at Microsoft, in their endless desire for yet more whizzo shit has (potentially/inevitably) won yet another Pwnie Award. Whenever I see someone with a palm-shaped bruise on their forehead, I know they're a Windows sysadmin. This one reminds me of that Windows Explorer bug that executed arbitrary code from inside image (picture) files when you opened the directory they were stored in.
"As if millions of voices cried out 'DUH!!!' and were suddenly silenced."
Unfortunately for you, the boards of directors of every coal and oil company got there first.
Myself, I'm a long time customer of the nice Jewish boy who owns the local pawn shop. Gotten some great deals there, especially on the second purchase of the day. Donald Trump is right, "those people" love to haggle :-D
The problem with diamonds (for us little folks, at least) has always been that you buy diamonds at retail, but sell them at wholesale. So that pretty much rules them out as "investment grade" anything.
The early (at least through OS/2) Microsoft developers and "architects" were VMS guys, which used the forward slash to pass command line arguments. This is how you ended up with, for example, linker arguments like /NODEFAULTLIBRARYSEARCH which could be abbreviated as /NOD. By the time heirarchical directories came around, (and they had seen UNIX) as you say, the slash was already in use, and so the backslash (the UNIX literal escape character) was used instead. A similar thing happened with CR/LF vs LF. As a result of the two, much hilarity has ensued, lo, even unto the third generation of users.
As I said:
no "internet" as we think of it today; not for individual users.
In other words, yes it had INSTITUTIONAL users, not people dialing in from their homes.
Secondly, BZZZT! WRONG!
I think I know which one of us is thea stupid troll -- his nick is gavron.
Yeah, it's on my shelf, too. Thing is, had it come out a few years later, the world would probably be running on it today. When the book came out, there WAS no "internet" as we think of it today; not for individual users. By the time Linux came out (from Minix), there was enough internet infrastructure in place so that people all over the world could form a virtual community to work on the source together.
So you're suggesting that when we all do better, we all do better? That's preposterous! Why do you hate America?
Walmart is Skynet.
Nah. The funniest Redd Foxx moment was when he fell over dead from a grabber IRL.
The one where "endtoend" appears as one word, but "ad hoc" appears as two - in the same quote.
How about instead we pound a wooden stake through its heart, burn the body, salt the ashes, apply holy water, weld it into an iron urn covered with runes and annointed with the boold of seven virgins and bury it at a crossroads under a full moon?
because That's they're using using UDP.