voodoo warez technologies

home of the object platform :
reconsidering the object
holistic software ecosystems







testing testing. is this mic on?
hello, and welcome to the object platform: birth of the computing ecosystem.


the application is legacy. all software exists in an ecosystem, each piece a member of a greater computing environment. faced with the deeply intertwined nature of our systems, the object platform aims to provide a platform which empowers everyday users to seamlessly shape and craft the connections, components and relations of their world to their own ends; to serve as a playground for experimentation and customization of our digital worlds. we wish to recast the pieces of our digital world to reflect the loosely coupled nature of an ecosystem;


technically, the object platform is an experimental runtime environment for real time and disconnected coordination, providing interaction and modification of distirubted objects through federated identity spaces. crafted as a transactional mobile ambient systems, the object platform purports to deliver a new level of "application interoperability". it derives largely from the concept of a federated object database to provide extensiblity and security across distributed systems. all of these capbilities are built on a rock-bed of dynamic typing and eager replication transactions. together, voodoo warez technologies believes this provides a seamless high performance platform for heterogenous pervasive computing. the new ecosystem. err, like we said, technically....


the object platform was crafted on the central philosophy of the [allegory of the code], the philosophy that an application is nothing more than a shadow puppet errected to obfuscate and manipulate how we view the raw primitives which make up our system. under the name of usability, application builders force monolithic systems upon hapless users and beg to be loved for having divined their perfect system. the purpose of the object platform is to rethink user interface by doing away with the obfuscation of the application; building systems out of of objects directly and permitting the user to interact with not just the final external interface but the inner workings of their systems as well. in the object platform, applications are merely configurations of objects, objects the user is free to manipulate directly should she choose. witness [demonstrations] for our first primitive use cases.




[Google Summer of Code Proposal: The New Ecology]

high level overview and technical description


"In ecology, an ecosystem is a naturally occurring assemblage of organisms (...) living together with their environment (or biotope), functioning as a unit of sorts."

"Ecosystem," Wikipedia, July 10, 2005.


The Object Platform hopes to provide a suitable technical environment to allow for the change, interconnection and evolution of presently isolated software units to form a growing living pervasive software ecosystem. The Object Platform purports to create a deeply nested transactional virtual memory system within the existing Common Language Infrastructure runtime (the virtual machine underneath dotNet) and links this object memory system to a Security Assertion Markup Language (SAML) and Liberty Alliance federated identity framework to allow for operation across untrusted and sometimes-disconnected systems. This serves as groundwork to allow the Object Platform to provide natural exposure to programs, users, scripts and daemons to the running application's object model, along with an integrated dynamic typing system to allow for modification, alteration and supplementation. These three components, the transactional object layer, the standards based federated identity system and dynamic typing extension allow for evolution of a new software ecosystem across formerly isolated disparate systems and disparate applications.




[Dear Lord, Why?!]


Case example. [SpiffyNet] was to be the pinnacle achievement, a home automation system to link together the dispirate devices of the home and achieve control. But control was too amorphous. As SpiffyNet came online I realized control could not be centralized. I bought a fancy USB remote. When I was watching a movie, I wanted it to control that. When I was listening to music, it should control that. If it was plugged into my laptop, I wanted it to still work across the network. All these activities seemed like they should be little more than simple scripts. But I needed an operating environment to script them in.


"Dont make me replace you with a very small shell script."


Thus The Object Platform. Everything would be easily reconfigurable live. The remote could easily shift its destination, and it no longer mattered what computer it was physically attached to.





[Current Status]


The Object Platform is in its second major revision, pending release in early January `06.

It is an open source project. Exact license To Be Determined.