Skip to content
Triston J. Taylor edited this page Nov 6, 2013 · 4 revisions

JSE Stands for JavaScript Engine, which is what the application hopes to be. A Vehicle to drive your talent and knowledge with the advanced programming features of object oriented programming that most coders have become used to in the modern age.

As a script engine with runtime binding, JSE makes good on its name. The binary can be programmed on the fly to handle and innumerable number of tasks such as compiling binary application code and loading it at runtime provided the host system supports the tools employed by the engine controller (main JavaScript).

Command shells, GUIs, management scripts, you name it. JSE was built to take on many tasks by being the master of almost none. This platform focuses on the users building the technology they need to get things done instead of offering some giant cookie cutter kit that doesn't even cut cookies to fit.

I'm not all that dumb. I know many things about computers, electronics, chemistry, music, arts, philosophy, etc.. But what I know that I don't know, is that I don't know everything! That's where the users and the beauty of this system comes in. Users will create what they need using the software. They will optionally share it with others, who will in turn, adapt and improve upon their works and possibly continuing the sharing process, until what you have are some really rock solid tried and true operations libraries built by talented and knowledgeable individuals all over the world (uncompiled ready for on-site customization!)

Yeah, I get it. There are many command interpreters available. Yes. But I did not create them and they are all geared toward a specific mission unlike a language such as C which is general purpose. JavaScript is the defacto general purpose scripting language in my book. While there may be some implementations out there worth their salt, I don't use them. I've learned many a coding language in my time and JavaScript by far is my favorite. Simple, reliable and dynamic. No head-up-own ass syntax, overly complex constructs and the like that I usually turn away from as soon as I start reading about rubies, snakes, and perls!

So we have binary programming meets scripting. Oh how many times have I been at the command prompt wishing there were some bridge to some API that I couldn't get to. Well, those days for me are soon over my friends! Feel free to join the party. You know what they say about getting in on the ground level don't you? Well I don't but it must be pretty damned good. That's all I can see from where I am sitting.

Clone this wiki locally