Thoughts on continuing development

To me I got lucky because I see Class Viewer as doing things close to the Java language itself, which I knew I wanted while developing, and in my opinion is for the most part a GUI on Java Reflections, so not much development needed. And for me Class Viewer is indispensable for rapid development, which now is usually on the app itself.

And being so close to the language, Class Viewer in a sense dynamically adjusts much with the Java language itself, so maintaining it is rather easy.

While it remains a useful tool for me I know as I use it, and for others, as continuing downloads over more than a decade support that view. And it has been for the most part a quiet and calm laid back thing with development for the over twelve years since I first put up on SourceForge.

Am MORE excited now though with some upcoming changes to the Java language, while also have some clean-up for Class Viewer itself as JApplet is deprecated, ending somewhat part of my vision for having something that can easily be put in a webpage. Class Viewer always has been aware of the web, and sees the web as resource, so its development in my mind includes if possible being a part of the web as well. Will see how that goes over time.

Making an application for Java developers that is VERY close to the Java language itself, and will admit I think it would be great if something like Class Viewer or the app itself ultimately became part of the language, is a really cool thing, where I have over a decade to see how cool it is.

Support for the application continues, where yes am aware is a single developer project, where wonder when that will change. For now is no pressure for it to be otherwise of which I'm aware, and 2017 should see some developments as the Java language itself evolves, and pushes up slightly on the Class Viewer app I built so close to it.