It's all spinning wheels and self-doubt until the first pot of coffee.

Mochi's Basic

Oh, and I've been happily doing quite a bit more work lately using MochiKit. It just occurred to me this morning that I get a similar feeling from the added capabilities in JavaScript as I did back when I was around 12 or so and I first discovered Simons' Basic for my C64.

Ooh, you mean I get an else now? And procedures? And error trapping? And a calcluated GOTO? And basic graphics, sound, and I/O commands? And sprites designed with ASCII art? Holy crap, this is fun!

Archived Comments

  • It's a big overhead for a normal web page though. The compressed library is 90K.

  • That's why JavaScript libraries really need to be highly modular, with minimal dependency chains. It should be as easy as possible for me to use MochiKit.Async without loading any unnecessary code like MochiKit.Visual or MochiKit.LoggingPane.

  • @Dean: Well, the "packed" MochiKit single-include is 90K... gzip'ed, it's about 24K, which I hope would be the relevant number if mod_gzip is in use. Though the point is a good one: MochiKit-based sites certainly won't be winning the 5k page competition.

    @Matt: Actually, MochiKit is pretty modularized-- if you're not using the "packed" version. Each module (ie. Async, Base, Color, DOM, etc...) has a check right at the top to ensure that what it needs is available. Async, for example, only requires Base-- it doesn't need Visual or LoggingPane.

  • re: Simon's BASIC

    Yeah, but you have no idea how many times I typed "center" when it wanted "centre" and "color" when it wanted "colour".

    Had the same problems years later with STOS and GFA on my ST, and AMOS on the Amiga.