No kidding... even from the fanboy front, supporters can easily call out that this is just a natural progression of all the "switchers" out there.
After all, just because you buy a new computer (in this case a Mac), doesn't mean you simply toss out the old one. You give it to the kids, leave it loafing around the house for specific tasks you hadn't transferred to the Mac yet, keep it around for the occasional PC game you don;t want to get rid of, use it for backing up your Mac (e.g. you copy stuff from new laptop to the old desktop), etc.
...plus, I sincerely doubt that Apple gives a damn if users keep their old PC's around so long as they're buying new Macs.
...depends on where the dough went. If Intel gave/donated/whatever the gifts to the project (and not him), then what's to report?
It also depends on what the gifts actually were. Cash is highly fungible, but a shiny new O-scope capable of analyzing a chip (some of the HP-built models can run upwards of $250,000 USD or more, not counting the periodic calibration/maintenance fees) isn't exactly something you're gonna see flogged on eBay for ready cash.
The traditional mono- and polysilicon panel makers catch hell for using things like lead (leading to RoHS solder being used and etc)... what's the plan for recycling these puppies?
(don't get me wrong, I'm loving the idea, but you know someone's gonna bitch about it...)
Also, since there are places that see annual windstorms which tend to rip the occasional shingle off of the roof, err, how much would it cost to repair/replace?
It'll be hammered out eventually (err, s'cuse the pun), but it's something I hope that someone is thinking about all this today, instead of the being blinded by the whole 'gee-whiz' factor that may come around to bite the whole renewables movement in the butt later on.
(disclosure - I work IT in this industry - take it as you will).
The first part IIRC already exists somewhat (especially in Vista, which is why UAC was so damned annoying and usually gets shut off at first opportunity). If you were thinking of some other mechanism, I apologize (unless that mechanism involves some sort of local or remote database of 'approved' software to check against, which is a very bad idea).
The second part would be cool, but the Windows Registry, being a constantly evolving thing (and of piss-poor design) has data written to it by the OS constantly during runtime. All the malware has to do (and usually does once infection hits) is to mimic the perms of the system itself and happily write to whatever parts of the registry it wants, discreet user-locks be damned. The only thing a user-lock would accomplish is to prevent you, the user, from removing the malware-written registry bits.
IF the programmers of Apple OSX, Linux, and BSD can make mostly malware-free software, Microsoft can also.
Depends on how stable the codebase is, how much backwards-compatibility is needed, how much of a kludge the component code bits in question were in the first place, how modular the overall design is/was, etc.
Sure - Microsoft can do it, but judging from complaints by former Microsofties, and the leaked code from way back in Windows 2000 as a design guide of sorts? Well, on the same note I can, with the same probabilities, dig out Mount Everest and relocate it by using nothing more than a pick axe with a busted handle.
Those operating systems have fewer vulnerabilities because they were designed to be secure.
More importantly, they were designed to be modular in nature. This means that you can rip out and re-write parts of, say, the kernel, without worrying as much about borking the whole thing by doing so*, or inducing even worse problems elsewhere in it.
*assuming you don't do anything outright stupid, of course...
Even compared to the secondary education I received, things are very dumbed-down today - with existing curriculae preferring to push boutique ideologies instead of the actual history, science, and mathematics. Rhetoric, Civics, and Logic aren't even taught anymore in most high schools, and a second language (no, not ESL) is usually Spanish if you're lucky enough to even get that as an option.
The teachers' unions like to blame the class sizes (e.g. they're not hiring enough new union member- err, teachers), and everyone else finds it convenient to blame the budget (in spite of private schools doing far more with far smaller budgets).
Personally, and from experience? I blame the districts and state management offices. There are far too many support personnel than there are teachers in a school (my last teaching position was at a regional college that had 150+ employees and 38 actual faculty - not teachers, "faculty"). There's too much middle management, too many niche positions (no, not special-ed teachers, I mean the really damned niche positions, like "state licensing facilitator", "curriculum specialist" and similar). Most school district employee lists read more like a who's-who of political favor recipients than of employees who actually contribute something useful towards educating a student. Sure a teacher's salary is crap - because the millions of dollars aren't going to them - it's mostly going to that great big grey hole down at the district office (and to vendors at exorbitant rates... if you think software vendors are greed-driven in the enterprise IT realm, you ain't seen shit).
I highly doubt Google deletes your stuff when you remove it. I bet they keep it around till they have a chance to look it over. And there is no way to know if they ever get rid of your/their data.
That's true, and I can very easily concede that one. I honestly never thought about that aspect of it - it's would be impossible to tell. One the one hand, it's data to be mined. OTOH, it's eating disk space.
True, but a lot of this depends on how long you have it sitting out there. If you're just passing it through, and if you do it right, I doubt that Google would have any time to soak it all in, let alone do anything about it (unless you have a shitload of data or you're just that unlucky). I could be wrong though, but I get the feeling that I'm at least halfway correct in the assumption. Apply the usual 'taste test before cooking' rules here, etc.
It kinda goes without saying though that if you have your company's trade secrets sitting in SharePoint, especially a rig with an external/public face to it? Odds are good that you have bigger risks now, than the chance of Google reading the thing into their ad-cruncher on its way to something else.
Also, a question, and I promise that it is asked in earnest: Why on Earth would anyone park trade secrets onto a company CMS (esp. one that's so damned integrated)? You'd think that kind of info would be stashed off onto its own little isolated environment and kept walled-off...
Don't even start me of Infopath documents being put in there to pretend to give it a forms engine. Its hell.
Worse than hell, really... and not very secure. Our purchase req's at work use it, and I doubt the doc author would know what I was talking about if I asked her whether she sanitized her inputs or not (for example, I can give my own PR's authorization all the way to the VP of finance if I wanted to... and they rely on the damned thing now).
As for the rest? Dude, I'd give it every mod point I'd ever see for the next year if I could. I'm guessing it's your latter reason (too much diaspora, with little to hold it together) that explains why few people use it. A good web designer can overcome that very easily, but unfortunately? A good web designer and a good SharePoint developer are apparently almost never the same human being (hell, our SP "developer" gets lost in an Event Log... how am I supposed to help explain the basics of CSS to the guy?)
PS: The search function is pure hell to get working right, if at all. The consultant who put ours together actually knew what he was doing, and SP search still works only half-assed, so don't feel too badly about it.
...then again, the Titanic may have been built in Belfast, but it was owned by a joint UK/US consortium known as the International Merchant Marine (J.P. Morgan fronted the US half, and White Star Line the UK half).
Even better question: Will they ever bother selling it?
Microsoft has a nasty habit of fending off emerging threats by promising vaporware products that do the same job, only somehow better. In many of these cases, it's main job isn't to do $functionality, but distract attention and hype away from competitors (like, say, Apple's rumored tablet thingy), then the proposed product gets quietly buried once the hoopla is over.
It's a great way to suck the oxygen out of an emerging concept that threatens any sort of status quo... after all, Microsoft's profit margins got socked in the gut pretty hard by the whole netbook emergence.
...except that once you remove the "free" qualifier, suddenly Hyper-V sucks hind teat. Call me a troll all you like, but the fact remains: Hyper-V cannot hold up under enterprise conditions.
As someone who has 75% (and counting) of his servers at work virtualized, I much prefer working and usable HA functionality (among many, many other tools), thanks. Hyper-V has no such thing yet, and their limitations (e.g. 24 VM's max per server because they run out of drive letters after that - seriously, WTF?) tends to put a serious cramp in any enterprise VM farm design. And yes, for what I get with VI/ESX, I'm more than willing to continue submitting PR's for the licenses, and given the savings and DR features (including Site Recovery Manager), my management is more than happy to sign those PR's.
Sure for free, you get some basic stuff that works a bit better for the workstation user than VMWare's free stuff gives you. But on the server side? This is going to sound a touch like the old IBM FUD, but in this case it is perfectly true: Hyper-V puts you one downtime incident away from the unemployment line (two if you have really good managers).
Over time this may change, but as of right now, no way... Hyper-V has a LOT more maturing that needs done before it can be considered useful in an enterprise environment.
...with your eyes, your ears, and your time. Nothing evil or good about that per se - it's just a question of what you're willing to put up with to get something that's "free". (Incidentally, if your'e required to have a Zune sub to get at those free games, isn't that like $14/month or so?).
Peddle your skills as a living professor of history. It'll take your lifetime and somebody else's to elaborate on all the aspects of the life and culture you knew (unless you're a.NET developer - then it's like five minutes plus a lifetime of everyone asking you, like, WTF?)
If FTL travel is hopping and happy, then trade your big ol' museum piece in for a flashy new FTL ship, and go find a new empty rock to call home.
Get a whole new education. It's not like you're suddenly incapable of learning.
Help restore lost technology/arts/sciences/etc. Hell, there was a ~1,000 year or so stretch of time between the last use of concrete by the Romans and our rediscovery of it. It took thousands of years to re-learn how a primitive copper-age society (for lack of better term) like the ancient Egyptians managed to pull off some of their biggest stunts... and even today, we're still guessing on a good chunk of it.
Buy a sex-bot or two while you're there... may as well.
Okay, note that most of those up there are only half-joking, but all of them (except maybe the last) are based on serious premises. Thing is, not going for fear that someone else beats you to the goal is kinda dumb, and it certainly didn't stop the folks heading for the gold rushes of the 19th century. When they arrived and found all the good claims taken, they just found some other way to get by (or they moved on), and along the way managed to create a whole new life for themselves and their kids.
Yes, the data is highest in importance, etc. However, the data does not an entire server make, and getting that data back up and spinning ASAP is even more important.
Yes, the site getting popped for any reason still sucks. However, there's still the question as to how big of a crater gets left behind, to use an abstraction.
Pull the zoom back a bit and look at the larger picture. If the data gets corrupted, most-to-almost-all of it (depending on how you built things) can be restored and recovered. If you built the server right initially, you probably won't even lose anything really valuable (e.g. customer data) to those who penetrate the thing.
However, from this pulled-back view, the question still remains - how bad did it get?
If it's just in the chroot jail, then the person penetrating got no further, and you have a little cleaning up to do w/ very little downtime.
If the OS is compromised, then odds are good that the entire box needs to be flushed.
Worse still, if we're talking more than one box and the OS gets compromised, then you'd better start sniffing the rest of your DMZ (or worse) for signs of penetration.
I don't know about you, but I would much prefer to clean up after a pipe bomb blast than to clean up after a thermonuclear detonation.
...depends on how a police officer could catch on.
Think about this one for a second - (we'll even pick an Oregon example): I-5 between Portland and Salem, just after morning rush hour, but with hundreds of cars entering and exiting every minute or so at ~45-70mph (the speed limit is 65).
Now if I hacked the RFID tag, the only way he's gonna know is...
...if some automated camera system is out there eyeballing my license plate and doing instantaneous checks of plate vs. RFID readout, for that car, at that precise moment in time. This of course is assuming that the state highway patrol (there is no federal one) will even bother with it, since they already have enough to do in a given day.
Oh, and unless the feds want to miss out on a metric ton of tax money, they're going to have to implement this system pretty much at every entrance or exit ramp, to every Interstate highway. That's 50,000+ miles of road, and a near astronomical number of ramps.
Slashdot Mirror
...and you are sooo gonna burn in hell for that one (and, err, so will I for laughing my ass off at it).
Good show!
If you need a Mac to do that, err, you may want to look for a better class of women and friends to impress. :/
No kidding... even from the fanboy front, supporters can easily call out that this is just a natural progression of all the "switchers" out there.
After all, just because you buy a new computer (in this case a Mac), doesn't mean you simply toss out the old one. You give it to the kids, leave it loafing around the house for specific tasks you hadn't transferred to the Mac yet, keep it around for the occasional PC game you don;t want to get rid of, use it for backing up your Mac (e.g. you copy stuff from new laptop to the old desktop), etc.
...depends on where the dough went. If Intel gave/donated/whatever the gifts to the project (and not him), then what's to report?
It also depends on what the gifts actually were. Cash is highly fungible, but a shiny new O-scope capable of analyzing a chip (some of the HP-built models can run upwards of $250,000 USD or more, not counting the periodic calibration/maintenance fees) isn't exactly something you're gonna see flogged on eBay for ready cash.
The traditional mono- and polysilicon panel makers catch hell for using things like lead (leading to RoHS solder being used and etc)... what's the plan for recycling these puppies?
(don't get me wrong, I'm loving the idea, but you know someone's gonna bitch about it...)
Also, since there are places that see annual windstorms which tend to rip the occasional shingle off of the roof, err, how much would it cost to repair/replace?
It'll be hammered out eventually (err, s'cuse the pun), but it's something I hope that someone is thinking about all this today, instead of the being blinded by the whole 'gee-whiz' factor that may come around to bite the whole renewables movement in the butt later on.
(disclosure - I work IT in this industry - take it as you will).
The first part IIRC already exists somewhat (especially in Vista, which is why UAC was so damned annoying and usually gets shut off at first opportunity). If you were thinking of some other mechanism, I apologize (unless that mechanism involves some sort of local or remote database of 'approved' software to check against, which is a very bad idea).
The second part would be cool, but the Windows Registry, being a constantly evolving thing (and of piss-poor design) has data written to it by the OS constantly during runtime. All the malware has to do (and usually does once infection hits) is to mimic the perms of the system itself and happily write to whatever parts of the registry it wants, discreet user-locks be damned. The only thing a user-lock would accomplish is to prevent you, the user, from removing the malware-written registry bits.
IF the programmers of Apple OSX, Linux, and BSD can make mostly malware-free software, Microsoft can also.
Depends on how stable the codebase is, how much backwards-compatibility is needed, how much of a kludge the component code bits in question were in the first place, how modular the overall design is/was, etc.
Sure - Microsoft can do it, but judging from complaints by former Microsofties, and the leaked code from way back in Windows 2000 as a design guide of sorts? Well, on the same note I can, with the same probabilities, dig out Mount Everest and relocate it by using nothing more than a pick axe with a busted handle.
Those operating systems have fewer vulnerabilities because they were designed to be secure.
More importantly, they were designed to be modular in nature. This means that you can rip out and re-write parts of, say, the kernel, without worrying as much about borking the whole thing by doing so*, or inducing even worse problems elsewhere in it.
*assuming you don't do anything outright stupid, of course...
Even compared to the secondary education I received, things are very dumbed-down today - with existing curriculae preferring to push boutique ideologies instead of the actual history, science, and mathematics. Rhetoric, Civics, and Logic aren't even taught anymore in most high schools, and a second language (no, not ESL) is usually Spanish if you're lucky enough to even get that as an option.
The teachers' unions like to blame the class sizes (e.g. they're not hiring enough new union member- err, teachers), and everyone else finds it convenient to blame the budget (in spite of private schools doing far more with far smaller budgets).
Personally, and from experience? I blame the districts and state management offices. There are far too many support personnel than there are teachers in a school (my last teaching position was at a regional college that had 150+ employees and 38 actual faculty - not teachers, "faculty"). There's too much middle management, too many niche positions (no, not special-ed teachers, I mean the really damned niche positions, like "state licensing facilitator", "curriculum specialist" and similar). Most school district employee lists read more like a who's-who of political favor recipients than of employees who actually contribute something useful towards educating a student. Sure a teacher's salary is crap - because the millions of dollars aren't going to them - it's mostly going to that great big grey hole down at the district office (and to vendors at exorbitant rates... if you think software vendors are greed-driven in the enterprise IT realm, you ain't seen shit).
I highly doubt Google deletes your stuff when you remove it. I bet they keep it around till they have a chance to look it over. And there is no way to know if they ever get rid of your/their data.
That's true, and I can very easily concede that one. I honestly never thought about that aspect of it - it's would be impossible to tell. One the one hand, it's data to be mined. OTOH, it's eating disk space.
Cheers!
True, but a lot of this depends on how long you have it sitting out there. If you're just passing it through, and if you do it right, I doubt that Google would have any time to soak it all in, let alone do anything about it (unless you have a shitload of data or you're just that unlucky). I could be wrong though, but I get the feeling that I'm at least halfway correct in the assumption. Apply the usual 'taste test before cooking' rules here, etc.
It kinda goes without saying though that if you have your company's trade secrets sitting in SharePoint, especially a rig with an external/public face to it? Odds are good that you have bigger risks now, than the chance of Google reading the thing into their ad-cruncher on its way to something else.
Also, a question, and I promise that it is asked in earnest: Why on Earth would anyone park trade secrets onto a company CMS (esp. one that's so damned integrated)? You'd think that kind of info would be stashed off onto its own little isolated environment and kept walled-off...
IIRC, the license key was nearly a universal one for the longest time...
(not advocating anyone actually putting that info to nefarious use or anything - just sayin' is all...)
Don't even start me of Infopath documents being put in there to pretend to give it a forms engine. Its hell.
Worse than hell, really... and not very secure. Our purchase req's at work use it, and I doubt the doc author would know what I was talking about if I asked her whether she sanitized her inputs or not (for example, I can give my own PR's authorization all the way to the VP of finance if I wanted to... and they rely on the damned thing now).
As for the rest? Dude, I'd give it every mod point I'd ever see for the next year if I could. I'm guessing it's your latter reason (too much diaspora, with little to hold it together) that explains why few people use it. A good web designer can overcome that very easily, but unfortunately? A good web designer and a good SharePoint developer are apparently almost never the same human being (hell, our SP "developer" gets lost in an Event Log... how am I supposed to help explain the basics of CSS to the guy?)
PS: The search function is pure hell to get working right, if at all. The consultant who put ours together actually knew what he was doing, and SP search still works only half-assed, so don't feel too badly about it.
Not really... at least once you shake it out into Google, you can then move it one more hop into something usable and open.
Google's API is merely the means, not the end.
...I bet neither of them had to wait out a nine-month-long compile...
...same empire ;)
...what's the ACID3 results for such a combo?
Their biggest competitor is BT ... Not quite seeing a stampede happening in that direction.
There's always Orange, I guess...
(...and to think that I bitch about Comcast...)
Even better question: Will they ever bother selling it?
Microsoft has a nasty habit of fending off emerging threats by promising vaporware products that do the same job, only somehow better. In many of these cases, it's main job isn't to do $functionality, but distract attention and hype away from competitors (like, say, Apple's rumored tablet thingy), then the proposed product gets quietly buried once the hoopla is over.
It's a great way to suck the oxygen out of an emerging concept that threatens any sort of status quo... after all, Microsoft's profit margins got socked in the gut pretty hard by the whole netbook emergence.
...except that once you remove the "free" qualifier, suddenly Hyper-V sucks hind teat. Call me a troll all you like, but the fact remains: Hyper-V cannot hold up under enterprise conditions.
As someone who has 75% (and counting) of his servers at work virtualized, I much prefer working and usable HA functionality (among many, many other tools), thanks. Hyper-V has no such thing yet, and their limitations (e.g. 24 VM's max per server because they run out of drive letters after that - seriously, WTF?) tends to put a serious cramp in any enterprise VM farm design. And yes, for what I get with VI/ESX, I'm more than willing to continue submitting PR's for the licenses, and given the savings and DR features (including Site Recovery Manager), my management is more than happy to sign those PR's.
Sure for free, you get some basic stuff that works a bit better for the workstation user than VMWare's free stuff gives you. But on the server side? This is going to sound a touch like the old IBM FUD, but in this case it is perfectly true: Hyper-V puts you one downtime incident away from the unemployment line (two if you have really good managers).
Over time this may change, but as of right now, no way... Hyper-V has a LOT more maturing that needs done before it can be considered useful in an enterprise environment.
Define "reasonable" - reasonable according to the end-user (okay, somewhat geeky end-user), or "reasonable" to Comcast, Verizon, AT&T...
You pay for a zune, then pay...
(Slashdot had a dupe problem too).
Okay, note that most of those up there are only half-joking, but all of them (except maybe the last) are based on serious premises. Thing is, not going for fear that someone else beats you to the goal is kinda dumb, and it certainly didn't stop the folks heading for the gold rushes of the 19th century. When they arrived and found all the good claims taken, they just found some other way to get by (or they moved on), and along the way managed to create a whole new life for themselves and their kids.
Yes, the data is highest in importance, etc. However, the data does not an entire server make, and getting that data back up and spinning ASAP is even more important.
Yes, the site getting popped for any reason still sucks. However, there's still the question as to how big of a crater gets left behind, to use an abstraction.
Pull the zoom back a bit and look at the larger picture. If the data gets corrupted, most-to-almost-all of it (depending on how you built things) can be restored and recovered. If you built the server right initially, you probably won't even lose anything really valuable (e.g. customer data) to those who penetrate the thing.
However, from this pulled-back view, the question still remains - how bad did it get?
I don't know about you, but I would much prefer to clean up after a pipe bomb blast than to clean up after a thermonuclear detonation.
...depends on how a police officer could catch on.
Think about this one for a second - (we'll even pick an Oregon example): I-5 between Portland and Salem, just after morning rush hour, but with hundreds of cars entering and exiting every minute or so at ~45-70mph (the speed limit is 65).
Now if I hacked the RFID tag, the only way he's gonna know is...
Oh, and unless the feds want to miss out on a metric ton of tax money, they're going to have to implement this system pretty much at every entrance or exit ramp, to every Interstate highway. That's 50,000+ miles of road, and a near astronomical number of ramps.