The Internet is a vast resource with greatly untapped potential. The web is but the first in a long future lineage of connected applications and experiences, and far less concentration should be wasted on trying to shoehorn today's problems into markup (XML, HTML) or HTTP-based solutions (SOAP/XML-RPC, .NET). Instead, new standards, protocols and systems should be explored, based on many of the problems that the Internet is perfect for addressing. The web is static, and people are dynamic; the glue that brings it all together is new software. To address the kinds of applications that people will want to build, the industry needs a dynamic platform that facilitates rapid exploration, prototyping, development and change. Building static shared libraries out of Objective-C and C++ code are not the right direction to take; the Newton approach is a far more flexible direction, and one that is screaming to be taken advantage of in the future. There are no demands that user interface, message handling, storage or network programming place on a system that necessitate it be built out of statically or expensively-bound libraries; dynamic programming languages like NewtonScript, JavaScript and SmallTalk are a much better choice for most higher-level programming tasks.
Simpler, faster and more powerful kernels have been developed than MACH, UNIX or Linux. Be did an excellent job of designing and implementing the lower levels of a modern operating system, leaving the aforementioned runtime and user-level technologies ripe for exploration and implementation. Palm and Apple allowing these technologies to vanish show how irresponsible and ego-driven these companies and their leaders are; it should not matter where a technology comes from; the best technologies should be harnessed to produce the best products with the lowest resource requirements, the best performance, and the simplest, least complex developer experience. This is the only responsible and scientifically credible way to advance technology, and taking this course results not only in the best performing, most efficient, and most legacy-free end-user products, but an exciting development experience that can ultimately be shared with programmers and users alike, ultimately yielding better products and a better user experience, which completes the cycle of success and innovation. Apple needs to get back to user-level systems like HyperCard and Newton, where programming, authoring and customization are paramount to the user experience, rather than trusting programmers with unwieldy programming languages like C++ and Objective-C.



