[vagueware] put to a vote

  • From: verbose@xxxxxxxxxx <verbose@xxxxxxxxxx>
  • To: <vagueware@xxxxxxxxxxxxx>
  • Date: Sun, 22 Aug 2004 21:36:13 -0700 (PDT)

ok, dudes..

something that just popped into my head. i've read the 
"http://vagueware.com/Future_of_Vagueware"; article and its pretty cool as far 
as a launching point as to what's next. but i guess what need to be done next 
is to consider how the vagueware software should work.

first, to really get down what is needed for it. or more like what it needs 
from the users. so i don't know if to actually begin another "vagueware 
software spec" article that links from "future of vagueware" article. or to 
keep polishing the vagueware software spec *inside* the "future of vagueware" 

one of the most important things about the way vagueware has to function is 
that it has to be as flexible and un-biased as possible. so how is that done?

it would suck if like, a few years from now, a utterly new, completely 
innovative paradigm were to pop up and vagueware could have dificulty in 
representing it. or in representing information in this paradigm.

so we have to think ahead.

anyway, "vagueware software spec" inside or outside?



Other related posts: