There's a difference between people believing MS's drivers to be involved, and them actually being involved. Even assuming that they *are* involved, though, that doesn't mean that OS X's drivers won't exhibit exactly the same behaviour.
The most likely thing at the moment appears to be that MacBook systems won't be affected, but it'd still be nice to have some confirmation on that.
They already seem to be doing more instant rebates anyway. The final price is usually a bit higher than with the mail-in rebate though.
Of course it is - more people actually get the rebate, thus the average price of the time goes down, thus they have to make the saving smaller to make the same amount of money.
That's all well and good, and forms part of a valid method of protest. However, in that case, you must be prepared to accept the consequences of your actions - protesting a law like that means being prepared to go to jail, protesting all the way that the law is wrong.
Oh well: The operative system may forbid to take screenshots of the windows that has DRM content (like mac os x does with DRm'ed videos I've been told). You may get your digital camera or even a vigilance camera could do it (you don't need to be 007 to do that).
Well, pretty much any company that implemented a DRM-protection scheme for its documents is going to be banning cameras in the work place anyway.
Besides which, you miss the point. The point is not to stop a malicious employee from purposefully leaking documents, it's to stop a (clueless) employee from *accidentally* leaking documents - eg emailing them to the wrong person, losing a USB key with them on, etc. That it makes malicious distribution harder is a bonus, not the main aim.
It's also a really sucky interface. I can remember using an app that once trapped certain keypresses for its own purposes (OK, it wasn't Java). Never ever again.
Konfabulator is one that springs instantly to mind; ICQ is another. Both trapped key presses that were meaningful to my choice of IDE at the time (JBuilder when I was using ICQ, Eclipse when I was using Konfabulator). Very annoying, until I found the config option to disable or change the trapped keys.
I can't comment on the US stock market, but here in the UK I have been in a company meeting at which the MD explained that one of the reasons why we were hiring contractors like crazy rather than permanent staff was because one of the main stock market measures was profit/(number of permanent employees). So, employ contractors rather than permies, that ratio goes up and the market likes you more...
Never mind that contractors cost more, leave sooner taking knowledge out of the company, etc, so your actual expenses are higher - that ratio's lower, so you *must* be doing better!
It isn't about tax evasion or good faith. It's a way to link productivity to company success.
No, this is about paying less tax on their salaries, thus lowering the overal wage bill and so increasing the overall worth of the company. It really is that simple; it may not be tax evasion (it's probably only tax avoidance), but it's nothing to do with tying productivity to company success.
By my count, less than 50MB is the Firefox heap, stack, and Firefox-specific shared libraries.
Well, that's nice, but I regularly see FF's RAM usage go over the 150-200meg mark after a few hours of what I consider light usage. It's not all system libs...
There's no technically about it; #3 is just a special case of #1, assuming you're thinking of the "run as" service.
Re:How can something publicly available be "leaked
on
IE7 Leaked
·
· Score: 1
Last I checked, MSIE 7 is available via MSDN subscriptions, Action Pack subscriptions, and even Microsoft's own web site
The page you linked to doesn't allow downloading of the IE 7 beta, you have to be an MSDN subscriber (and must log in as such) in order to download it.
Bottom line is that I (as a non-subscriber, non-MS partner, etc) have no official way to obtain a copy of this beta; in every sense of the word, this is a leak.
My digital camcorder has a USB out and a FireWire out. If you want to transfer "proper" video from it, you must use the FireWire out; the USB out can only be used to transfer stuff off the SD card. That means (crap) still photos and (crap, very short) low-quality movies.
That would be the correct solution, but there's a problem - neither Outlook nor Outlook Express honour the In-Reply-To header. So while it would work for properly-written MUAs, neither of MS's own desktop apps would be able to use the feature. Also, given that they have no understanding of the header, I'd be surprised if Hotmail itself did.
Why? I turn my TV off at the button on the set every night. Doing so adds maybe an extra 5 seconds to the warm up time the next day when I switch it on, but so what? Same for my monitor - if I'm going to be away from the PC for more than a few minutes, off it goes.
On the other hand, if you are forced to patent before your competitor does, you reveal your secrets to every competitor in the world, even ones not excluded by your patent. They can then use your patent (and your competitors patents too) in their products in their markets to their advantage.
No they can't, you own a patent on it. They can learn from your patent, conduct research in that area, come up with something sufficiently different and use that, but they can't just use your patented tech. There are no exclusions - this isn't a trademark, where you have to be in the same "business area", or copyright, where you have to actually copy something.
The whole point of a patent is that you tell everyone how to do something, while simultaneously being granted a temporary monopoly on doing it. If something is "excluded" from the patent, then it wasn't patented in the first place. If it is covered by the patent, then no-one can use it without licensing it from you.
The problem with trade secrets is that if they leak, you're screwed. You can maybe sue the source of the leak, but that's it. You have no recourse against anyone who implements the leaked tech.
Don't get me wrong, I'm against software patents, but you seem to be arguing from a set of mistaken beliefs. Those who want software patents will never agree to accept trade secrets instead, as they offer zero protection.
Am I wrong for thinking that most Linux users use distributions?
No you're not, and that's exactly my point, although I'm not sure that you quite got it. This is a patch to the KDE source. It does jack shit to the binaries that you installed as part of your distro's release of KDE. In other words, if you installed Fedora, or Mandriva, or whatever, this is almost useless to you. In order to use it, you need to download and "install" the KDE source tree, apply the patch, compile the tree and install the resulting binaries.
Once Redhat, or Mandriva, or whoever's distro you use releases a patch via their update service, then you can just grab it and install it. Until then, this is meaningless for anyone who doesn't know enough about computers to be compiling stuff from source. Like I said, that's fine for me (I have 7 years commercial programming experience on top of all the hobbyist stuff before that), but utterly meaningless for "normal" users; for them, this is still unpatched. Once the distros release patches, then it's patched.
There are patches already available. Fix it. Move on.
There are source patches available. That's fine for you and me, but it's no good for the increasing number of "normal" users who are moving to Linux, who wouldn't be able to apply them if you showed them how. They still have to wait on binary patches from their vendors.
Mind you, this is not like what happens with "some other operating systems," where they have to be berated by users into issuing patches...
That's mostly because the self-same users berated them into only releasing patches once a month at most; they can't have it both ways. I'd also be willing to bet that patches from commercial OS vendors go through rather more rigorous QA processes than this; support contracts and such like make that essential.
This is not ethics or morals, its like asking walmart to give up their entire inventory of shop-brand cola forever, while still buying it in.
Except that in this case, google would still have their data of course. They may lose some of their competitive advantage, but they wouldn't just be throwing money into a hole.
Drawing analogies between data and physical goods is bound to fail; they simply are not the same.
If a web server starts sending back unexpected garbage replies to a web browser, we would all expect the web browser to handle such replies without problem.
No. While I most certainly would not expect the browser to crash, I would not expect it to handle it. Well, yes I'd expect it to handle it, all the while silently cursing that it did and wishing that it told me that the document was screwed, my hatred of IE growing ever so slightly more intense.
Guessing and muddling through is the absolute last thing I (as a web developer) actually want the browser to do. I would like it to choke immediately and obviously, not just do the best it can, sometimes introducing subtle little bugs that can be a complete bitch to track down.
As for an RSS reader, well as others have already pointed out, RSS is just XML, and so if the document isn't well formed, the reader is required by the spec to fail to parse it.
They have to be developed in a way to deal with bad data
The correct way to deal with bad data varies from situation to situation. In this case, it is to display an error. The wrong thing to do is to muddle through. (Needless to say, crashing is an absolute no)
each time that happens there is a wave of complaints to your IT department. And yet they keep doing it anyway. They're either heartless, bastard pyschopaths with no concept of sympathy
You've met our IT department then? (I only wish I was entirely joking)
And then, as if by magic, the link disappeared, with nary a word from the editors.
Editors, it's your site. You can do whatever you like with the submissions, and I can certainly understand you removing that link now that it's been brought to your attention.
However, at the time of my writing this, the only comment rated at +5 is the one I'm replying to, commenting on the link. Surely it's only polite to update the article summary to add something about having removed the link? Otherwise putko starts to look a bit silly...
Slashdot Mirror
There are people dying by the thousands in this country and abroad
According to the hungersite, 24,000 people die every day of hunger and related causes.
Just sayin'.
There's a difference between people believing MS's drivers to be involved, and them actually being involved. Even assuming that they *are* involved, though, that doesn't mean that OS X's drivers won't exhibit exactly the same behaviour.
The most likely thing at the moment appears to be that MacBook systems won't be affected, but it'd still be nice to have some confirmation on that.
They already seem to be doing more instant rebates anyway. The final price is usually a bit higher than with the mail-in rebate though.
Of course it is - more people actually get the rebate, thus the average price of the time goes down, thus they have to make the saving smaller to make the same amount of money.
That's all well and good, and forms part of a valid method of protest. However, in that case, you must be prepared to accept the consequences of your actions - protesting a law like that means being prepared to go to jail, protesting all the way that the law is wrong.
No, they're trying to stop MS having an unfair advantage. If the US government had any balls when it came to MS, they'd do the same.
And before there was yahoo there was altavista. Remember that far back?
I remember altavista when it was a subdomain of (iirc) digital.com.
I remember the web when there were no search engines, or at least none that this poor Physics undergrad knew about.
There should be a note that one or two results were removed due to a request based on the DMCA.
Gotta love the way they link to ChillingEffects.org for a copy of the complaint, rather thatn just hosting it themselves.
It may not work outside the US.
It worked on a request to google.com and google.co.uk from the UK.
Their job is to provide search results to those who need them.
Which, arguably, they are no longer doing in China.
Oh well: The operative system may forbid to take screenshots of the windows that has DRM content (like mac os x does with DRm'ed videos I've been told). You may get your digital camera or even a vigilance camera could do it (you don't need to be 007 to do that).
Well, pretty much any company that implemented a DRM-protection scheme for its documents is going to be banning cameras in the work place anyway.
Besides which, you miss the point. The point is not to stop a malicious employee from purposefully leaking documents, it's to stop a (clueless) employee from *accidentally* leaking documents - eg emailing them to the wrong person, losing a USB key with them on, etc. That it makes malicious distribution harder is a bonus, not the main aim.
It's also a really sucky interface. I can remember using an app that once trapped certain keypresses for its own purposes (OK, it wasn't Java). Never ever again.
Konfabulator is one that springs instantly to mind; ICQ is another. Both trapped key presses that were meaningful to my choice of IDE at the time (JBuilder when I was using ICQ, Eclipse when I was using Konfabulator). Very annoying, until I found the config option to disable or change the trapped keys.
I can't comment on the US stock market, but here in the UK I have been in a company meeting at which the MD explained that one of the reasons why we were hiring contractors like crazy rather than permanent staff was because one of the main stock market measures was profit/(number of permanent employees). So, employ contractors rather than permies, that ratio goes up and the market likes you more...
Never mind that contractors cost more, leave sooner taking knowledge out of the company, etc, so your actual expenses are higher - that ratio's lower, so you *must* be doing better!
It isn't about tax evasion or good faith. It's a way to link productivity to company success.
No, this is about paying less tax on their salaries, thus lowering the overal wage bill and so increasing the overall worth of the company. It really is that simple; it may not be tax evasion (it's probably only tax avoidance), but it's nothing to do with tying productivity to company success.
By my count, less than 50MB is the Firefox heap, stack, and Firefox-specific shared libraries.
Well, that's nice, but I regularly see FF's RAM usage go over the 150-200meg mark after a few hours of what I consider light usage. It's not all system libs...
There's no technically about it; #3 is just a special case of #1, assuming you're thinking of the "run as" service.
Last I checked, MSIE 7 is available via MSDN subscriptions, Action Pack subscriptions, and even Microsoft's own web site
The page you linked to doesn't allow downloading of the IE 7 beta, you have to be an MSDN subscriber (and must log in as such) in order to download it.
Bottom line is that I (as a non-subscriber, non-MS partner, etc) have no official way to obtain a copy of this beta; in every sense of the word, this is a leak.
My digital camcorder has a USB out and a FireWire out. If you want to transfer "proper" video from it, you must use the FireWire out; the USB out can only be used to transfer stuff off the SD card. That means (crap) still photos and (crap, very short) low-quality movies.
That would be the correct solution, but there's a problem - neither Outlook nor Outlook Express honour the In-Reply-To header. So while it would work for properly-written MUAs, neither of MS's own desktop apps would be able to use the feature. Also, given that they have no understanding of the header, I'd be surprised if Hotmail itself did.
That would be extremely inconvenient.
Why? I turn my TV off at the button on the set every night. Doing so adds maybe an extra 5 seconds to the warm up time the next day when I switch it on, but so what? Same for my monitor - if I'm going to be away from the PC for more than a few minutes, off it goes.
I really don't see how it's an inconvenience.
On the other hand, if you are forced to patent before your competitor does, you reveal your secrets to every competitor in the world, even ones not excluded by your patent. They can then use your patent (and your competitors patents too) in their products in their markets to their advantage.
No they can't, you own a patent on it. They can learn from your patent, conduct research in that area, come up with something sufficiently different and use that, but they can't just use your patented tech. There are no exclusions - this isn't a trademark, where you have to be in the same "business area", or copyright, where you have to actually copy something.
The whole point of a patent is that you tell everyone how to do something, while simultaneously being granted a temporary monopoly on doing it. If something is "excluded" from the patent, then it wasn't patented in the first place. If it is covered by the patent, then no-one can use it without licensing it from you.
The problem with trade secrets is that if they leak, you're screwed. You can maybe sue the source of the leak, but that's it. You have no recourse against anyone who implements the leaked tech.
Don't get me wrong, I'm against software patents, but you seem to be arguing from a set of mistaken beliefs. Those who want software patents will never agree to accept trade secrets instead, as they offer zero protection.
Am I wrong for thinking that most Linux users use distributions?
No you're not, and that's exactly my point, although I'm not sure that you quite got it. This is a patch to the KDE source. It does jack shit to the binaries that you installed as part of your distro's release of KDE. In other words, if you installed Fedora, or Mandriva, or whatever, this is almost useless to you. In order to use it, you need to download and "install" the KDE source tree, apply the patch, compile the tree and install the resulting binaries.
Once Redhat, or Mandriva, or whoever's distro you use releases a patch via their update service, then you can just grab it and install it. Until then, this is meaningless for anyone who doesn't know enough about computers to be compiling stuff from source. Like I said, that's fine for me (I have 7 years commercial programming experience on top of all the hobbyist stuff before that), but utterly meaningless for "normal" users; for them, this is still unpatched. Once the distros release patches, then it's patched.
There are patches already available. Fix it. Move on.
There are source patches available. That's fine for you and me, but it's no good for the increasing number of "normal" users who are moving to Linux, who wouldn't be able to apply them if you showed them how. They still have to wait on binary patches from their vendors.
Mind you, this is not like what happens with "some other operating systems," where they have to be berated by users into issuing patches...
That's mostly because the self-same users berated them into only releasing patches once a month at most; they can't have it both ways. I'd also be willing to bet that patches from commercial OS vendors go through rather more rigorous QA processes than this; support contracts and such like make that essential.
This is not ethics or morals, its like asking walmart to give up their entire inventory of shop-brand cola forever, while still buying it in.
Except that in this case, google would still have their data of course. They may lose some of their competitive advantage, but they wouldn't just be throwing money into a hole.
Drawing analogies between data and physical goods is bound to fail; they simply are not the same.
If a web server starts sending back unexpected garbage replies to a web browser, we would all expect the web browser to handle such replies without problem.
No. While I most certainly would not expect the browser to crash, I would not expect it to handle it. Well, yes I'd expect it to handle it, all the while silently cursing that it did and wishing that it told me that the document was screwed, my hatred of IE growing ever so slightly more intense.
Guessing and muddling through is the absolute last thing I (as a web developer) actually want the browser to do. I would like it to choke immediately and obviously, not just do the best it can, sometimes introducing subtle little bugs that can be a complete bitch to track down.
As for an RSS reader, well as others have already pointed out, RSS is just XML, and so if the document isn't well formed, the reader is required by the spec to fail to parse it.
They have to be developed in a way to deal with bad data
The correct way to deal with bad data varies from situation to situation. In this case, it is to display an error. The wrong thing to do is to muddle through. (Needless to say, crashing is an absolute no)
each time that happens there is a wave of complaints to your IT department. And yet they keep doing it anyway. They're either heartless, bastard pyschopaths with no concept of sympathy
You've met our IT department then? (I only wish I was entirely joking)
And then, as if by magic, the link disappeared, with nary a word from the editors.
Editors, it's your site. You can do whatever you like with the submissions, and I can certainly understand you removing that link now that it's been brought to your attention.
However, at the time of my writing this, the only comment rated at +5 is the one I'm replying to, commenting on the link. Surely it's only polite to update the article summary to add something about having removed the link? Otherwise putko starts to look a bit silly...