Sam Ruby: Sometimes the dragon wins. Not here: ɥɦɐ. And you can search for it.
My dirty little secret, however, is that I'm storing everything in MySQL in fields declared to be encoded in latin1, storing UTF-8 in there anyway, and trusting the browser to get Unicode right. I've tried storing everything in Unicode-encoded fields in MySQL, but it mangled some of the rarer characters when I tried to convert this post once my host upgraded to MySQL 4.0 or 4.1 (whichever one first supported Unicode fields). Some characters worked, some didn't. My only guess is that MySQL only handled an older version of Unicode and stripped everything it didn't understand.
I've decided that my wiki has long since been dead. Editing has been disabled for a while, and I don't even remember whether that was an accident or not (i.e. whether I was working on the software and left it broken (and whether that was intentional or not) or whether I just decided to disable it). Public editing just did more harm than good (extraneous pages were created, comments would be left I didn't need, and discussions would form (and a wiki isn't a good place to conduct a discussion)).
But, I still want a place to put random pages. So, should I:
- Put all random pages at my root (i.e. right under keithdevens.com/)?
- Clean up the /wiki and put all random pages there?
- Create a new namespace like /pages and put random pages there?
I'm leaning towards A because:
- I already have certain content pages at my root, such as the pages in my tabbed navigation at the top
- Even though they're at the root, random pages can still have structured (i.e. nested) URLs
- Why have the extra nesting of a /pages or a /wiki? It's like "of course they're 'pages'. They're on your web site, after all". Or alternatively, "Huh? /wiki, but uneditable pages?"
Chris Langreiter puts all his stuff under "space". Ian Bicking puts all his stuff at the root, but that's the root of blog.ianbicking.org so that doesn't count. Main reasons I'm reluctant to choose A are:
- It pollutes my root namespace and seems "messy" to me
- Lots of little pages at the root make trivial little pages as important, as far as the URL is concerned, as important pages like /about or /software
- I feel like it's hard to change to something else later if I do it this way
Opinions very welcome.
Which do you think is the more appropriate behavior for escapes that aren't escapes in your programming language: Say you have an escape that doesn't mean anything, like "\g". Should your programming language turn that into "g" or leave it as just "\g"?
$>python -c "print \"\g\""
\g
$>perl -e "print \"\g\""
g
$>ruby -e "print \"\g\""
g
$>php -r "print \"\g\";"
\g
$>lua -e "print \"\g\""
g
$>cat test.c
#include<stdio.h>
int main(){printf("\g");}
$>gcc test.c
test.c:2:19: warning: unknown escape sequence '\g'
$>a
g
$>MzScheme -e "(display \"\g\")"
Welcome to MzScheme version 299.400...
#f::9: read: unknown escape sequence \g in string
> ^Z
Anyone want to test C# and Java for me (since I don't have the interpreters on my system)? More importantly, want to tell me which you prefer? What does JSON do? (Update: it's not defined in JSON, but an alert("\g") in Firefox's JS console gives 'g').
Friday, November 4, 2005
Permalink
Spider solitaire
To answer an earlier question, I amalmost certain every game can bebeat. ...
Jared: Jul 16, 2:20pm