If history repeats, the nature of the paradigm shift would have the
following properties:
- It will be coded by one, two, or three geeks who are fed up
- It will be all over the news for two days before disappearing again
- It will have an open source tool
- It would be bootstrapped off the old paradigm
- It will be instantly dismissed by scores of developers
- It will be instantly dismissed by scores of "developers", who will write
books about why it's not important
- Once it was understood by a few, a slew of companies will arise claiming
to have a tool that implements it
- Microsoft will claim to have one ready in four months, called Visual
NewParadigm.NET
- Years later some non-original tools will actually implement it.
- It's benefits may be relative to the old paradigm (ala procedural vs. OOP),
not necessarily superior
- Once it is understood, something beyond it will arise iteratively, for a
while they will be called the same thing, until they become distinct.
- It's not going to be programming language as we know it. Maybe some
combination of architectural, evolutionary, and aspect techniques
- Lisp weenies will claim
prior art
- The Perl community will claim it's been in the Perl Language all along, you
just have to say "#(&&->$\/\//@mumble->frabitz;;" to accomplish
it.
- Even after it's established by many as the Next Big Thing, people will have
arguments as to what it is. (cf Nobody Agrees What Is OO)
- It won't be where the architects/scientists were looking
- Xerox Parc probably threw it
out as unusuable, years ago.
цитата из
Beyond Object Orientation