How to make a hacker hate his keyboard
Documentation, standardization. I almost ripped out my hand when writing those two words.
And still, that’s what is happening right now. Tired of asking questions on IRC about the ins and outs of the ooc language? Wish you could study it all by yourself in a dark corner of your room without feeling silly for asking questions that were asked a thousand time before?
Well, here you go: http://github.com/nddrylliog/the-ooc-language I’ve begun writing a ‘book’ that explains the features of ooc chapter by chapter. Some chapters are mostly about syntax and easy to comprehend (ie. properties) and some go more deeply into the crusty stuff (ie. covers vs classes) - don’t be intimidated if you have to read it more than once.
Now for the next shocking revelation: do you think the ooc community is fragmented? Are you afraid of the many SDKs lying around? Do you wake up covered in sweat crying “NOooooOOO! Not Tango/Phobos all over again!” and staring at your poster of Walter Bright, breathing slowly to calm down?
Then fear no more: http://github.com/ooc-lang/ooc-std Mark Fayngersh, aka the man known for making ooc-lang.org look good for 20 dollars and a few rubys (thanks Mark!) has decided it was about time that the ooc SDK was standardized. This is an incremental effort - you can contribute, your best bet is to come discuss about it with us on IRC (#ooc-lang channel, on Freenode). Thanks in advance for all your contributions.
In other news, I’ve been working on.. fixing bugs, implementing generic inlining (still experimental), pure ooc coroutines (ucontext-based, still debugging it), building to shared libraries and true partial recompilation (ie. faster compile times), and tons of other cool stuff. Man, I love working on ooc. And I love you all. Until the next time, enjoy!
