Slashdot Mirror


Permanet vs. Nearlynet

Clay Shirky has a good essay on wireless networking, contrasting two approaches to building out a network, roughly akin to the cathedral and bazaar methods of building software.

9 of 58 comments (clear)

  1. the problem with wireless networking by potaz · · Score: 5, Insightful
    quote: For most of the past year, on many US airlines, those phones inserted into the middle seat have borne a label reading "Service Disconnected." Those labels tell a simple story -- people don't like to make $40 phone calls.

    Well, duh. Most people don't like to spend $40 on anything, let alone a phone call. I don't understand how businesses think that hey, if we're dealing with other business people, they'll want to throw money around like it was candy! Treat them like other people (ie: cheap) and you'll find you have more realistic expectations.

  2. Future market on the horizon by manseman · · Score: 5, Interesting

    When the permanet is a reality everywhere, the real profit will be in selling devices that disconnect or shield you from the nets. Kind of like sunblock.

  3. summary by DrSkwid · · Score: 3, Insightful

    it's easier to turn "cheap and lousy" into "cheap and adequate" than it is to turn "expensive and ubiquitous" into "reasonable and ubiquitous" and that people will tolerate the cheaper option if the price differential is sufficient.

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  4. Re:false dichotomy by LoadStar · · Score: 4, Interesting
    the nearlynet that shirky disparages so loudly is what creates technological innovations and practical experience in building a network. We have very few technologies in any field that resist quick obsolescence. Until we do we shouldn't build a perma-anything. I think nanotechnology will allow us to engineer things that will still be useful hundreds of years from now.

    I didn't get from the article that he disparages the nearlynet - in fact, he credits nearlynets for pushing permanets out. In his examples - iridium and airphones - he describes how the nearlynet - cell phones and wifi - has lower cost of entry and use, and as such, will tend to win over the more expensive permanets.

    Permanets seem to have more innovative solutions, but the cost of building out these permanets means that the cost-benefit ratio rarely works out - people just don't need to be connected that badly.

    My only question that just popped into my head: the Internet was built-out as an extension of a government program. If the Internet had been a private sector project, would it have been built? It seems to have all the earmarks of a permanet as described in the article... a fairly expensive and permanent build-out phase, and during the build-out phase, very little benefit to balance out the cost. It was only fairly heavy government subsidies that helped the Internet become a reality and make it affordable for anyone to get on.

    It's an interesting thought. If the government building out the Internet helped make it affordable enough - would doing the same with, say, Iridium have helped? Could we have been carrying around sat phones at this point had it been a government project that was then opened up to the public? It kind of helps make the taxes that are going to, say, NASA, make sense - because perhaps, one of their projects might be the next Internet.

  5. Re:false dichotomy by madfgurtbn · · Score: 3, Interesting

    My only question that just popped into my head: the Internet was built-out as an extension of a government program. If the Internet had been a private sector project, would it have been built?

    Prodigy, Compuserve, AOL all attempted it, but I think they were all doomed to the extent they tried to maintain walled gardens.

    The nearlynet/permanet problem has also been exacerbated by the walled garden approach, I think.

    --
    Send lawyers, guns, and money. Dad, get me out of this.
  6. But they are important to remember by bluGill · · Score: 3, Insightful

    Sure as a tech I can design a network to be avaiable anywhere. (Even on airplanes during takeoff/landing, where most electronic devices are banned) However this artical make it clear that I shouldn't spend my time doing that unless someone is watching the overall ecconmic costs. Sure as an engineer that isn't my prime responsibility, but I should be aware that other issues exist, and if they are not being watched by someone who understand them (which I likely don't) then I should expect the project to fail.

    It has been said that most technological project fails because of bad management. I believe it, because I've seen it. Engineers may not understand or know these issues, but it is the job of management to know they exist and solve them. Technical problems can be solved if resources are unlimited (Mostly money, but sometimes other). However that is not the case. Many projects have solved all the technological problems, but the cost was so high that nobody could afford them.

  7. Microsoft: Ahead of Its Time by KPU · · Score: 3, Funny

    Support for disconnection is already included in all versions of windows. Some call this feature the BSOD, others call it Driver Signing and Palladium. But these all have one common feature: windows supports disconnecting and you don't even have to do anything!

  8. Not Cathedral/Bazaar! by mcrbids · · Score: 4, Insightful

    This is not really at all like "Cathedral/Bazaar" but rather, " Worse is Better. (now updated)

    The underlying idea is that the "right" way isn't always the best, but rather, that the "best" way is what is "good enough" for cheap.

    This is the same force that makes Linux compete against *nix, and is also responsible for the rise of Microsoft against vastly superior technologies.

    --
    I have no problem with your religion until you decide it's reason to deprive others of the truth.
  9. Failure of the Essay by aaarrrgggh · · Score: 3, Insightful
    The failure with permanets is not "permanet" vs. "nearlynet", it is about creating a business strategy to bridge between the two.

    Simple example: I can't get cell phone reception in the basement of the building I work in. The building has many wireless services, but the only one with antennas in the basement is the Facilities walkie-talkie system.

    It will never be cost-effective for a wireless phone company to provide us with better cellular service in our little basement, but it is worthwhile for me to have phone access everywhere in the building. What are the alternatives?

    Land-line phones at regular intervals throughout the building so it is easy to get to a phone.

    A pager network to know when someone wants to reach you.

    A private exchange telephone service (a la original PCS concept), with antennas distributed as required. ...but other people have different needs! Someone else needs their blackberry, and another person needs the iPaq and 802.11.

    Ultimately, the only viable solution is software defined radio devices, which take advantage of whatever distribution mechanisms are available.

    To put it in terms of the article, the best permanet is a loose network of nearlynets....