Unless you’ve been living under a rock, you can’t have missed the news that ComiXology released a new version of their mobile app that drastically changes how comics are purchased. It was reported on technology, gadget, Apple-related, and of course comicbook-related websites. It was even discussed heavily on RPG forums.
A summary of the situation is that:
- The iPad/iPhone app doesn’t have in-app purchases anymore — you’re forced to buy directly from the web by switching to Safari.
- The Android app still has in-app purchases, but as I understand it they don’t go through Google Play anymore and, instead, directly hit ComiXology’s servers.
Of course, the internet being what it is, a lot of people are pissed off and are voicing their rage on social networks. I’m not happy with the change either but I’m going to try and articulate my more moderate opinion in a few points here.
These past couple years my free time has been consumed by work on PieCrust,
Wikked, and, oh, yeah, having 2 kids and 2 cats (what I was thinking, I
don’t know). As a result, I haven’t been playing music or drawing much, which I miss a lot.
So I started doing it at work. Well, not playing music, because a drumset in
the middle of the open-space would probably be frowned upon, but drawing and
The result is a whole bunch of post-it notes with some pretty decent art, which
I’ve collected over on a “Meeting Notes” page. Check it out!
Since I announced Wikked here, I’ve been mostly working on fixing bugs, editing the documentation, and evaluating its performance — which is what we’ll look at here today.
The big question I wanted to answer was how far you can go with just the default configuration, which is based on SQLite and requires no setup from the user. The reason for this was twofold:
- I needed to write some advice in the documentation about when you should start looking into more sophisticated setups.
- I plan to setup a public test wiki where people can try Wikked directly, and I needed to know if it would go down after I post the link on Reddit or HackerNews.
There hasn’t been any updates on this blog for a few months, and there was a good reason for that: I was working on someting new.
The problem is that I was trying to get this new project to a “good enough” state to launch publicly… but somehow I ended up in a seemingly infinite loop of improvements, refactorings, and bug fixing.
Eventually I snapped out of it: fuck it, let’s launch it as is, and see if anybody cares enough to complain that it’s not good enough. I wrote some basic documentation, fought with
setuptools for packaging, and uploaded it to the Python package server.
So lo and behold, here is Wikked, a wiki engine entirely managed with text files sitting in a revision control system.
I think it’s pretty cool, so come read more about it after the break!
It’s been long overdue, since PieCrust 1.0 was released more than 4 months ago, but at last it’s here: PieCrust 1.1!
Every time I figure I will go with a “release small, release often” kind of philosophy, I still end up with more of a “wait, I’ll just get this last feature ready first” kind of vicious circle… sigh.
Anyway, grab the new release, or keep reading if you want to know about the most important changes. As always, big thanks go to the people who reported bugs and/or helped fix them, or generally participated in the evolution of PieCrust.