Script editors and IDEs can excite fiery passion or yawning boredom amongst coders. Like any craftsman, we get excited over a good tool. Once we learn the intricacies and idiosyncrasies, we're bored by any tool that doesn't offer us something extraordinary to compensate us for the cost of having to retrain our fingers and brains to use it. (And, the older we get, the more compensation we require.)

You could probably spend a lifetime scouring the Internet, trying out all the free and cheap editors, from those designed for a single language to completely generic setups. The trade-off, as you move from the specific to more general, is that the tool is often less useful for any given language; yet it gives you the benefit using your acquired skills with the tool, regardless of context.

Bravely attempting to straddle the gap is PrimalScript 4. Now, the folks at Sapien might not appreciate PrimalScript being called a “script editor.” In fairness, it's much closer to a full-blown IDE than it is to your typical notepad replacement. The balancing act, here, is to provide you with a tool that allows you to easily create, edit, test, and even debug and install all your scripts, from a tool that causes little more apparent strain than notepad. So, is it successful?

There's no question that it's lightweight, in the best sense of the word. As for whether it's capable enough to replace your editors for any of the 30+ languages it supports, the answer is: maybe. Let's take a look at the whys and wherefores as they apply to PrimalScript 4 Professional (PS4).

PrimalScript installs quickly and cleanly, and works out-of-the-box with many existing language installations. Significantly, the IDE loads and unloads quickly. Actually, it does just about everything in a sprightly fashion which, when you get down to it, is probably the primary criterion for any scripting environment. As a feature, it ties only with keyboard-friendliness—another area in which PrimalScript excels.

From there, you get a clean, familiar setup. Menu bars and tool bars along the top, code editor in the middle flanked by two “nexuses.” A nexus, in PrimalScript terms, is an explorer-type window that shows you various facets of the environment, which we'll talk about in a little bit.

One problem with having a such an ordinary-looking interface like this is that it's inherently underwhelming. One has a sense of “been there, done that” which the IDE has to overcome to make an impression. So, let's look at some of those impressions.