I agree with you that he does actually say some useful things (I wouldn't run a firewall if it weren't for the GRC), but after reading some things against him I have come to agree with them at least a little - for example, from vmyths, "Translation: antivirus software could no longer save the world from evildoers as of 1992.". Also, they go on to say ""Nearly impossible to detect." "Alarming capabilities." "The game is forever changed." "Amazing and staggering." "Completely incapable." "Fundamentally a dead end." Gibson mastered the art of trigger phrases at least nine years ago.". This is something that is very obvious if you read something he's written - the first time I went to GRC, I wasn't sure it was real because his writing style looks like it's stolen straight from spam. He is doing everything possible to get his readers' attention, and it seems to be working, which is a bad thing if he starts spreading delusions. ---
They want.NET compatibility. If they don't support C#, that's not.NET compatibility - they will make it impossible to use their work for a development platform under the.NET system. ---
>>>What I don't get is why the HELL they are implementing the CLR. There's already a GNU endorsed, open source VM architecture - Kaffe. GCC 3.0 does java bytecode's now, too. It's a massive wheel-reinvention to go implement an MS technology.
Chances are that.net, like Windows 9x and possibly Windows XP, will catch on quickly among consumers and MS-oriented businesses and become very popular (they have already made very good progress on the server side from what I can see). Ximian is attempting to loosen the monopolistic powers this will give Microsoft by providing the same client functionality in linux. Now, can you tell me why they would try to duplicate client functionality minus one of it's important parts? If they use the GNU endorsed, open source VM architecture their client won't be compatible with any programs that use the CLR, and that defeats the whole point. ---
But the point is that they will lose sales by using Passport exclusively. If they can add the passport users who won't use a non-passport site while keeping their current customers, they will do it. If they will lose customers by using passport exclusively, they are stupid. ---
The internet will still be here. There will be nothing to stop us from using linux and downloading OSS from other people like we've always been doing. I'd be surprised if the big sites supported passport exclusively (oh, by the way, you can't use our site unless you installed Netscape on your Pentium 3 in 1970 too). The worst they can do is take down the competition on their ground (.NET). ---
Taxes aren't all that bad. Would you like to remove all taxes and pay the full price (divided among users) of every pulic service you use? Would you like to have a special device in your car to bill you for every 50 meters of road you use? This is not the way to get privacy - you would have to be tracked everywhere for billing. Sure, some people pay for things they don't use, but others get a lot more than they pay for. ---
As I say below, even when some sites are still working, calling your ISP can help (unless you feel you can analyze the entire north american portion of the internet from your computer). Let's say a few routers go down somewhere, and some of the sites your company uses regularly are cut off. After you know your connection with your ISP is good, you call them. They find that they problem isn't on their side, so they call their connections. It keeps going until they find where the problem is, and knowing this helps you know what to do (try again, wait a while, use the 'TCP/IP over avian carriers' protocol). It may not always work this well (depending on what your ISP things of you), but putting the question through the same route that your connection goes can save you time and get an answer. Of course this may not be the best thing for an end-user, but for a large data-storage company it's a great way to find the problem and know if there are any solutions and when it will be fixed. ---
In this case, the person is complaining that they are too stupid to know who to call when something goes down. Let's say someone accidentally cuts through a backbone and most of the sites they access don't work anymore. When this happens, they can call their ISP, who can call their provider, until they get up to the company that controls the backbone, that should know when it goes down. Even if some of the sites do still work, the ISP can be a good source of information, because they know how to get information from higher places (even if you wanted to call the backbone owner to ask about the status, how would you know the problem is there? The best reason to call your ISP is that they can find the problem if it's with them or pass it on to the next level if it's not.) ---
It's like napster against gnutella - the speed of a centralized server (which has to be a very good server for this to work) against the open target for problems it causes.
This 2 minutes between post thing is great for generating traffic, because I keep clicking submit until it goes through! ---
The funny thing here is that what they say they want to do could easily turn into the stupides thing ever - re-inventing the whole internet. They don't like the way things are, so they want to start from scratch. And we all know how well that works:)
I just hope they never get around to trying to do this the smart way. ---
>not having a clue who their ISP is
if they expect a working connection they'd better know who their ISP is. This might be a case of managers trying to do everything instead of the tech people who were trained to do it. ---
But of course - it's their god-given right to take all your money and control your life! What else would you expect from the people destined to be the true masters of the universe? ---
ok, if another website goes down, there's nothing you can do about it. But if your connection dies, then your ISP is probably your only link to the internet, so they should know something. It may be something beyond their control (maybe one of their connections is having problems), but they are where you connect to the internet, so if your connection isn't working (and it's not a problem on your end), they should know what's happening. Maybe they can't solve the problem, but they should be able to tell you where it is (at least more accurately than you could find out yourself) ---
One of the people says "If something goes down, you don't even know who's accountable. The Internet is, like, 'Who ya gonna call?' "
hmm... maybe START WITH YOUR ISP!!!! It's really not that hard to figure out - they are responsible for connecting you to the internet, so when there's a problem, call them! I wish he would go compete in the darwin awards olympics. What a fucking idiot! ---
why couldn't an IP address replace a domain name? And whether someone thinks they can send an email to their local [network|host] and i'll get it, or they just can't send the email, it makes no difference at all the me. They are the one wasting their time (although I hope they aren't that ignorant). ---
maybe not that much, but take my Athlon: the entire component, with the pins and cache memory, is a good-sized object (for an internal computer component), but the actual core that does the work is probably near-invisible to the naked eye. Unless we totally abandon modular computers, every component will have to come in a size that can easily be handled by a human, and the actual working parts will continue to shrink. ---
Re:Discussing an entire marker/industry in one boo
on
Linux Game Programming
·
· Score: 1
Yes there is a way it could have been a good book. They could have been more complete, had less useless information (a summary of each license would be sufficient IMO, and a good chapter about why to open-source a game might be enough for me to buy it). They should have also either targeted new game developers or game developers who want to target linux and then witten a book that covers all the important points for their target audience. ---
Wouldn't it be possible to add error correction to the ripping software? 99% of the digital music will be intact, it will just be the occasional piece of broken data that makes the sound, so it should be trivial to use the error correction or some other audio correction technology to fix these without going through the hardware. ---
My friend uses Windows 2000 and he says it has never crashed on him, but for everyone who's used Windows 9x, Linux would br a way better OS. They could, of course, switch to win2k for more stability, or they could get Linux - i've heard the Mandrake 8 powerpack has packages that would cost over 1000$ under windows. Or, if they don't even want to pay a fraction of the price of Windows, they can just download everything and get nearly all the software they would in the powerpack. Linux may not have the same advantages over Win2k that it does over 9x, but it's still a fraction of the price (especially when you consider that linux contains nearly the equivalent of Win2k server (or whatever their most expensive is), Office, and half a software store) ---
Or just write a program that tests every possible name... as a bonus you get to crash the server by sending non-alphanumeric characters and overload their connection. ---
By 2020, the physical connections will probably be nearly infinitely bigger than the technology! (well, at least I hope computers are still modular until they have infinite power in inifintely small space). We already have CPUs that are 99.999% casing and connections, but with this technology we wouldn't be able to tell the difference between a blank casing and a working component without a powerful microscope! ---
Slashdot Mirror
I agree with you that he does actually say some useful things (I wouldn't run a firewall if it weren't for the GRC), but after reading some things against him I have come to agree with them at least a little - for example, from vmyths, "Translation: antivirus software could no longer save the world from evildoers as of 1992.". Also, they go on to say ""Nearly impossible to detect." "Alarming capabilities." "The game is forever changed." "Amazing and staggering." "Completely incapable." "Fundamentally a dead end." Gibson mastered the art of trigger phrases at least nine years ago.". This is something that is very obvious if you read something he's written - the first time I went to GRC, I wasn't sure it was real because his writing style looks like it's stolen straight from spam. He is doing everything possible to get his readers' attention, and it seems to be working, which is a bad thing if he starts spreading delusions.
---
They want .NET compatibility. If they don't support C#, that's not .NET compatibility - they will make it impossible to use their work for a development platform under the .NET system.
---
>>>What I don't get is why the HELL they are implementing the CLR. There's already a GNU endorsed, open source VM architecture - Kaffe. GCC 3.0 does java bytecode's now, too. It's a massive wheel-reinvention to go implement an MS technology.
.net, like Windows 9x and possibly Windows XP, will catch on quickly among consumers and MS-oriented businesses and become very popular (they have already made very good progress on the server side from what I can see). Ximian is attempting to loosen the monopolistic powers this will give Microsoft by providing the same client functionality in linux. Now, can you tell me why they would try to duplicate client functionality minus one of it's important parts? If they use the GNU endorsed, open source VM architecture their client won't be compatible with any programs that use the CLR, and that defeats the whole point.
Chances are that
---
But the point is that they will lose sales by using Passport exclusively. If they can add the passport users who won't use a non-passport site while keeping their current customers, they will do it. If they will lose customers by using passport exclusively, they are stupid.
---
The internet will still be here. There will be nothing to stop us from using linux and downloading OSS from other people like we've always been doing. I'd be surprised if the big sites supported passport exclusively (oh, by the way, you can't use our site unless you installed Netscape on your Pentium 3 in 1970 too). The worst they can do is take down the competition on their ground (.NET).
---
Taxes aren't all that bad. Would you like to remove all taxes and pay the full price (divided among users) of every pulic service you use? Would you like to have a special device in your car to bill you for every 50 meters of road you use? This is not the way to get privacy - you would have to be tracked everywhere for billing. Sure, some people pay for things they don't use, but others get a lot more than they pay for.
---
As I say below, even when some sites are still working, calling your ISP can help (unless you feel you can analyze the entire north american portion of the internet from your computer). Let's say a few routers go down somewhere, and some of the sites your company uses regularly are cut off. After you know your connection with your ISP is good, you call them. They find that they problem isn't on their side, so they call their connections. It keeps going until they find where the problem is, and knowing this helps you know what to do (try again, wait a while, use the 'TCP/IP over avian carriers' protocol). It may not always work this well (depending on what your ISP things of you), but putting the question through the same route that your connection goes can save you time and get an answer. Of course this may not be the best thing for an end-user, but for a large data-storage company it's a great way to find the problem and know if there are any solutions and when it will be fixed.
---
In this case, the person is complaining that they are too stupid to know who to call when something goes down. Let's say someone accidentally cuts through a backbone and most of the sites they access don't work anymore. When this happens, they can call their ISP, who can call their provider, until they get up to the company that controls the backbone, that should know when it goes down. Even if some of the sites do still work, the ISP can be a good source of information, because they know how to get information from higher places (even if you wanted to call the backbone owner to ask about the status, how would you know the problem is there? The best reason to call your ISP is that they can find the problem if it's with them or pass it on to the next level if it's not.)
---
The hardest part was getting past the 'reinstall windows' tier of support
:)
Try insisting that they have to re-install all their routers and wiring
---
It's like napster against gnutella - the speed of a centralized server (which has to be a very good server for this to work) against the open target for problems it causes.
This 2 minutes between post thing is great for generating traffic, because I keep clicking submit until it goes through!
---
The funny thing here is that what they say they want to do could easily turn into the stupides thing ever - re-inventing the whole internet. They don't like the way things are, so they want to start from scratch. And we all know how well that works :)
I just hope they never get around to trying to do this the smart way.
---
>not having a clue who their ISP is
if they expect a working connection they'd better know who their ISP is. This might be a case of managers trying to do everything instead of the tech people who were trained to do it.
---
But of course - it's their god-given right to take all your money and control your life! What else would you expect from the people destined to be the true masters of the universe?
---
ok, if another website goes down, there's nothing you can do about it. But if your connection dies, then your ISP is probably your only link to the internet, so they should know something. It may be something beyond their control (maybe one of their connections is having problems), but they are where you connect to the internet, so if your connection isn't working (and it's not a problem on your end), they should know what's happening. Maybe they can't solve the problem, but they should be able to tell you where it is (at least more accurately than you could find out yourself)
---
One of the people says "If something goes down, you don't even know who's accountable. The Internet is, like, 'Who ya gonna call?' "
hmm... maybe START WITH YOUR ISP!!!! It's really not that hard to figure out - they are responsible for connecting you to the internet, so when there's a problem, call them! I wish he would go compete in the darwin awards olympics. What a fucking idiot!
---
"small as a baseball"
at what point? It could have started out the size of a truck and burned up to a small core piece or 5.
---
Of course, they just lost customers and everyone knows they use ROT13...
---
mod parent up!!! +3 funny!
---
why couldn't an IP address replace a domain name? And whether someone thinks they can send an email to their local [network|host] and i'll get it, or they just can't send the email, it makes no difference at all the me. They are the one wasting their time (although I hope they aren't that ignorant).
---
maybe not that much, but take my Athlon: the entire component, with the pins and cache memory, is a good-sized object (for an internal computer component), but the actual core that does the work is probably near-invisible to the naked eye. Unless we totally abandon modular computers, every component will have to come in a size that can easily be handled by a human, and the actual working parts will continue to shrink.
---
Yes there is a way it could have been a good book. They could have been more complete, had less useless information (a summary of each license would be sufficient IMO, and a good chapter about why to open-source a game might be enough for me to buy it). They should have also either targeted new game developers or game developers who want to target linux and then witten a book that covers all the important points for their target audience.
---
Wouldn't it be possible to add error correction to the ripping software? 99% of the digital music will be intact, it will just be the occasional piece of broken data that makes the sound, so it should be trivial to use the error correction or some other audio correction technology to fix these without going through the hardware.
---
My friend uses Windows 2000 and he says it has never crashed on him, but for everyone who's used Windows 9x, Linux would br a way better OS. They could, of course, switch to win2k for more stability, or they could get Linux - i've heard the Mandrake 8 powerpack has packages that would cost over 1000$ under windows. Or, if they don't even want to pay a fraction of the price of Windows, they can just download everything and get nearly all the software they would in the powerpack. Linux may not have the same advantages over Win2k that it does over 9x, but it's still a fraction of the price (especially when you consider that linux contains nearly the equivalent of Win2k server (or whatever their most expensive is), Office, and half a software store)
---
Or just write a program that tests every possible name... as a bonus you get to crash the server by sending non-alphanumeric characters and overload their connection.
---
By 2020, the physical connections will probably be nearly infinitely bigger than the technology! (well, at least I hope computers are still modular until they have infinite power in inifintely small space). We already have CPUs that are 99.999% casing and connections, but with this technology we wouldn't be able to tell the difference between a blank casing and a working component without a powerful microscope!
---