Like many others, I wanted to go with someone other than the local phone company's (SWB) DSL, but was told by Rhythms, Covad, etc. I was too far away from the local office. A call to SWB, though, revealed that I *was* too far away -- if I had copper -- but since I had fiber to the curb then I could indeed get DSL. I asked the phone company why the other providers didn't have this information (eg. who can receive VDSL via fiber) and they didn't have an answer (I really didn't expect the sales guy to know, but I thought I'd ask). Anyway, it seems the trouble with RBOCs and DSL begin with the sales process and goes from there...
Oh, I think we've got to give people and systems more credit. There are many systems that are incredibly complex, yet the human mind both imagined and conjured them. I don't think this concept is anymore exotic than that of genetic algorithms (which, when first introduced, seemed pretty farfetched). Of course, JIT coding probably only optimally applies to certain problems. And, it seems that there should be no fear of losing work to JIT systems. There's always new problems to solve and old bugs to fix.
Slashdot Mirror
Like many others, I wanted to go with someone other than the local phone company's (SWB) DSL, but was told by Rhythms, Covad, etc. I was too far away from the local office. A call to SWB, though, revealed that I *was* too far away -- if I had copper -- but since I had fiber to the curb then I could indeed get DSL. I asked the phone company why the other providers didn't have this information (eg. who can receive VDSL via fiber) and they didn't have an answer (I really didn't expect the sales guy to know, but I thought I'd ask).
Anyway, it seems the trouble with RBOCs and DSL begin with the sales process and goes from there...
Oh, I think we've got to give people and systems more credit. There are many systems that are incredibly complex, yet the human mind both imagined and conjured them. I don't think this concept is anymore exotic than that of genetic algorithms (which, when first introduced, seemed pretty farfetched). Of course, JIT coding probably only optimally applies to certain problems.
And, it seems that there should be no fear of losing work to JIT systems. There's always new problems to solve and old bugs to fix.
Talk about no class...