Why bother with Frontier again?

I’ve asked myself the question “Why bother with Frontier?” many times in the last month.  I spent some time talking to people on the Frontier Kernel mailing list about getting involved with the project again.  I learned many things, including the fact that I’m not qualified to help in a meaningful way right now.  Sometimes knowing your limits is as important as knowing your strengths.  In my case, I would need to learn 10 years of C coding to catch up to the complicated environment that is the Frontier kernel.

I think instead I’ll spend my time building the software that I want instead of trying to fix the issues with the existing project.  There are many things about the Frontier coding environment that are appealing:

  1. Editing code in an outliner
  2. Scripting applications to automate tasks
  3. Building applications that work on more than one platform

That said, I think that I can build my own software while addressing my shortcomings.  I have the books and the tools to learn C, compile programs and run them under MacOS X and Windows.  I have the motivation to learn and some spare time.

So, why bother with Frontier again?  Why indeed.