Amorphous OS

a new paradigm for a computing environment OS

"Water is insubstantial. By this I mean you can not grasp
hold of it. You can not punch it and hurt it. Be formless,
shapeless, like water. Now you put water into a cup, it
becomes the cup, you pour water into a bottle, it
becomes the bottle, you put water into a teapot, it
becomes the teapot. Now water can flow or it can
crash...be water my friend." --Bruce Lee

Slide 3

USERS Perspective

Why does the user need to see the local hardware?

With modern networking we can eliminate the users awareness of disk space, memory size, cpu power.

We can even go far enough to eliminate file names, paths and directories, and even network topologies.

These concepts are as irrelevant to reading E-mail or browsing the web as head cylinder and sectors on the hard drive are.

Developers Perspective

You should be able to write code in what ever is most familiar, comfortable and gets the job done.

Dissimilar languages should have a common method for communication.

Interaction between languages, CPU's, OS's, systems, and remote locations can be abstracted through a common interface.

Direction of computing.

Most aspects of computing are improving exponentially.

(CPU, RAM, DRIVES, NETWORKS, WIRELESS)

For the past 20 years, a system at that time has been able to emulate a system 5 years older. Moores Law stated 2x in 18 Months, this is 10x in 5 years. and 100x in 10 Years.

Soon Any wrist watch can run anything we have today faster then we can now!.

ASP and Network Software Distribution

The Current architectures make this very impractical.

Installing massive bloat ware packages are time consuming, risky of crashes, often require reboots and is difficult to copy protect.

The ASP's are limited to software installs or the web interface.

A new model for incremental payments and just in time installation is needed.

Slide 8

Amorphous file System

A Decentralized file system

Extend one continuous virtual file system across multiple networked computers and operating systems, even the Internet.

Eliminate the concept of directories. As they are currently know.

Any file may be anywhere in physical space on the computers. Each computer locates and re-locates files and parts of files transparently on the fly, this is hidden by an abstraction layer.

Slide 10

Slide 11

Software Architecture

Replace legal “copyright” with a profit or “compensation right”. Meaning anyone can copy and transport and use the software but the author reserves the right to profit from his work. This ties into an incremental, fractional micropayment system for one of several profit models.

Micropayments for:

Code or Data usage

server CPU usage

drive space usage

Slide 13

What do I mean by Object?

In Unix script are like objects.

#!/bin/sh

code ...

data ...

The /bin/sh tells the shell(os) what program is to be used to process the rest of the file.

Unix doesn’t care what’s in the file. Perl, TCL, csh, bash, or even uuencoded data, or a jpeg image even.

Slide 15

Slide 16

Slide 17

Another advantage

How to allow GUI based code to take advantage of parallel processing

How to simplify object oriented to run on parallel processing clusters.

SMP will soon be integrated into a multiple CPU in one chip package, Applications need to handle this gracefully.

The Next level

Whole desktop with applications available on a subscription basis from a yahoo or google. Software, Books, music, video, photos, etc.

Backup services, remote repair and upgrades and virus's will be a thing of the past.

Your desktop work environment will be more like a home page. It's not tied to a computer, since the hardware is disposable. It's

tied to your portal and user account.


	Why does the user need to see the local hardware?

	With modern networking we can eliminate the users awareness of disk space, memory size, cpu power.

	We can even go far enough to eliminate file names, paths and directories, and even network topologies.

	These concepts are as irrelevant to reading E-mail or browsing the web as head cylinder and sectors on the hard drive are.


	You should be able to write code in what ever is most familiar, comfortable and gets the job done.

	Dissimilar languages should have a common method for communication.

	Interaction between languages, CPU's, OS's, systems, and remote locations can be abstracted through a common interface.


	Most aspects of computing are improving exponentially.
	(CPU, RAM, DRIVES, NETWORKS, WIRELESS)
	For the past 20 years, a system at that time has been able to emulate a system 5 years older. Moores Law stated 2x in 18 Months, this is 10x in 5 years. and 100x in 10 Years.

	Soon Any wrist watch can run anything we have today faster then we can now!.


	The Current architectures make this very impractical.

	Installing massive bloat ware packages are time consuming, risky of crashes, often require reboots and is difficult to copy protect.
	The ASP's are limited to software installs or the web interface.

	A new model for incremental payments and just in time installation is needed.


	A Decentralized file system

	Extend one continuous virtual file system across multiple networked computers and operating systems, even the Internet.

	Eliminate the concept of directories. As they are currently know.

	Any file may be anywhere in physical space on the computers. Each computer locates and re-locates files and parts of files transparently on the fly, this is hidden by an abstraction layer.


	Replace legal “copyright” with a profit or “compensation right”. Meaning anyone can copy and transport and use the software but the author reserves the right to profit from his work. This ties into an incremental, fractional micropayment system for one of several profit models.
	Micropayments for:
	Code or Data usage
	server CPU usage
	drive space usage


	In Unix script are like objects.
	#!/bin/sh
	code ...
	data ...

	The /bin/sh tells the shell(os) what program is to be used to process the rest of the file.

	Unix doesn’t care what’s in the file. Perl, TCL, csh, bash, or even uuencoded data, or a jpeg image even.


	How to allow GUI based code to take advantage of parallel processing

	How to simplify object oriented to run on parallel processing clusters.

	SMP will soon be integrated into a multiple CPU in one chip package, Applications need to handle this gracefully.


	Whole desktop with applications available on a subscription basis from a yahoo or google. Software, Books, music, video, photos, etc.
	Backup services, remote repair and upgrades and virus's will be a thing of the past.

	Your desktop work environment will be more like a home page. It's not tied to a computer, since the hardware is disposable. It's
	tied to your portal and user account.