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!
It has to be going somewhere. jdk-discuss informed (list is moderated, read: another time waster).
Pretty, isn't it. Look&Feel is called JTattoo.
Image was made with the automatic screenshot module on a very old Windows 7 machine where my OS runs flawlessly.
I submitted this bug report to Oracle, and I'm making super-fancy functions like cleanDefunctACCsInAllThreads that automatically fix memory leaks other Java programmers have never heard of.
We will sail memory leak-free! :)
Today we launched bla bla bla.
(No, seriously—we actually did. There is an awesome YouTube downloader in my operating system. I'm just too lazy to write.)
Now I need an awesome screenshot module and an awesome auto-upload-to-blog module.