Construction 70% Complete

LightFrame HQ has moved, and all the stuff has been transported from location A to location B. Unfortunately, all the stuff are in crates #0 through #59, including a new work desk that are in various Galant-labeled cardboard casings. Unfortunately LightFrame HQ will not be fitted with Aerons (the nearest outlet is about 200km away), although I would've loved some Hermann Meyer action over here.

Anyhow, the point remains that I have no place to work at, and the construction is not even complete (how I wish it would be C&C-easy). But, I'm certain that things settle in the nearest weeks. Until that, however, I probably still won't touch the codebase.

Hectoticket

Whoop whoop, LightFrame has got its hundredth ticket! Actually, I realized this a bit late, as there are already 107 of them. But better late than never, as they say. Hooray for me. I don't know where I got this inspiration to come up with and write new tickets, but it's never a bad thing.

This means first and foremost that I know that I have by work cut out for the future, and there's much to be done until I can claim it to be complete (whether it ever will become complete is an entirely different question).

We'll be moving to our new apartment next Friday. This means that I'm soon getting the time and space to actually code something new to LightFrame. Oh, god, how I've waited for that moment. Soon, soon...

Restate My Assumptions

To piggyback one of my favorite movies ever, here are some assumptions that keep me developing LightFrame (when I have the time and inspiration, naturally).

1. PHP is the most popular language used for websites among non-corporate efforts (e.g. hobby projects).
2. A considerable amount of PHP-based sites are not installed on freely manageable servers (e.g. webhotels).
3. Developers like popular frameworks like Ruby on Rails, but find it difficult to find proper hosting for required technology stacks. (Ruby in this case.)
4. In small-scale web projects, sacrificing some performance to gain convenience for the developer is an acceptable trade-off.
   

I might elaborate on the fourth point sometime. Now, it's beddy-bye for me.