From the earlier post:
wiki + database = ?
wiki = collaborative editing + moderation.
database = tables, UDFs, views + multiuser data-modification capacities.
So, wiki of databases = ?
“of” == a relation phrase.
Other common relation phrases are : about, over, under, before, after, for
wiki about databases == wikipedia page for databases
wiki over database layer == normal wiki app.
btw, abnormal wiki app will be ….?
wiki with flat-file backend !
wiki _without_ database.
(note to self: so next time, don’t forget “without” in the relation phrases list.)
os without os == fake OS!! or OS simulator !!
os without wiki = ?
think… (hint: wiki == modification)
os without *modfication* == read-only file system!!
simply, insufficient user permissions for you as a user.
wiki under database layer = ?
flexible file system which can be edited by anybody!!
(no points for guessing which popular os allows anybody to manipulate internals maliciously 😉 😉 )
or more consructively,
multiple interconvertible filesystems….
wait! do i hear “virtualization“?
VMware come hire me 😉
I’m gonna be rich! I’m gonna be famous! I’m gonna be powerful! I’ll rule the world! 😉
or even more constructively,
an os that has modularity and can be re-coded and compiled / interpreted on-the-fly!
Complete interpreted OS!!
True open source and free software!
or still more dizzily,
editable VM images, changing VM images or appliances on-the-fly.
and lastly, if you did not start jumping excitedly,
editable *processor*, on-the-fly!
Multi-purpose CPUs arranged in cluster-like fashion, but, on-the-fly reprogrammable, as FPU, GPU, Vector CPU, 32-bit to 64-bit or 64-bit to 32-bit, whatever else you have….
All running a wiki! 🙂
Interoperable and freely interconvertible virtual appliances from various VM solution providers.
That is, an open format for VM appliances or VM images !
And an open format for describing the gate-level or unit-level logic for all such userland-requested editable-processors so that such OSes and VMs can happily interconvert in such dynamic server environments.
Actually sounds like pure and complete chaos more than flexibility.
But good to think this out till here.
Foolish companies can stick with bribing officials while we floss guys innovate open ideas and implement opens systems for the next quarter century of computing 🙂
Yeah! IP scumbags, come, sue me! Sue! Sue! Sue!
All started from a humble play of words.
So much for the credibility of the concept of “inventive step”
As you can see, ladies and gentlemen, IPR stands for “Intelligent Phony Rights”
And Inventive Step is pretty much “inventable” by a well written program!
Go ahead and file as many patents as you want!
They mean **nothing** in software.
This is the spirit of Free Software. Free ideaware. Free mindware. Free thoughtware.
(er… thought?? where?? it’s only a “smart” algorithm! 😉 )
All this is prior art if no one’s already thought of it. See the timestamp url at the end of this entry.
See the site http://publictimestamp.org
There is more money in the correct way than in the extortion system.
Volume is the generator of revenue in this new age.
GPL violations is one.
BSA-authorized anti-piracy raids is another.
easy and big money isn’t there. But money is there.
I’m suggesting this only so that you don’t come suing me.
I intend to hurt no one’s earning.
Even if piracy were to be eliminated, Megaflop would lose no revenue, simply because the guys who might use FLOSS and Linux are mostly pirating anyway!
FLOSS will clean up the system for non-paying users of proprietaryware, and enterprise customers of Megaflop can continue using the same products. No problems for anyone.