Agreed. But that's what you get with a single payer system that doesn't have the funds to treat everyone. You start to have to make decisions about who gets treated and who gets... what did our President say? A pain pill.
I don't think Windows RT devices exist because they are "priced less". I think they exist so that Microsoft can show that they are a player in the ARM space. As a product, it doesn't need to succeed, it merely needs to exist.
I agree, though, that the user base could do without them.
> If Microsoft called the devices and software layer WinTouch or something, that might have helped a little, as a lot of people have been disappointed that a "Windows" computer can't run legacy mouse/keyboard Windows apps.
IIRC that was true of Windows CE also, and cause considerable confusion back then. Everything old is new again etc etc.
I think that this is one more issue that stems with wanting to call everything "windows".
Thanks very much, I was powerful confused by earlier posts. So to paraphrase, WinRT is the run time API for what we call Metro, (on Intel and ARM) and Windows RT is that version of Windows (8, currently) that runs on ARM? Wow, no wonder people are confused.
Line the makers of Gardisil up on the firing line first. And if you feel strongly about protecting them you are more than welcome to stand in front of them to catch the bullets:)
I have to agree. I'm generally in favor of vaccines, (I had a bad case of chicken pox in my twenties -- I'm told I smelled like rotting meat -- daughter got the chicken pox vaccine) but drew the line at Gardisil. I think that was an illustration that you can't take either side of the argument completely at their word.
Which, come to think of it, is true for most arguments.
I dunno, I see it as a toaster meatloaf peeler combo. In an environment where your job required a meatloaf peeler (although you don't see the use) and what you personally really need is to toast some bread.
I wonder how cops will react to citizens having cameras on their persons during altercations with cops? In theory it should be exactly the same thing, but in practice, citizens trying to (legally) film cops during such interactions have not gone well for the citizen.
I dunno, this sounds like a false choice to me. Whether Common Core is good or bad is debatable, and I'm sure there are a lot of people willing to debate you on that. Do the SATs need to be changed? Yes. I could agree with that. But this doesn't mean that the changes suggested are the best way to go about it, or even if the changes are better than what we have now.
A couple of things. First, do you really need to back up all 20 GB of data? How much of that can be recovered by other means? For instance, is it reasonable to back up the OS if you would probably just reinstall anyway? How much of your content did you acquire electronically? Would it be easier to go back to the source?
Thing two: If you really have to back up all 20 GB, the only really practical, cost-effective way to back up that much data is to another set of hard drives. Build up a second array, replicate, and then turn the backup array off. Leave it off except for periodic backups.
For incremental backups, dedicate one removable SATA slot. (I use one of those "hard drive toasters" that plug into a USB slot and allow you to hot-plug a SATA drive.) Plug in a drive on a regular schedule, and copy over the files that have changed recently. Mark it with a sharpie and put it in a safe place.
The idea is to (a) back up only what you couldn't easily recover through other means, (b) back up to the cheapest and fastest per byte, which is currently other hard disks, (c) keep your backup disks turned off when not in use, and (d) Figure out a schedule that suits you. For me, it was replicating the entire array only a couple times a year, supplementing with incremental backups to individual drives every week or so. Yes, you could still lose data, but not nearly as much as if you did nothing. Don't choose a solution so ambitious that you would later tire of it and stop doing it.
Windows ce/mobile agree, but I carried a Palm OS phone for awhile, and it was ok. It ran all the apps from my Pilot and worked OK as a phone. Later I migrated to Blackberry and never looked back. All the capabilities that the Treo should have had and dead nuts reliable. If the offshore admins at my current company could figure out how to keep BES up, I'd still be on Blackberry. Current phone is Android (not Samsung, and I have no intention of marching lockstep with zombie-Jobs) so I guess I'll just get some popcorn and watch the carnage.
> Also, I find it laughable that so many republicans are concerned about 'welfare' and 'entitlement' yet happily sign on for farm subsidy bills that cost trillions, to keep the votes from fat-ass, lazy, uneducated, corn-fed, bigoted midwesterners rollin' right in.
"But they all have smart phones". True, and that doesn't invalidate the XP type interface as superior on the desktop. Granted, phones and tablets are a growing market and desktop not so much, but Microsoft *owns* the desktop, and that would be a big enough market to make a nice living for some time, if they weren't so adamant about forcing a touch interface on it. It's natural for them to want to stretch into markets where they traditionally don't do so well, but they seem stubbornly trying to shoehorn one GUI into all environments. With Windows Mobile, that meant having an inappropriate interface in a market segment where they weren't doing well anyway, but with Windows 8, they're screwing with their base. It doesn't make any damned sense.
The difference here is that the Ukraine already knows what it's like to be under Russian rule. I could imagine that they'd be pretty desperate for that to not happen again.
I know what KVM means, thanks, but you weren't clear about what kind of machines you're using them on.
I'm in IT and I wouldn't have any problem with Classic Shell itself being on a Win8x computer. I use it myself, after all.
And neither would I, if I was forced to use Windows 8. (We as a company decided not to deploy 8. We will stick with 7 and revisit when 9 comes out. We also skipped Vista, incidentally.) The thing is, as an administrator, I don't get to make the rules. The architects don't even make the rules. They make recommendations to management, who then cross reference with legal and others before making the final decision. We (as a company) would not deploy a tool like Classic Shell for the same reason we would not run our business on CentOS. (Which is a fine build -- I use it for prototyping.) It's not a functional issue.
And at home... we had a laptop with touch screen that had been upgraded to 8.1 Pro (or whatever they call it). It was easier to reinstall 7 Pro (from "system recovery") than try to figure out all the absurdities in 8. So even there, we were not forced to use 8, so I again had no use for Classic Shell.
Slashdot Mirror
First thing I thought of, also. "X-ray glasses" as an app for your phone. Um, great...
Agreed. But that's what you get with a single payer system that doesn't have the funds to treat everyone. You start to have to make decisions about who gets treated and who gets... what did our President say? A pain pill.
I don't think Windows RT devices exist because they are "priced less". I think they exist so that Microsoft can show that they are a player in the ARM space. As a product, it doesn't need to succeed, it merely needs to exist.
I agree, though, that the user base could do without them.
> If Microsoft called the devices and software layer WinTouch or something, that might have helped a little, as a lot of people have been disappointed that a "Windows" computer can't run legacy mouse/keyboard Windows apps.
IIRC that was true of Windows CE also, and cause considerable confusion back then. Everything old is new again etc etc.
I think that this is one more issue that stems with wanting to call everything "windows".
The problem is, like many Microsoft product names, "modern UI" is too generic to mean anything to the casual listener.
Thanks very much, I was powerful confused by earlier posts. So to paraphrase, WinRT is the run time API for what we call Metro, (on Intel and ARM) and Windows RT is that version of Windows (8, currently) that runs on ARM? Wow, no wonder people are confused.
> You can't deny coverage in a single-payer system.
Um, sure you can. Or, if not "coverage", then treatment.
Line the makers of Gardisil up on the firing line first. And if you feel strongly about protecting them you are more than welcome to stand in front of them to catch the bullets :)
I have to agree. I'm generally in favor of vaccines, (I had a bad case of chicken pox in my twenties -- I'm told I smelled like rotting meat -- daughter got the chicken pox vaccine) but drew the line at Gardisil. I think that was an illustration that you can't take either side of the argument completely at their word.
Which, come to think of it, is true for most arguments.
At least 26 deaths from Gardasil according to these guys
What, those guys? Call me when you have a credible source like... um, never mind.
I wonder how often something like this happens and we never hear about it, because the "second dash cam video" doesn't exist or never comes to light.
I dunno, I see it as a toaster meatloaf peeler combo. In an environment where your job required a meatloaf peeler (although you don't see the use) and what you personally really need is to toast some bread.
Ok, that sounded better in my head.
Well, you know.
Do you really believe in your heart of hearts that if a cop commits a crime during an altercation, that the video won't somehow get lost?
I wonder how cops will react to citizens having cameras on their persons during altercations with cops? In theory it should be exactly the same thing, but in practice, citizens trying to (legally) film cops during such interactions have not gone well for the citizen.
> i hear they were trying to start fires on board earlier by putting in bad batteries
Wrong plane.
I dunno, this sounds like a false choice to me. Whether Common Core is good or bad is debatable, and I'm sure there are a lot of people willing to debate you on that. Do the SATs need to be changed? Yes. I could agree with that. But this doesn't mean that the changes suggested are the best way to go about it, or even if the changes are better than what we have now.
Terabytes, right. The solution still stands.
A couple of things. First, do you really need to back up all 20 GB of data? How much of that can be recovered by other means? For instance, is it reasonable to back up the OS if you would probably just reinstall anyway? How much of your content did you acquire electronically? Would it be easier to go back to the source?
Thing two: If you really have to back up all 20 GB, the only really practical, cost-effective way to back up that much data is to another set of hard drives. Build up a second array, replicate, and then turn the backup array off. Leave it off except for periodic backups.
For incremental backups, dedicate one removable SATA slot. (I use one of those "hard drive toasters" that plug into a USB slot and allow you to hot-plug a SATA drive.) Plug in a drive on a regular schedule, and copy over the files that have changed recently. Mark it with a sharpie and put it in a safe place.
The idea is to (a) back up only what you couldn't easily recover through other means, (b) back up to the cheapest and fastest per byte, which is currently other hard disks, (c) keep your backup disks turned off when not in use, and (d) Figure out a schedule that suits you. For me, it was replicating the entire array only a couple times a year, supplementing with incremental backups to individual drives every week or so. Yes, you could still lose data, but not nearly as much as if you did nothing. Don't choose a solution so ambitious that you would later tire of it and stop doing it.
> Sorry, but you need better admins if they can't keep a BES up and running.
I don't dispute that.
> It's a crying shame that no one bought up BES and turned it into a device-agnostic activesync competitor.
Absolutely true.
I like how you're thinking.
Windows ce/mobile agree, but I carried a Palm OS phone for awhile, and it was ok. It ran all the apps from my Pilot and worked OK as a phone. Later I migrated to Blackberry and never looked back. All the capabilities that the Treo should have had and dead nuts reliable. If the offshore admins at my current company could figure out how to keep BES up, I'd still be on Blackberry. Current phone is Android (not Samsung, and I have no intention of marching lockstep with zombie-Jobs) so I guess I'll just get some popcorn and watch the carnage.
> Also, I find it laughable that so many republicans are concerned about 'welfare' and 'entitlement' yet happily sign on for farm subsidy bills that cost trillions, to keep the votes from fat-ass, lazy, uneducated, corn-fed, bigoted midwesterners rollin' right in.
I'm guessing you've never worked on a farm.
"But they all have smart phones". True, and that doesn't invalidate the XP type interface as superior on the desktop. Granted, phones and tablets are a growing market and desktop not so much, but Microsoft *owns* the desktop, and that would be a big enough market to make a nice living for some time, if they weren't so adamant about forcing a touch interface on it. It's natural for them to want to stretch into markets where they traditionally don't do so well, but they seem stubbornly trying to shoehorn one GUI into all environments. With Windows Mobile, that meant having an inappropriate interface in a market segment where they weren't doing well anyway, but with Windows 8, they're screwing with their base. It doesn't make any damned sense.
The difference here is that the Ukraine already knows what it's like to be under Russian rule. I could imagine that they'd be pretty desperate for that to not happen again.
I know what KVM means, thanks, but you weren't clear about what kind of machines you're using them on.
I'm in IT and I wouldn't have any problem with Classic Shell itself being on a Win8x computer. I use it myself, after all.
And neither would I, if I was forced to use Windows 8. (We as a company decided not to deploy 8. We will stick with 7 and revisit when 9 comes out. We also skipped Vista, incidentally.) The thing is, as an administrator, I don't get to make the rules. The architects don't even make the rules. They make recommendations to management, who then cross reference with legal and others before making the final decision. We (as a company) would not deploy a tool like Classic Shell for the same reason we would not run our business on CentOS. (Which is a fine build -- I use it for prototyping.) It's not a functional issue.
And at home... we had a laptop with touch screen that had been upgraded to 8.1 Pro (or whatever they call it). It was easier to reinstall 7 Pro (from "system recovery") than try to figure out all the absurdities in 8. So even there, we were not forced to use 8, so I again had no use for Classic Shell.