Wayback Machine - InformationWeek

InformationWeek is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

IoT
IoT
Government // Enterprise Architecture
Commentary
10/30/2008
12:00 AM
Commentary
Commentary
Commentary
50%
50%

Wayback Machine

It is interesting to look back at one's own code from years ago. It's like having one's own Wayback Machine.

It is interesting to look back at one's own code from years ago. It's like having one's own Wayback Machine.

FIJI the ForthIsh Java Interpreter is open source I started in 1998, posted in 1999, and updated in 2001. Scripting Java was hot stuff and FIJI garnered some notice inside and outside Sun. Downloads have continued over the years but nothing like an active FIJI community grew. I stopped working much on FIJI by 2002.

This year I wrote PigIron which deals with mainframe administrative automation. Since this stuff can format the disks, create users, etc., you can imagine it's pretty complex to test in an automated fashion. I turned to Open ObjectRexx plus BSF4Rexx.

Then a funny thing happened. Having returned to serious coding after years of team leading, the simplicity bug bit again. Ditched OpenSolaris with Gnome and KDE. Back to OpenBSD with DWM . And discovered this bug in OpenObjectRexx on OpenBSD that I traced through for days ...

I switched to FIJI for testing PigIron. I started writing in Java in 1997 because it simplified my life, specifically portability. Why was I maintaining someone else's complicated albeit lovely open source tool when I had my own much simpler code, FIJI, for the same tasks?

How good is FIJI anyway? I'd certainly spent many more hours coding Rexx than FIJI. FIJI is certainly simpler, the way Forth is always simpler. You don't spend time declaring stuff and then implementing it and then calling it. You name something. My fingers appreciate the smaller number of key impacts. But is FIJI really all there?

I kept finding gaps in FIJI, dusting off the source, starting to code. Then I'd discover that actually everything was already there. I checked in a few changes, none of which were really necessary. Re-reading the manual that this younger me authored, I remembered how simple it was.

FIJI is weird but solid. It never yet learned to save compiled wordlists but someday I'll fix that. If anyone ever needs it.

We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.
Comment  | 
Print  | 
More Insights
Commentary
Get Your Enterprise Ready for 5G
Mary E. Shacklett, Mary E. Shacklett,  1/14/2020
Commentary
Modern App Dev: An Enterprise Guide
Cathleen Gagne, Managing Editor, InformationWeek,  1/5/2020
Slideshows
9 Ways to Improve IT and Operational Efficiencies in 2020
Cynthia Harvey, Freelance Journalist, InformationWeek,  1/2/2020
White Papers
Register for InformationWeek Newsletters
Video
Current Issue
The Cloud Gets Ready for the 20's
This IT Trend Report explores how cloud computing is being shaped for the next phase in its maturation. It will help enterprise IT decision makers and business leaders understand some of the key trends reflected emerging cloud concepts and technologies, and in enterprise cloud usage patterns. Get it today!
Slideshows
Flash Poll