Input:
"Confessions of a Burglar Video"
(It's the name of a video on YouTube.) So... is the video confessing—or the burglar? Let's ask the parser.
1. Confessions {of {a {Burglar Video}}} 2. {Confessions {of {a Burglar}}} Video
Yup, it has found the 2 grammatical possibilities. Next up: Semantic analysis to rate these against each other.
We're reaching a nice number of JavaX-enabled computers. And no, they're not all mine.
until Stefan's OS takes the world.
Stefan's OS has a greater impact than Windows 95. You just wait and see!
The solution is source code inspection, and JavaX makes it practical.
The operating system is the optimal place to automate everything—it sees everything and it can act upon information. Also loading and even making dynamic code on the fly is trivial in my OS.
Let's say vanilla Java is too verbose. (Everybody knows this.) Instead of this:
class ShowBackgroundImage extends DynModule {
I want to type (and see) only this:
class ShowBackgroundImage > DynModule {
In JavaX, that takes exactly one line in the translator:
jreplace(tok, "class <id> > <id> {", "class $2 extends $4 {");
And this easily, my language has been extended.
Numerous small improvements. Finds memory leaks automatically (!). Ability to make "alternative brains" (multiple distinct instances of OS on a machine). Still compatible with Windows, Linux and Mac.
Gotcha.
I told you Java is stable!