>>128
Chrome and Safari are both WebKit, so the current set of mainstream browser rendering engines really reduces down to IE's Trident, Firefox's Gekko, and all the WebKit shells.
>>129
Anonix reached the point where anoncoreutils was 50% complete (all my *nix systems have the utilities that were completed), but what lead to its demise was a decline in participation and motivation; it was a community project but interest waned. This (currently) isn't a community project, it's something I've been working on intermittently for the past couple of years. More importantly, the motivation for this is strong: every time I'm irritated by the browsers I use, I work on it for a little while. Anoncoreutils came out of the observation that GNU coreutils is bloated, and it was a source of irritation, but far less than that of the browsers available today. There are far more users of browsers, including those who have no idea what a command line is.
The decompiler/analysis system
is a source of income for me and quite a few others, so it wouldn't make sense to release that (yet). I am not aiming for 64k, I am aiming for 1MB. Didn't I say this before?
>>130
There is a lot of software I wish to rewrite, but the one that stands out to me due to how much use it gets and annoyance it has caused me is the browser. Unlike a bloated GNUtility that really ticks me off only when Chrome and Safari are both WebKit, so the current set of mainstream browser rendering engines really reduces down to IE, Firefox, and I do an
ls on the filesize or stumble on the sourcecode, the browser stands out whenever I use it.
I'm not specifically aiming at "low resource", but it just happens to be the easiest way of doing it, as a side-effect of omitting all useless complexity. I'm not asking for community help or anything (unless OP is still here; ideas would be nice). Maybe in another 2 years' time something interesting will appear, maybe not. That's the way that it goes, and it's what nobody knows.