Over a million developers have joined DZone.

Inq: New Scripting Language & Execution Environment for Java


Inq (www.inqwell.com) is a more than just a language - it's an application server and GUI environment for rapid development of distributed applications.

In recent years enterprise frameworks have come and come again. There has been much discussion of their benefits and promise of code reuse. As a developer I never saw much of this mythical reuse. I generally found myself implementing the same boiler plate code of database adapters and GUI table models over and over again.

I have generally worked in environments where feature creep would be a luxury - most often requirements are poorly specified and incomplete and the landscape subject to change by new regulations or client demand. Such is the world of the finance industry and yet systems have to be produced. When the world changes how does your design stand up? Do you throw it all away and start again or make-do-and-mend? How long will it take? How much will it cost?

IT departments attempt to mitigate the high cost of change by imposing strict requirements definition and a formal project process. But is that good enough? Does it actually solve the problems or just brush them under the carpet? When the chips are down the user is king and if making them conform to the methodology won't work what do you do? Answer - come up with a new methodology (or is it an old one?)

Inq is a new scripting language written in Java. It's a dynamic language that uses a node space and simple eval-based functions to model the real world. Node structures are built to order so relationships can be loose and allowed to evolve.

But Inq is also an execution environment for client and server. Its key features are:

  • Server-side atomic transactions and automatic instance locks
  • Complete insulation from SQL with full database implemention independence
  • Caching of database result sets
  • Events as transactions create, modify and destroy application type instances
  • A process architecture with conditional monitors for simpler concurrency handling
  • Easily laid-out GUIs with automatic binding of views to models

Inq is free to use. We developed it because we got bored and wanted to put the fun back into programming.

You are invited to learn more at www.inqwell.com



{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}