Please bear with me.
Point of departure:
My goal is OWL (but replacing the "O" for
Ontological with Noological)
Declaration: None of these OO
languages in their current context seem to work for
me.
Observations:
I love AWK, I don't
like C++, I Like plain vanilla Prolog and
Smalltalk (as procedural and declarative) IDE's, but in there current form
useless for my purposes.
I'm unsure of Haskell but, feel it has untapped
potential at a meta level.
So far I have found, that Haskell is a great
"what-if" language (the comparison with the spread sheet correct). I am very
much a remnant of the "how-to" generation (one cannot get much lower than
assembler). I found it difficult to take responsibility and let go of my "goto".
But I do need to reach the "when-to" level: my
project is Virtual Reality and SAI:(asIn Silicon Assisted Intelligence is gnot
AI).
Somehow though all of us early (infant)
programmers moved pretty seamlessly form goto's and flowcharting to
pseudo-code and structure programming techniques: because it works.
However in 1989 I did BR and Semantic Modeling
(Debenham and Montgomery UTS), realising immediately that it did not work. Since
then I still see the Systems Designers equivalent of the flowchart and the
goto i.e
Why is it so hard for SysDesigners to make the same
mind shift we did?
Sorry if I sound rude but I'm stuck in an OO rut
and I need to reach Process Orientation rather quickly.
Any serious suggestions (apart from "just go
away")?
Justin
PS: I don't like dialectical bickering over
detail.
Please spare me the flaming
---
Outgoing mail is certified Virus
Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.585 /
Virus Database: 370 - Release Date: 2/11/04