And just to expand on this, my impression was always that most people in the US wouldn't think twice about getting in the car and driving for 10 hours, while in much of Europe that'd take you across three countries.:-)
They don't generally, for example, take their cars on long-distance holidays like Europeans do. They don't ever get in their car in, say, New York and drive all the way to Charleston; they fly. Whereas lots of Europeans would think nothing of getting in our cars in, say, Manchester, and driving all the way to Bordeaux, or starting a journey in Rome and driving to Zurich.
I'd actually be kinda curious how true this is, because my impression was actually the reverse. This may just be my own personal view, but growing up, we never flew -- the first time I was on a trip by plane I think was in college. But we usually do a trip to somewhere somewhat remote by car about once a year. I made multiple trips by car from central PA to each of St Lawrence Seaway destinations (350 mi, 6 1/2 hrs), northern Vermont (450 mi, 8 hrs), North Carolina (500 mi, 8:45), and even two trips to eastern Nova Scotia (1,200+ mi, 21 1/2 hr). On my own, I've made several trips from Wisconsin to Arkansas (670 mi, 12 hr) and back to my parents' in PA (713 mi, 13 hr). [Times and distances from Google maps.]
With the exception of a flight from PA to Wisconsin, the shortest plane trip I've been on (at least that wasn't part of a larger trip) was about 1000 mi; that was my first plane trip.
Meanwhile, my impression of Europe was that, at least for much of continental Europe, good rail connections and budget airlines meant that people rarely made such trips.
I'd be interested to know which of our experiences is more atypical.:-)
To be honest, I did download it and try it out -- and I much prefer DejaVu mono. I'm sure some of that is what I'm used to, but the Adobe font seems too light to me. In particular, I rather dislike the shorter ex-height (which the author points out as an advantage); I think that it looks even more stretched horizontally than many monospace fonts. It also renders weird for me, but that may just be my setup or something.
Sort of; SRT is software-controlled though (basically software-RAID-based), and is limited to Windows. (Possibly you could set something up with the LVM or similar on Linux though.) Definitely a very different beast from hybrid drives, at least if my assumptions as to how the latter work are any indication.
(You also need a newish computer and it's Intel only.)
I'm not speaking to why the backup software keeps backing up the actual game files; I'm more talking about why cutting the Steam folder out of being backed up will leave some things that won't be replaced.
The complaint isn't Steam startup time, it's the startup time of the individual programs that are launched from Steam. (When it sits there for a few seconds going "Preparing to launch Portal" or whatever, and you want to tell it what's with all the preparing and to stop preparing and just go.:-))
After you explained it it does make sense... I'm just not sure I knew that they killed off the recipient's marrow before transplant. Seems like one of those things I might have known at one time and then forgot, but my brain could just be playing tricks.
Still, I'm still a bit astonished that the mortality rate is that high. Guess that just means there's lots of room for improvement...
[This is a little bit in reply to your child post as well that lists additional statistics]
The real danger is there is about 15 to 50% dying from the treatment itself.
Jesus, I didn't realize that the transplant was so risky. I'd have guessed that the "didn't really get the cancer" part would get a lot of people, but the other problems I'd have not expected. Even MozeeToby's idealistic 5% is surprisingly high to me.
It's sometimes depressing how little we know about how the body works and how little we can do to fix it despite the medical advances of the last 150 years.
to sell here, you MUST implement 'display protection' (its not copy protection; lets call it what it really is).
[citation needed]
IANAL, but to my knowledge selling a display without HDCP or whatever isn't in violation of the DMCA, it just won't be able to display content that requires HDCP. That's different from actively circumventing HDCP.
(Also "display protection" isn't any better a term.)
You're going to have to fix the bug anyway, why not just do it when it is fresh in your mind and keeping you from using the code anyway?
What if those things aren't true? What if you're using your program, discover some edge case with a bug, and don't have time or it's not worth it to fix right away?
Also, it may be that "this was hard to set up" had as much to do with us being weirdos for using it in the first place and thus they didn't have a standard image of it (or much experience) as it just being annoying in general.
Several people in my group are using or were using XP 64 (now transitioning to Win7). Different computers, and none I think purchased with a particular eye toward "this hardware has support."
While my impression is that our IT folks had a difficult time getting them set up, they all worked fine with the exception of AFS support.
XP 64 gets a bad rap, and it probably wouldn't have been a good idea for someone at home who wanted to play games or whatever, but from my observations, the support was as bad as people say (at least eventually).
It was simply a policy of keeping it to yourself,...
What about the discharges caused when a third party outed someone?
Saying DADT just meant you had to keep it to yourself is dishonest. Not to mention inconsistent, or heterosexual people would be kicked out for revealing that, e.g. going "hey guys, check out this photo my girlfrend sent me."
Seriously, I don't understand why it was considered such a bad program...
Without even getting into whether it was fair, because we're expelling people who are qualified? From positions where we lack people? Surely you remember the stories about how the CIA or whatever was really looking for people who could translate Arabic at the same time we were discharging someone under DADT.
Just because DADT was an improvement over what came before doesn't mean it was a terrible policy.
Instead it was treated as an evil concept that should be stomped upon and destroyed as a horrible idea
It kind of was a terrible idea that should be stomped on. Not the most terrible idea we've had, but still pretty darn bad.
Slashdot Mirror
And just to expand on this, my impression was always that most people in the US wouldn't think twice about getting in the car and driving for 10 hours, while in much of Europe that'd take you across three countries. :-)
They don't generally, for example, take their cars on long-distance holidays like Europeans do. They don't ever get in their car in, say, New York and drive all the way to Charleston; they fly. Whereas lots of Europeans would think nothing of getting in our cars in, say, Manchester, and driving all the way to Bordeaux, or starting a journey in Rome and driving to Zurich.
I'd actually be kinda curious how true this is, because my impression was actually the reverse. This may just be my own personal view, but growing up, we never flew -- the first time I was on a trip by plane I think was in college. But we usually do a trip to somewhere somewhat remote by car about once a year. I made multiple trips by car from central PA to each of St Lawrence Seaway destinations (350 mi, 6 1/2 hrs), northern Vermont (450 mi, 8 hrs), North Carolina (500 mi, 8:45), and even two trips to eastern Nova Scotia (1,200+ mi, 21 1/2 hr). On my own, I've made several trips from Wisconsin to Arkansas (670 mi, 12 hr) and back to my parents' in PA (713 mi, 13 hr). [Times and distances from Google maps.]
With the exception of a flight from PA to Wisconsin, the shortest plane trip I've been on (at least that wasn't part of a larger trip) was about 1000 mi; that was my first plane trip.
Meanwhile, my impression of Europe was that, at least for much of continental Europe, good rail connections and budget airlines meant that people rarely made such trips.
I'd be interested to know which of our experiences is more atypical. :-)
To be honest, I did download it and try it out -- and I much prefer DejaVu mono. I'm sure some of that is what I'm used to, but the Adobe font seems too light to me. In particular, I rather dislike the shorter ex-height (which the author points out as an advantage); I think that it looks even more stretched horizontally than many monospace fonts. It also renders weird for me, but that may just be my setup or something.
Huh? That setting chooses whether you want a write-back or write-through cache.
That's not the same thing as saying it supports or doesn't support RAID; in fact, they're almost completely independent.
Sort of; SRT is software-controlled though (basically software-RAID-based), and is limited to Windows. (Possibly you could set something up with the LVM or similar on Linux though.) Definitely a very different beast from hybrid drives, at least if my assumptions as to how the latter work are any indication.
(You also need a newish computer and it's Intel only.)
No, but defense in depth is.
My policy is that when I see a news headline that is a yes/no question, I assume the answer is "no". It works pretty well.
I'm not speaking to why the backup software keeps backing up the actual game files; I'm more talking about why cutting the Steam folder out of being backed up will leave some things that won't be replaced.
Isn't that only for Steamworks-enabled games? And you're out of luck for older things (say, KOTOR)?
The complaint isn't Steam startup time, it's the startup time of the individual programs that are launched from Steam. (When it sits there for a few seconds going "Preparing to launch Portal" or whatever, and you want to tell it what's with all the preparing and to stop preparing and just go. :-))
You can just pull everything back via Steam anyway.
I'm not 100% positive about this, but I'm pretty sure that some games store saved games in the Steam folder.
(That said, I'm nitpicking here; it's not like most people consider saved games to be high-value documents.)
Besides, if you file a chargeback and win, then the service was never paid for. So why are you using it?
Really? It doesn't occur to you that there could theoretically be one fraudulent transaction on an account that is actually used?
(It's been a bit since I saw your response.)
After you explained it it does make sense... I'm just not sure I knew that they killed off the recipient's marrow before transplant. Seems like one of those things I might have known at one time and then forgot, but my brain could just be playing tricks.
Still, I'm still a bit astonished that the mortality rate is that high. Guess that just means there's lots of room for improvement...
[This is a little bit in reply to your child post as well that lists additional statistics]
The real danger is there is about 15 to 50% dying from the treatment itself.
Jesus, I didn't realize that the transplant was so risky. I'd have guessed that the "didn't really get the cancer" part would get a lot of people, but the other problems I'd have not expected. Even MozeeToby's idealistic 5% is surprisingly high to me.
It's sometimes depressing how little we know about how the body works and how little we can do to fix it despite the medical advances of the last 150 years.
to sell here, you MUST implement 'display protection' (its not copy protection; lets call it what it really is).
[citation needed]
IANAL, but to my knowledge selling a display without HDCP or whatever isn't in violation of the DMCA, it just won't be able to display content that requires HDCP. That's different from actively circumventing HDCP.
(Also "display protection" isn't any better a term.)
And not only that, but it's supposedly temporary, presumably while they work on a better fix.
You're going to have to fix the bug anyway, why not just do it when it is fresh in your mind and keeping you from using the code anyway?
What if those things aren't true? What if you're using your program, discover some edge case with a bug, and don't have time or it's not worth it to fix right away?
One more self-reply and then I'm done:
but from my observations, the support was as bad as people say (at least eventually)
Should have been "not as bad as people say"
Also, it may be that "this was hard to set up" had as much to do with us being weirdos for using it in the first place and thus they didn't have a standard image of it (or much experience) as it just being annoying in general.
Ah, I didn't know that the Alpha versions ran in 32-bit modes. I just knew that they were at times supported. Thanks for the information.
Several people in my group are using or were using XP 64 (now transitioning to Win7). Different computers, and none I think purchased with a particular eye toward "this hardware has support."
While my impression is that our IT folks had a difficult time getting them set up, they all worked fine with the exception of AFS support.
XP 64 gets a bad rap, and it probably wouldn't have been a good idea for someone at home who wanted to play games or whatever, but from my observations, the support was as bad as people say (at least eventually).
What's wrong with using a 32 bit OS?
Nothing, until you run across a file where G++ takes 6 GB to compile. :-)
(I've actually seen that.)
No, because there's also a 64-bit version of XP.
If you want to get technical about it, NT has never not supported some 64-bit architecture (though I'm too lazy to check the RAM limits).
What about the discharges caused when a third party outed someone?
Saying DADT just meant you had to keep it to yourself is dishonest. Not to mention inconsistent, or heterosexual people would be kicked out for revealing that, e.g. going "hey guys, check out this photo my girlfrend sent me."
Without even getting into whether it was fair, because we're expelling people who are qualified? From positions where we lack people? Surely you remember the stories about how the CIA or whatever was really looking for people who could translate Arabic at the same time we were discharging someone under DADT.
Just because DADT was an improvement over what came before doesn't mean it was a terrible policy.
It kind of was a terrible idea that should be stomped on. Not the most terrible idea we've had, but still pretty darn bad.
Oh, and while you're at it... if you want an awesome feature request: be able to get directions by clicking on the map instead of typing a location.