As yet there's no community here, but there might be later, after support for users is added. You only get user rights explicitly granted to you: none as of today. Unless the rules change, nothing here is yours. If you submit email, you also grant a perpetual license to freely edit, print and reprint email as briarpig likes.
Please do not request free labor. As long as you get things here free, it's fairly offensive to ask for more. Why not donate your own time for free instead?
Request no commentary from briarpig on anything, not even to judge beauty contests for pigs. It's still a request for free labor, even if intended flattering. (By now you might be peeved at briarpig's dim view of your scruples and manners. Apologies instantly offered to any saints of the internet slumming in this quarter.)
Software developers, please suppress any urge to treat your personal taste as a universal rule for judging what is right, proper, and true. Be more open.
Occasional creative writing might aggressively sell Briar Pig as if a real being. Anyone failing to see humor in this will be summarily accused of stupidity. Aiming for a PG rating, vulgar language is not allowed, but euphemisms may be used. Briar Pig blurts phrases in native Pigese, shown in pseudo (not pig) latin.
I preview most of this site with Opera. So if a page looks miserable under some other browser, you might try Opera as a last resort, until I fix whatever causes problems later.
I'm a programmer pushing 50 years of age. Here I'll discuss code. This site's not about me. I enjoy email very little. I prefer to code & document — private email simply isn't worth the time. Let's make a deal: only email what I can publish. I'll edit and reword any email printed, with lightly obscured addresses.
Personal questions, language advocacy, and long harangues are all unwelcome. Be crisp and to the point. Ask few questions (and none at all starting with who, when, or why). I censor all link spam unrelated to language implementation.
Email about me is rarely fit to print: this is not a vanity site. If I tell personal stories or describe past jobs, email about them (not me) might work. My nods to personal perspective help ground my stories in reality. But it's context only. I'm just an example, not the subject, to help you better "consider the source" when reading.
In particular, neither my state of mind (what I'm thinking) nor my prospects (your analysis or mine) are things I like to discuss, except when limited to software I write. What I think about programming languages is fair game, as is any line of reasoning behind code I show or mention tangentially. But status of personal life and work are off limits.
Choose one of these demos for sample code and related docs, developed together to motivate þ C++ code for this purpose.
mu: toy, peg, imm, tag, box, symbol, token, number, bigint, class, method, reader, writer, eval, env, vm, gc, world, pcode, compiler, asm, lathe, lisp, smalltalk, design, weight, jar, card, harp, debug, profile
thorn: todo, names, iovec, assert, log, run, hex, crc, buf, in, out, quote, escape, compare, file, deck, cow, arc, blob, tree, slice, rand, time, stat, heap, node, primes, page, book, pile, stack, atomic, lock, mutex, thread, map, meter, list, iter, ctype
The new mu menu links future toy language pages. Many demos are stubs; see todo for a thorn demo guide, or toy for mu updates. Also see names for an overview of naming schemes.
You might wonder: what's this site about? What am I up to here? Well, several things, all related, along with an obligatory blog — log — for news, updated no more often than once a day, no less often than every several days. (Please poll seldom with robots.)
The "several related things" involve:
- dynamic programming languages (λσπ)
- þ common runtime library (thorn)
- naming convention busting (names)
- rich internet application support (gui)
- scripted generation of websites (wyv)
- Plan9-ish mounts & namespaces (wyv)
- (maybe) Hypercard-esque web stacks
- website sandbox for sons to code & play
But since this list will take some time to flesh out with plain language sketches, those pages linked above might not fill faster than several percent a week. (Patience: check the log for news.)
My main short term goal is bringing up Scheme on top of þ, so I can start teaching my sons to code with enough progress on a web page framework to let them cut their teeth on that, once they get the general idea of code.
Update: see these log entries for steering corrections:
- 27Oct2007 - event-driven scripting support
Briar Pig is a character I invented, based on the tale about three little pigs who, as you recall, built houses of straw, sticks, and bricks. In the traditional version, the third pig survives, but not in the version told here. Briar Pig styles himself the seventh and final little pig, who built a house in a briar patch. Details can wait.
When I post on your site, I'll only use briarpig or one of my names. Otherwise, it's not me posting. I have better things to do than play games on your site.
I lack interest in link exchange. But I'll take links on programming language implementation. You'll rarely get a link published here unless the other end shows or discusses low level coding.
An address exists for mailing lists (etc), but it's reserved for friends or project acquaintances. If you email david (at) briarpig (dot) com, but I don't know you, I may treat it as sent to briarpig at either of the public addresses. Update: as of February 2008 I plan to check the briarpig email addresses at yahoo and gmail very rarely because I don't get email there, so it's a waste of time to look. See demos for recent material.
fineprint « Þ
