Someone should do a research project to see the average amount of time that passes between when a new technology is mentioned on/. and when a product actually comes out. I expect that/. is pretty far ahead of the curve. I'm guessing somewhere in the 5 year range.
What if we set up the wireless accounts to use corporate bandwidth only after business hours. I know most businesses (my own included) don't use any bandwidth at all after 5 pm. If there were restrictions set up to allow connections only after hours, it would be a good compromise. People would get free (although limited) online access and the companies wouldn't be giving up any of their 'business critical' bandwidth.
I agree. I was just talking to someone yesterday about getting Linux to the desktop. One of the main problems with this is the varied location of all of the system files. One of the things other OSes have is a standard place for all operating system files (System folder for MacOS and Windows or Winnt for the other). I think something like this would be very helpful for getting Linux to the desktop.
If you have one all-powerful directory that you tell end-users to keep their mits off of, you make the system more user friendly. They know they can't break anything if they don't mess with that directory.
I realize that this pushes Linux away from basic *nix compatibility but maybe that's a good thing.
There is another problem with this kind of thing. What if the software that I write is using some DLLs that Microsoft wrote. Do I become liable with Microsoft's DLL is causing the problem? What about basic conflict between software running on a machine. I can't tell you how many times I've installed a program just to find that it crashed something else on my system.
Microsoft isn't altering a web page on the server side, they are altering it on the client side. Once that page is downloaded to the client's computer, it becomes their property to modify in any way they see fit (including allowing Microsoft's new software to modify it for them).
Short of forcing users to accept some EULA forbidding modifications before viewing your website, there is nothing that you can do. Even if you did that, we all know how impossible it would be to enforce something like that.
If you're now being charged by the byte that you download, this means that you're actually paying for those banner adds and other popups on websites. It's bad enough we're subjected to advertising we don't want to see and now we'll be expected to pay for the priveledge?!
I sincerely hope this doesn't become a worldwide trend.
Slashdot Mirror
Someone should do a research project to see the average amount of time that passes between when a new technology is mentioned on /. and when a product actually comes out. I expect that /. is pretty far ahead of the curve. I'm guessing somewhere in the 5 year range.
What if we set up the wireless accounts to use corporate bandwidth only after business hours. I know most businesses (my own included) don't use any bandwidth at all after 5 pm. If there were restrictions set up to allow connections only after hours, it would be a good compromise. People would get free (although limited) online access and the companies wouldn't be giving up any of their 'business critical' bandwidth.
I agree. I was just talking to someone yesterday about getting Linux to the desktop. One of the main problems with this is the varied location of all of the system files. One of the things other OSes have is a standard place for all operating system files (System folder for MacOS and Windows or Winnt for the other). I think something like this would be very helpful for getting Linux to the desktop.
If you have one all-powerful directory that you tell end-users to keep their mits off of, you make the system more user friendly. They know they can't break anything if they don't mess with that directory.
I realize that this pushes Linux away from basic *nix compatibility but maybe that's a good thing.
Just my thoughts...
-BigNumber
There is another problem with this kind of thing. What if the software that I write is using some DLLs that Microsoft wrote. Do I become liable with Microsoft's DLL is causing the problem? What about basic conflict between software running on a machine. I can't tell you how many times I've installed a program just to find that it crashed something else on my system.
Microsoft? Unfair Business practice?
It just can't be!
Microsoft isn't altering a web page on the server side, they are altering it on the client side. Once that page is downloaded to the client's computer, it becomes their property to modify in any way they see fit (including allowing Microsoft's new software to modify it for them).
Short of forcing users to accept some EULA forbidding modifications before viewing your website, there is nothing that you can do. Even if you did that, we all know how impossible it would be to enforce something like that.
BigNumber
If you're now being charged by the byte that you download, this means that you're actually paying for those banner adds and other popups on websites. It's bad enough we're subjected to advertising we don't want to see and now we'll be expected to pay for the priveledge?! I sincerely hope this doesn't become a worldwide trend.