Atomic OS: Take Two - Part One

by Scott Elcomb Email

Over the last few months my pet project "Atomic OS" has been completely refactored. And I mean completely. Right down to the very premise of the project.

Follow up:

The reason for these changes is that, believe it or not, the concept is nearly five years old. There have been lots and lots of improvements in DHTML (er... AJAX now) over this period.

The project summary on SourceForge currently reads:

Atomic OS is a responsive Web 2.0 operating environment & development platform. Based on AJAX techniques, it emulates/provides standard operating system features including a command-line shell, interpreter, filesystem, database access and GUI services.

While the intent will still be the same in spirit, I've finally come to the conclusion that my code won't and can't do everything. This thought led to the stripping-down of every idea, concept, and desire to the bare minimum.

Another change in the works starts with this blog. In an effort to "join the FOSS movement," I created this project way to early and without the benefit of experience. I very nearly killed it. Several times. Need to fix that.

So, today my intention is to develop a new iteration of Atomic OS following a pattern that was, to my mind at least, most effectively portrayed by Dr. Jack Crenshaw's "Let's Build A Compiler!" tutorial series. I will blog during the development of the next Atomic OS core and try to explain why certain decisions are made.

Tomorrow (literally speaking), I will release WASH-SE (the Web Application SHell - Simplified Edition) along with a blog post describing what is, does, and why WASH is so fundamentally important to the Atomic OS project.

Tomorrow (figuratively speaking), it's my intention to integrate Atomic OS with other stunning web development libraries and applications. Specifically, I'd like to look at integration with:
TiddlyWiki, the Lively Kernel, ExtJS, and OAT.

Well that's it for now. If you found my site via the Atomic OS project, I hope you'll join me tomorrow. I welcome your feedback. Cheers!