The wrong answer is the right answer

[brentdax]

So, I'm working on a programming project that I will only publicly call "Knightley". (I've spoken much more about it to a few select friends, but it's a relatively clever idea, so I'm not willing to blab about it to just anybody.) It's a web-based project that involves, among other things, annotating user-submitted HTML with custom XML tags and

Comments

[acdragonmaster]

Well, if you're willing to invest the time in meticulously making sure the "nasty" system works, I'd say by all means go for it. Just make sure to give it plenty of time to play around with and test and be given to other people to abuse for you, and probably have one of the other systems ready as a backup in case you need it.

[sangochan]

Use the nasty system.

Just because it's nasty doesn't mean it's not the answer. Hacking, you know?

Just try and hack the hack. Make sure that you've got a decent back-up or recover-from-fuck-up in place.

[codepoetica]

Well, you can still use the slow alternative for batch conformance testing the fast nasty version, if you go that way.

Assuming the results of this regex transformation can be stored decently, such as back to a database, for logging, and the associated source later reparsed by the slow library. Would make for a decent sanity spotcheck, either in development or live-maintenance.

You're going to be giving up XML validation.

[meagenimage]

Damn, dude... you're like an epic hacker to me. The cleverest thing I've done with code this summer was a PHP/MySQL dynamic event calendar for a website. (And it *was* rather clever, especially the logon feature, but I digress...)

[ext_880]

Epic she says! ^o^

[chiave_trust]

The number of cutegirls proclaiming Brent's epic-ness is increasing.