I think you're missing the point - a large amount of the functionality of IE was moved into system DLLs, to make IE part of the OS proper during MS's claims that you couldn't remove IE.
Due to the incredible genius and well-disciplined engineering that comprises MS, that functionality became interdependent with other functionality that is part of the OS. So, in a way, MS was right, IE cannot be fully removed from the OS anymore without seriously reworking pieces of their architecture.
The rest of the post describes why this is a major problem due to MS's architecturally flawed security.
Unfortunately for you and MS, the core DLLs at the root of many of "IE"'s vulnerabilities are actually "core" pieces of the OS and can and are, in fact, exercised by other applications as well. "Uninstalling" IE, or never installing it, still results in an OS with these DLLs in place.
So yes, IE vulnerabilities ARE part of the MS OS vulnerabilities, but trust me, these are the least of MS's problems. The core issue is that the OS was "designed", if you could call it that, by the equivalent of 8th graders from a security stand point, and that might be unfairly insulting 8th graders. The OS is completely backwards in its outlook on security compared to any modern in use OS. It runs on a highest privileged token, which is "masked" or "filtered" in an effort to give "least privileges". You then "elevate" yourself by removing these privileges. Why is this a problem? If you need to do anything important, like, say, change passwords of users, then your process must run with that privilege all the time. So any flaw anywhere can be exploited to expose that privilege. In the newest version of 2008 R2 most of the token manipulation routines have been "broken" regarding any meaningful elevation, thus forcing this wrong-headed approach down your throat. Unless, of course, you don't mind injecting code into some random DLL that runs as "SYSTEM" somewhere.
Compare that with *nix for example, where your process runs with no privileges, so a flaw has no privileges when exploited... and you can see why security people that actually know anything RUN from an MS installation.
The First Sale Doctrine covers the actual work. And in the case of photos/prints, I don't know how they could retain copyright to anything other than their own creations. Someone else can photograph an object and they're good to go. Now if they sculpted or painted something, and didn't sell it and hid it from the world or destroyed it and sold prints/video of them, then they'd retain all rights, as they'd be the sole copyright holders.
He didn't say they were all wrong, he said they had "upheld all manner of blatantly unconstitutional law". They could also have upheld constitutional laws and invalidated unconstitutional laws.
And do note that you have to make a valid argument in front of the court to get something invalidated. You can't just file a "This law is unjust! Unjust I tell you. UNCONSTITUTIONAL!!!!" and expect them to throw it out.
TQ's demo crashed my entire computer on exit, which meant I didn't even attempt to buy it until Steam offered it and expansion for $10. I assume they'd worked out the bugs by then.
No problemo! Just reimage your winblows game only drive using your linux partition, like you did before you installed this game.
at this point, I purposely break IE6 by including certain 3rd party libraries that are standards complaint yet don't work in IE6. I have that little notice that this site may not work properly in IE 6, along with a link to Firefox and Safari.
I suggest you check your websites on firefox 2.xx. I was at a business this morning that still runs Windows 98 and firefox 2.xx. Their core application won't run on XP, OSX or Linux....There are people out there who can't change for good reasons.
No, there are people out there who drank the coolaid and built systems on alpha software and refuse to change. That's different than cannot change like a leopard can't change its spots, but it can certainly decide to eat the rabbit over the snake.
It's obvious - every camcorder made since day 1, or at least longer than 20 years ago, had an electronic "pre" viewfinder, because the optical viewfinder generally gave you no idea as to what was going on film.
As for TV, the quality of programming has gone downhill,
naah, TV sucked long ago, you just didn't know any better. just watch some reruns of the A-Team or the Love Boat, or worse yet, Charlies Angels or Mcgyver and you'll get the picture.
I will give you this - "Reality TV" has seriously delved to new lows in "programming", although you can argue it's "no programming" at all.
Windows 7 is Vista, release 1.0. They decided to partially switch it off for you.
It still doesn't solve the core problems with the (lack of) security architecture. It's still swiss cheese, they've just added enough layers to hide the holes somewhat.
... So if a given file was created using an old version of Word that includes implicit vulnerabilities, for example, Word 2010 will open it in read-only mode with macros disabled, while giving the user a button to activate the disabled features (with an "it's your funeral" warning message)
You've merrily drunk the MS coolaid. The idea that a server is only good for 1 task sells... more hardware and software!
We happily run a DB, mail server, web application server and more on a single decently sized box.
(Yes, there are situations where you need to separate functions due to pure load optimization/performance requirements, but Exchange doesn't meet those criteria as in most cases the server is sitting idle except when a mail virus comes along, in which case they fall over)
>>>Don't upgrade if you don't think it's worth it!
You can't do that with Macs. They'll stop running the latest software. For example I wouldn't be able to run Firefox 3 or 3.5 on my G4 Mac's original OS (10.1). I had to upgrade.
I'd like to run Office 2008 on WinME... wait, I can't. Not in Win2K either. Oh no!!!! How about that DX10 game on XP? Nope, can't do that either.... Gosh darn it!
FYI - there were major changes in OS APIs between 10.1-10.6. Something designed for 10.6 won't run on 10.3 or before. A little thing about binary compatibility due to physical architecture and system API support.
(RE CVS/VSS)...Implying that either of these is more reliable than git is a claim that really needs some backing up
I made no such claim. I did imply that both them and MKS are completely unusable due to lack of atomic operations and other issues.
Clearcase... actually sort of works... normal usage is a pain
Yes, CC is an absolute pain to use for those new to it. It can take an easy 6-12 months just to get up to adequate speed with it, if you're using a slightly more complicated system. It also requires a real administrator to operate even remotely decently.
multi-site support is a joke
Apparently someone forgot to tell us this as we worked in 5 sites across the globe. Maybe you needed a better administrator? (Yes, ours was paid more than all but the top developers)
Now to your comments:You say that none of the new SCMs do what you want. Fine, but that does not mean that there is no innovation in the field...
After re-reading my comments, I suppose I wasn't clear enough: There is no widely supported, easy to use and maintain form of SCM currently available.
Hopefully we can agree on that. Git, your apparent favorite, is nowhere near mainstream.
Still, some comments: Training is a given, but I assume you didn't expect innovation without any changes.
True innovation would be a painless SCM. The changes I'd expect would include less work and training, not more.
Reliability: suggesting that git is unreliable and implying CVS and VSS are, is just totally absurd in my opinion.
You said this, not I. I gave CVS, VSS, and MKS as examples of unreliable SCMs. VSS at best should be considered a tool of sabotage. Oh yes, 4 posts up the hierarchy, I said exactly that.
...If my employer told me to work with CVS, I'd probably start looking for a new job. Not because working with CVS is impossible but because it's just a really, really bad sign if an employer doesn't give a skilled worker the best tools available...
That's interesting. So what are the best tools available? Seriously. Just state it so we all know and can go home now. I merely stated my dissatisfaction with the current state of SCMs.
I'm still looking. Name me something that can be used today for my particular needs and I'd be happy to look at it. That would be more useful instead of just engaging in weak insults.
Git does not fit my needs. Cost is a constraint. Not just cost of the software itself, but implementation, configuration, management, training, and maintenance. Most of those should be low with little time impacts on most of our developers. And then there are the functional requirements: reliability... heck, if it's not reliable (StarTeam, CVS, MKS, and VSS especially) it's just a wanna be.
So step up and offer a solution that meets these needs and I'll be happy to try it out. Otherwise, my statement stands that there is no innovation worth speaking of in the SCM field. I'm not interested in school or niche projects that will never see commercial use. I wouldn't bet my company on such an item, and neither will anyone else with a smidgen of intelligence and common sense.
When you get used to the workflow you'll wonder how people ever used svn.
No they won't - SVN pretty much sucks all around. There'll be no wonder if Git's actually better. I've considered looking over Bazaar and AccuRev, but the latter costs too much, and I ran out of time for the former.
There's not an SCM system made that doesn't suck that I'm aware of. Having said that, I've not used Perforce nor Git. Git has no real integration with my IDEs of choice, and Perforce I only have second hand info on, but former co-workers that have converted to it seem to not be sold on it either. I have considered writing my own, just lack the 8 solid months and desire to do such a thankless task.
I have had the pleasure of using, in no particular order: StarTeam, SVN, CVS, MKS, and ClearCase. SVN was by far the easiest to use while actually performing basic SCM functions adequately. ClearCase was the best at dealing with branches. They all suck, however, and are only used because there's a lack of anything better at an acceptable price, or even unacceptable price (ClearCase and Perforce are certainly at the top end).
VSS is bar far the worst and should be considered a tool of sabotage at best. CVS and MKS both share the inability to do atomic transactions. Nothing, and I mean nothing, will ruin your day like a file that's listed as checked in, logged as checked, but was never actually commited to the repository...
And as far as branching goes, the only one that's even in the ballpark is ClearCase.
Picking an SCM system is more about picking your least pain than picking something that actually helps your process. There has been no innovation to speak of in the last ten years, or 20 years, for that matter as most of these systems cores date back 20 years.
Yes, Semis are the biggest road problem. That "This truck pays 10K a year in road taxes" is a laugh, they should be paying at least 100K / year for the damage they do. 1 truck does as much damage as 100K cars for a given section of highway according to an old study I read way back when I had to do such things.
It's easy, raise taxes on fuel, and watch trains revive. Also watch pickups, SUVs, and other gas guzzlers disappear from daily commuters and roadway traffic congestion ease.
Unfortunately, it will also damage our economy. So what to do? The only answer I can think of is to equally subsidize trains, make them competitive, and then slowly raise the taxes to lower the subsidies.
Slashdot Mirror
I think you're missing the point - a large amount of the functionality of IE was moved into system DLLs, to make IE part of the OS proper during MS's claims that you couldn't remove IE.
Due to the incredible genius and well-disciplined engineering that comprises MS, that functionality became interdependent with other functionality that is part of the OS. So, in a way, MS was right, IE cannot be fully removed from the OS anymore without seriously reworking pieces of their architecture.
The rest of the post describes why this is a major problem due to MS's architecturally flawed security.
Unfortunately for you and MS, the core DLLs at the root of many of "IE"'s vulnerabilities are actually "core" pieces of the OS and can and are, in fact, exercised by other applications as well. "Uninstalling" IE, or never installing it, still results in an OS with these DLLs in place.
So yes, IE vulnerabilities ARE part of the MS OS vulnerabilities, but trust me, these are the least of MS's problems. The core issue is that the OS was "designed", if you could call it that, by the equivalent of 8th graders from a security stand point, and that might be unfairly insulting 8th graders. The OS is completely backwards in its outlook on security compared to any modern in use OS. It runs on a highest privileged token, which is "masked" or "filtered" in an effort to give "least privileges". You then "elevate" yourself by removing these privileges. Why is this a problem? If you need to do anything important, like, say, change passwords of users, then your process must run with that privilege all the time. So any flaw anywhere can be exploited to expose that privilege. In the newest version of 2008 R2 most of the token manipulation routines have been "broken" regarding any meaningful elevation, thus forcing this wrong-headed approach down your throat. Unless, of course, you don't mind injecting code into some random DLL that runs as "SYSTEM" somewhere.
Compare that with *nix for example, where your process runs with no privileges, so a flaw has no privileges when exploited... and you can see why security people that actually know anything RUN from an MS installation.
The First Sale Doctrine covers the actual work. And in the case of photos/prints, I don't know how they could retain copyright to anything other than their own creations. Someone else can photograph an object and they're good to go. Now if they sculpted or painted something, and didn't sell it and hid it from the world or destroyed it and sold prints/video of them, then they'd retain all rights, as they'd be the sole copyright holders.
He didn't say they were all wrong, he said they had "upheld all manner of blatantly unconstitutional law". They could also have upheld constitutional laws and invalidated unconstitutional laws.
And do note that you have to make a valid argument in front of the court to get something invalidated. You can't just file a "This law is unjust! Unjust I tell you. UNCONSTITUTIONAL!!!!" and expect them to throw it out.
TQ's demo crashed my entire computer on exit, which meant I didn't even attempt to buy it until Steam offered it and expansion for $10. I assume they'd worked out the bugs by then.
No problemo! Just reimage your winblows game only drive using your linux partition, like you did before you installed this game.
at this point, I purposely break IE6 by including certain 3rd party libraries that are standards complaint yet don't work in IE6. I have that little notice that this site may not work properly in IE 6, along with a link to Firefox and Safari.
I suggest you check your websites on firefox 2.xx. I was at a business this morning that still runs Windows 98 and firefox 2.xx. Their core application won't run on XP, OSX or Linux....There are people out there who can't change for good reasons.
No, there are people out there who drank the coolaid and built systems on alpha software and refuse to change. That's different than cannot change like a leopard can't change its spots, but it can certainly decide to eat the rabbit over the snake.
It's obvious - every camcorder made since day 1, or at least longer than 20 years ago, had an electronic "pre" viewfinder, because the optical viewfinder generally gave you no idea as to what was going on film.
Heck, that's the "not so open source model"! Build crap and give it away for free, then charge out the wazoo for "support".
Well, it's a good business model anyways. :)
As for TV, the quality of programming has gone downhill,
naah, TV sucked long ago, you just didn't know any better. just watch some reruns of the A-Team or the Love Boat, or worse yet, Charlies Angels or Mcgyver and you'll get the picture.
I will give you this - "Reality TV" has seriously delved to new lows in "programming", although you can argue it's "no programming" at all.
Windows 7 is Vista, release 1.0. They decided to partially switch it off for you.
It still doesn't solve the core problems with the (lack of) security architecture. It's still swiss cheese, they've just added enough layers to hide the holes somewhat.
... So if a given file was created using an old version of Word that includes implicit vulnerabilities, for example, Word 2010 will open it in read-only mode with macros disabled, while giving the user a button to activate the disabled features (with an "it's your funeral" warning message)
Ahhh good - UAC all over again....
You've merrily drunk the MS coolaid. The idea that a server is only good for 1 task sells... more hardware and software!
We happily run a DB, mail server, web application server and more on a single decently sized box.
(Yes, there are situations where you need to separate functions due to pure load optimization/performance requirements, but Exchange doesn't meet those criteria as in most cases the server is sitting idle except when a mail virus comes along, in which case they fall over)
There are people who can write code 16 hours a day for 4+ weeks straight. They're in that mythical 1/10th of 1% group.
Then there's the 95% who barely qualify as data entry clerks, but call themselves programmers.
Damn - no karma.
Somehow the "solo" bit was missed by the GP.
What do you need that extra speed for?
less time wasted staring at an hourglass cursor, of course..
hourglass? Perhaps that's the problem?
>>>Don't upgrade if you don't think it's worth it!
You can't do that with Macs. They'll stop running the latest software. For example I wouldn't be able to run Firefox 3 or 3.5 on my G4 Mac's original OS (10.1). I had to upgrade.
I'd like to run Office 2008 on WinME... wait, I can't. Not in Win2K either. Oh no!!!! How about that DX10 game on XP? Nope, can't do that either.... Gosh darn it!
FYI - there were major changes in OS APIs between 10.1-10.6. Something designed for 10.6 won't run on 10.3 or before. A little thing about binary compatibility due to physical architecture and system API support.
(RE CVS/VSS)...Implying that either of these is more reliable than git is a claim that really needs some backing up
I made no such claim. I did imply that both them and MKS are completely unusable due to lack of atomic operations and other issues.
Clearcase ... actually sort of works ... normal usage is a pain
Yes, CC is an absolute pain to use for those new to it. It can take an easy 6-12 months just to get up to adequate speed with it, if you're using a slightly more complicated system. It also requires a real administrator to operate even remotely decently.
multi-site support is a joke
Apparently someone forgot to tell us this as we worked in 5 sites across the globe. Maybe you needed a better administrator? (Yes, ours was paid more than all but the top developers)
Now to your comments:You say that none of the new SCMs do what you want. Fine, but that does not mean that there is no innovation in the field...
After re-reading my comments, I suppose I wasn't clear enough: There is no widely supported, easy to use and maintain form of SCM currently available.
Hopefully we can agree on that. Git, your apparent favorite, is nowhere near mainstream.
Still, some comments: Training is a given, but I assume you didn't expect innovation without any changes.
True innovation would be a painless SCM. The changes I'd expect would include less work and training, not more.
Reliability: suggesting that git is unreliable and implying CVS and VSS are, is just totally absurd in my opinion.
You said this, not I. I gave CVS, VSS, and MKS as examples of unreliable SCMs. VSS at best should be considered a tool of sabotage. Oh yes, 4 posts up the hierarchy, I said exactly that.
...If my employer told me to work with CVS, I'd probably start looking for a new job. Not because working with CVS is impossible but because it's just a really, really bad sign if an employer doesn't give a skilled worker the best tools available...
That's interesting. So what are the best tools available? Seriously. Just state it so we all know and can go home now. I merely stated my dissatisfaction with the current state of SCMs.
I'm still looking. Name me something that can be used today for my particular needs and I'd be happy to look at it. That would be more useful instead of just engaging in weak insults.
Git does not fit my needs. Cost is a constraint. Not just cost of the software itself, but implementation, configuration, management, training, and maintenance. Most of those should be low with little time impacts on most of our developers. And then there are the functional requirements: reliability... heck, if it's not reliable (StarTeam, CVS, MKS, and VSS especially) it's just a wanna be.
So step up and offer a solution that meets these needs and I'll be happy to try it out. Otherwise, my statement stands that there is no innovation worth speaking of in the SCM field. I'm not interested in school or niche projects that will never see commercial use. I wouldn't bet my company on such an item, and neither will anyone else with a smidgen of intelligence and common sense.
Remember: SCM is merely a tool, not an end.
>
Self-destructive argumentation, on the other hand, is progressing faster than ever!
as are vapid empty statements!
Most times it is: Violence is the last resort of the incompetent.
I think it's violence is the first (or maybe second) resort of the incompetent.
When you get used to the workflow you'll wonder how people ever used svn.
No they won't - SVN pretty much sucks all around. There'll be no wonder if Git's actually better. I've considered looking over Bazaar and AccuRev, but the latter costs too much, and I ran out of time for the former.
There's not an SCM system made that doesn't suck that I'm aware of. Having said that, I've not used Perforce nor Git. Git has no real integration with my IDEs of choice, and Perforce I only have second hand info on, but former co-workers that have converted to it seem to not be sold on it either. I have considered writing my own, just lack the 8 solid months and desire to do such a thankless task.
I have had the pleasure of using, in no particular order: StarTeam, SVN, CVS, MKS, and ClearCase. SVN was by far the easiest to use while actually performing basic SCM functions adequately. ClearCase was the best at dealing with branches. They all suck, however, and are only used because there's a lack of anything better at an acceptable price, or even unacceptable price (ClearCase and Perforce are certainly at the top end).
VSS is bar far the worst and should be considered a tool of sabotage at best. CVS and MKS both share the inability to do atomic transactions. Nothing, and I mean nothing, will ruin your day like a file that's listed as checked in, logged as checked, but was never actually commited to the repository...
And as far as branching goes, the only one that's even in the ballpark is ClearCase.
Picking an SCM system is more about picking your least pain than picking something that actually helps your process. There has been no innovation to speak of in the last ten years, or 20 years, for that matter as most of these systems cores date back 20 years.
Yes, Semis are the biggest road problem. That "This truck pays 10K a year in road taxes" is a laugh, they should be paying at least 100K / year for the damage they do. 1 truck does as much damage as 100K cars for a given section of highway according to an old study I read way back when I had to do such things.
It's easy, raise taxes on fuel, and watch trains revive. Also watch pickups, SUVs, and other gas guzzlers disappear from daily commuters and roadway traffic congestion ease.
Unfortunately, it will also damage our economy. So what to do? The only answer I can think of is to equally subsidize trains, make them competitive, and then slowly raise the taxes to lower the subsidies.
funny, my apache always runs as... apache...
Because why would I not fully control what my service(s) can access?