OOPv2

This project is about re-orienting the Object-Oriented Paradigm. About fulfilling it`s vision of re-usable code which after 20+ years hasn't happened. This -- in the Internet Age, with the exabytes of wealth in public data -- is an unacceptable waste.

First to analyze what went wrong.

• A thousand programs with their own personal folksonomies of data organization created a thousand mini domain-specific languages (their API) that always felt like wearing someone else`s underwear.
• No language was really willing or ready to provide the tools in which a DataEcosystem could evolve. Most languages were still focused on the individual programmer.
• Some languages attempted to be so pure to the OOP paradigm (making everything an object), that they couldn't entice the practical programmer anymore.
• The understanding and the art simply hadn't been perfected. Many were focusing the theory on simulating actual or geometrical objects in an attempt to make it maximally generalizable, which in practice was never done and misguided the thought processes. Consider "never" a practical, not absolute, word.

Secondly, to offer solutions to fix it.

• A programming environment which allows interaction with, and testing of, user-created, pre-documented, and network-sourced data objects,
• A programming language which recognizes the need and function for many, simple, loosely-coupled, modular objects that can be built up into complex compound objects using object composition, just as the Unix shell did for simple file system commands,
• An education outreach to teach programmers about how much data is sitting underutilized from science, government, and elsewhere which is not generating the value that it could to make a better world.

For the second issue in the last paragraph, some work has been done.

Most objects need to communicate to the programmer environment, to build greater data structures, not to the outside world, so make inter-object communication built-in, so programmers aren't spinning their own solutions -- doing it wrong and/or arbitrarily. Answer: Create a uniform syntax for all objects, using operators >>InTake, <>, absent a left-hand side (lhs) could be decoded as a request from the interpreter environment itself to instantiate the object and send it on it's way: "EcosystemShell$ >>ThisDBTemplate".

For more, see ObjectOrientedRefactored.