The any-TLD idea is intriguing, actually -- it would work with minimal disruption to current DNS services. And there'd be far less of a squatting problem given such a large space to fill.
One disadvantage, of course, is that you'd no longer be able to (as) reliably guess a company's domain name.
And you'd still be stuck with the current morass of trademark protection vis-a-vis domains...e.g., can I register microsoft.sucks without being harrassed by Microsoft's phalanx of lawyers?
What's more, the rendering task is distributed, while the generation is centralized at the web server (and associated applications). Thus, the effect of code inefficiency is magnified on the server side.
Optimization of server-side web code isn't really that different from the general problems of parallel-process and database-access optimization. There's nothing magical about the fact that the front end is a web server rather than (say) a 3270 or the like. All the usual problems are there -- resource shared vs. exclusive access, race conditions, process model tuning, and so forth -- and all the usual solutions apply.
Many companies go astray when they fail to realize that a web app is just a traditional app with a particular front end. This leads them to believe that the rules of good enterprise software development don't apply, and 99% of the time disaster ensues, either immediately, or when they attempt to scale the system up or add/change features.
BTW, has anyone else noticed that Katz has shifted gears over the past few weeks from the "computer people are the smartest, bestest, wonderfullest, most misunderstood" to "computers suck, and they are damaging our society beyond repair"? I wonder if he just had a major system crash a few weeks ago?
Slashdot Mirror
The any-TLD idea is intriguing, actually -- it would work with minimal disruption to current DNS services. And there'd be far less of a squatting problem given such a large space to fill.
One disadvantage, of course, is that you'd no longer be able to (as) reliably guess a company's domain name.
And you'd still be stuck with the current morass of trademark protection vis-a-vis domains...e.g., can I register microsoft.sucks without being harrassed by Microsoft's phalanx of lawyers?
What's more, the rendering task is distributed, while the generation is centralized at the web server (and associated applications). Thus, the effect of code inefficiency is magnified on the server side.
Optimization of server-side web code isn't really that different from the general problems of parallel-process and database-access optimization. There's nothing magical about the fact that the front end is a web server rather than (say) a 3270 or the like. All the usual problems are there -- resource shared vs. exclusive access, race conditions, process model tuning, and so forth -- and all the usual solutions apply.
Many companies go astray when they fail to realize that a web app is just a traditional app with a particular front end. This leads them to believe that the rules of good enterprise software development don't apply, and 99% of the time disaster ensues, either immediately, or when they attempt to scale the system up or add/change features.
Nah, he just has 10,000 shares of eToys stock.