The idea for a modern _(Forth) *(OS) has been kicking around since maybe 1995. It's popular with folks who want a simple, understandable _(OS). Anyway, feel free to add your ideas here (see _(Text Formatting) for info on TUNES CLiki formatting rules).

Traditionally _(Forth) _(OS)es are _(no-kernel) systems, but recent incarnations are integrated with "modern" _(OS)es _(kernel)s and so they have usual _(protection) barriers.

Projects:
<ul class="implementations">
  <h2>IBM PC (Intel Architecture)</h2>
  <li>_(Retro Native Forth | Retro).</li>
  <li>_(BootOS | BootOS) (_(old | http://mak.chat.ru ), _("at FIG RU" | http://wiki.forth.org.ru/BootOS)).</li>
  <li>_("Enth & Flux" | http://www.ynet.com.au/sean/) (lots of experimental Color Forth type stuff).</li>
  <li>_(colorForth | http://www.colorforth.com) _(Chuck Moore)'s _(Forth) _(OS).</li>
  <li>_(ZOG | http://www.dedasys.com/freesoftware/zog.html) is _(FICL) on top of _(eCos).</li>
  <li>_(SOL | http://www.not-compatible.org/SOL/index.html) is a small, _(FORTH)-like language and _(OS). It currently runs on 8086-based PCs with at least 64K bytes of RAM.</li>
  <li>_(4IM | http://membres.lycos.fr/astrobe/) is a Forth system that can run standalone or in DOS.</li>
  <li>_(ForthOS | http://www.forthos.org/) started out as a port of eForth by _(Andy Valencia) to the x86 architecture in 32-bit mode, more recently, this work was dusted off to adapt it to the GRand Unified Bootloader, also known as "GRUB". While this was easily done, the itch was irresistable to spruce up the environment a bit... the result is ForthOS.</li>
<hr>
  <h2>Non-PC</h2>
  <li>_(Aha | http://www.ultratechnology.com/aha.htm) Jeff Fox's project for the F21 processor.</li>
  <li>_("JPB Forth" | http://jpb.forth.free.fr/Anglais/encadrement.html) a M68000 based _(Forth) system (hardware + software) with _(GUI).</li>
<hr>
  <h2>Other Platforms</h2>
  <li>_(IsForth | http://isforth.clss.net) (for _(Unix)/_(Linux)).</li>
  <li>_(H3rL | ftp://linux01.gwdg.de/pub/cLIeNUX/interim/ABOUT) Hohensee's 3-ring Linux, a _(Forth)-like language in the _(Linux) _(kernel).</li>
<hr>
  <h2>Project Proposals</h2>
  <li>_("OS/Forth" | http://www.forth.org/svfig/osf.html) a proposal at SVFIG _("old mirror" | http://twister.pp.ru:8100/tech/OS4th/).</li>
<hr>
  <h2>Missing in Action (_(MIA))</h2>
  <li>_(4os | http://www.itvc.com/Technology/4os.htm) proprietary _(OS) intended to run on _(MISC)-based set-top-box. _(Mirror | http://web.archive.org/web/19991022233047/www.itvc.com/Technology/4os.htm)</li>
  <li>_(COLDFORTH | http://coldforth.teegra.net). _("Mirror"|http://web.archive.org/web/20020527124246/http://coldforth.teegra.net/)</li>
</ul>

Goals for a basic _(Forth) _(OS):
<ul>
  <li>Boot up in a split second.</li>
  <li>Use a small portion of a floppy.</li>
  <li>_(Assembler|assembly)/metacompiler so it can recompile itself.</li>
  <li>_(Block Editor), etc.. for a complete development environment.</li>
  <li>Simple, efficient</li>
</ul>

Additional goals for a more powerful _(Forth) _(OS):
<ul>
  <li>Support common hardware (hard/cd/floppy drives, usb, video, etc)</li>
  <li>Graphical interface</li>
  <li>Network and internet support</li>
  <li>Web browser/email</li>
  <li>Other applications</li>
</ul>

Blocks vs. Filesystems?
<ul>
<li>Do both? Say, 240 blocks on a floppy, 1200k for files.</li>
<li>Just using BLOCKS would be simpler and easier to implement</li>
</ul>
