I do a bit better when I've had a decent night's sleep and haven't spent the day on a trade-show floor. This was "Timothy finds Jesse standing around and asks him stuff" and not "interview with an agenda."

That being said, I totally need to learn a bit about concise speaking. Also, thanks :)

See http://hardware.slashdot.org/comments.pl?sid=5449405&cid=47526135, but, uh. I never even vaguely meant to imply we'd be crazy enough to build keyswitches out of wood.

Hi, jesse of keyboardio here.

As of this week, the editors actually have it more correct than our website. We'd been prototyping in wood. In between when the video was shot last month and when this got posted, we finally got our first "finalish" aluminum prototype made. The aluminum prototype was what we talked about publicly on Highway1 (highway1.io) demo day and what we hoped to launch publicly. Once we had it in hand, we discovered a bunch of reasons we're not going to go with aluminum for production. (Mostly, cost, Weight, looking too much like an Apple product, weight, and weight.) We went back to the drawing board and believe we've got techniques, technologies and costs for commercial manufacture of a milled wood enclosure. We've been at OSCON this week, but should get the website updated soonish.

God no. Someone actually offered to sell us some endangered hardwood for the keyboards the other day. The plan is for something reasonably, pretty, reasonably hard, reasonably sustainable and reasonably inexpensive. N

I designed this just a couple weeks ago:

http://blog.fsck.com/2013/01/pinkies-and-your-brain.html

I've been using it and am fairly happy with it.

What I did was to get a Jaunty _chroot_ running on the Kindle 2. The interesting bits were mostly around making X work and beating the 5-pad into submission.

Longstaff,

3 seconds to iterate over the queue list sounds _broken_. I know you're no longer with that employer, but I'd encourage anybody else running into performance issues like that to bring them up on The rt-users mailinglist. There are plenty of folks who've probably seen and work through whatever it is that you're running into. And I'd much rather get scalability issues aired publicly in an rt-related forum where the community can work together to improve matters than have multiple sysadmins, DBAs and programmers struggle in silence.

Readers might want to take my comments with a grain of salt, as I'm RT's original author and chief architect. I routinely work with clients with RT instances that are well over 100,000 tickets. When using any large application at scale, you're going to need to invest time in performance tuning, but 100k tickets isn't "big" for an RT instance. With a single front end box and a single backend (untuned, but beefy) DB server, I've seen an RT server doing 10,000 tickets on a slow day, bursting to 25,000 with several million in the database.