sab39

... indistinguishable from magic
effing the ineffable since 1977

Categories

Recent Posts

Archives

You're a circle!

9/28/2007
Usually, Alexa and Luke come over every weekend, alternating between just Saturday morning and the whole weekend from Friday night to Sunday. They really seem to enjoy their trips to "Daddy house" which of course makes me very happy. Here are some random bits of cuteness from the past few months.


Luke threw a bowl of chili on the floor when he was done eating it and got it all over the carpet. So I was rather annoyed and being all stern mean Daddy, and told him he had to sit in the chair until I was done cleaning it up, and THEN he'd go in timeout. So after ten minutes of me grumpily going over the large area of carpet that was splattered in chili, trying to get it clean, muttering under my breath (and still not close to finished) he looks at me and says in the sweetest innocentest voice - "Hey! Daddy house! Watcha doin?"

(Yes, he still went in timeout as promised. But I was a little less grumpy after that)

***

After Alexa gets done in the bath I get her big fluffy yellow towel and start drying her off. When I get to her face I make a big show of drying her face off all energetically, especially her nose. Then I start drying off the rest of her. But every 5 seconds during the process she giggles and says "Nose, please!". And I have to dry her nose again.

Or sometimes I'll just grab it and hold it until she wriggles free, just for fun :)

***

Luke was still taking a bottle at night up until a few months ago, and it got to the point where that particular battle needed to be fought. So during the day I explained to him he was a big boy and didn't need a bottle any more, and asked him to put his bottles in the trashcan, which he dutifully and happily did. Then bedtime came around and as soon as he was put into bed he started crying for a bottle. The conversation went something like this:

Luke: "Want bottle!"
Me: "You can't have a bottle, Luke, you threw them away because you're a big boy, remember?"
Luke: "No! Tiny baby!"
Me: "But tiny babies don't get to ride on the choo choo trains, do they?"
Luke: "No"
Me: "And tiny babies don't go to the playground, do they?"
Luke: "No"
Me: "And tiny babies don't get to play with cars do they?"
Luke: "No"
Me: "So you're a big boy, right?"
Luke: "Right"
Me: "And you don't need a bottle, right?"
Luke (crying again): "Want bottle!"
Me: "You don't need a bottle, cos you're a big boy!"
Luke: "No, tiny baby!"
Me: "I think this conversation is going in circles."
Luke (uber whiny): "YOU'RE a circle!"
Me (leaving the room while valiantly trying not to crack up): "Goodnight, Luke, I love you."

***

Alexa has learnt that if she hurts herself she'll get a kiss better. Of course if she ASKED for a kiss she'd also get a kiss, but she prefers to come up to you like this:
Alexa: "Hurtcha elbow"
Me: "Awww" *kiss*
Alexa: "Hurtcha leg"
Me: "You hurt your leg too? Awww" *kiss*
Alexa: "Hurtcha nose!"
Me: "I don't think you really hurt your nose, you just want kisses" *kiss*
Alexa: "Hurtcha fingers! Hurtcha feet! Hurtcha cheeks!"
Me: "Now you're just being silly." *kiss* *kiss* *kiss*

***

Me: "Luke, drink your juice."
Luke: "I can't WANT to drinka juice!" ("can't want to", I love that, as if he'd really LIKE to want to, but just can't)
Me: "Why not?" (this was one of Luke's favorite phrases at the time, I thought I might outsmart him by turning it around on him)
Luke: "Cuz... NO!"

(oh, and this also seems like the best place to mention what he says when he really DOES want to drink what he's been given. "This is very thirsty!")

***

I was reading them "Love you forever" and on one of the pages the little boy in the story has left a dirty handprint. Luke pointed at it and said "A clue!"

***

One more. Luke again (Alexa is just as adorable, but since Luke's language development has now clearly surpassed hers, she's adorable in less verbal ways, that are less bloggable). I'd been watching some Thomas the Tank Engine (or "Thomas the train!") videos with them on Youtube and then we had lunch. While I was making lunch I merrily sang the Thomas theme music.

Luke: "Stop singing!"
Me: "I can't sing? Why not?"
Luke: "Cuz... no singing!"
Me: "But I want to sing!"
Luke: "No singing Thomas the Train song!"
Me: "Ok, what can I sing? Can I sing this?" *starts singing one of the songs from OMWF*
Luke: "No singing Buffies!"
Me: "How about, can I sing this?" *starts singing some Ben Folds*
Luke: "No singing!"
Me: "Ok then, what can I sing, Luke?"
Luke (thinking hard): "Hmm... sing... Thomas the Train song!"

 

The reinvigoration of Classpath?

9/21/2007
(Disclaimer: I'm just observing all this from the sidelines; my opinion is almost entirely derived from Planet Classpath and the Classpath mailing lists. If I'm wrong on some salient point, please comment and let me know!)

I'm very pleased to see that the Classpath project seems to be picking up some of the steam it lost on the announcement of OpenJDK. I have mixed feelings about OpenJDK itself: on the one hand, Sun did exactly the right thing by releasing the JDK under the best possible choice of license as we'd all wanted for years; on the other hand, I've seen at least two blog entries on Planet Classpath in the past week that were variations on "hooray, the trivial patch I submitted to OpenJDK the week it was released has been accepted a mere three months later!"

IcedTea appears to have picked up some of this slack and last I heard had built a mostly-working Java implementation by plugging in Classpath code to fill the holes in OpenJDK. Haven't heard much about it lately though - has development stalled or are people just not blogging about it?

However, part of me feels that IcedTea is approaching the problem from the wrong end. The code that the Classpath developers have labored over for ten years deserves a higher place than being used as filler to patch the holes in an inferior, ex-proprietary codebase. I'm not trying to argue that Sun's code is "bad" or that Classpath's code is perfect, but I do know that code developed in the bright light of public view, with no schedule pressures other than "when it's right", is invariably [UPDATED: Jeroen points out in the comments that this isn't so invariable after all] higher quality than code developed inside a large, bureaucratic organization with constant pressure to ship to a deadline. The fact that these things have historically affected Java's development is apparent in the public API: public members whose types are nonpublic, public RCSID fields, serialVersionUID fields defined on interfaces.

The difference is apparent in the sheer size of the codebases - the JDK is several times the size of Classpath, despite Classpath providing the vast majority of the same level of functionality. (I'm actually considering sticking with an older version of IKVM for this reason - file size matters when you're building an installer that's being shipped over the network). It's apparent in the fact that Classpath has a clean API for targeting multiple VMs including VMs for which native code is unnecessary, where the JDK's VM interface is internal and relies heavily on native code.

It seems to me that there would be a lot of value in approaching an OpenJDK / Classpath merge in the same way the libgcj and Kaffe merges were approached: compare the code on a class-by-class basis, bring in whichever implementation is best, and change it if necessary to account for things the other implementation did better. My gut instinct says a lot more Classpath code would survive that process than is surviving today in IcedTea - and the end result would be significantly smaller, cleaner, faster and bug-free-er.

I don't know whether the copyright ownership issues have been resolved yet to make it possible to actually pull OpenJDK code directly into Classpath though.

Regardless of what approach ends up being taken, though, it's good to see work happening on Classpath again, and a new release being contemplated. I guess it means I need to get those darn Japi runs happening again though!

 

Confused but Japi

9/20/2007
The Japi runs for the last couple of days have gotten very confused. Yesterday they started believing that JDK7 had no classes in it; now they seem to believe that Classpath doesn't.

I'm not sure what's going on just yet, and I haven't yet had time to do any actual investigation. In the meantime, I killed today's run as soon as I noticed what was going on; no Harmony results today because I'm almost sure they'd have been bogus anyway.

I'll keep you posted.

 

Let's moon 'em!

9/13/2007

I make no secret of the fact that I'm really excited about the private sector finally getting into the spaceflight business. I consider SpaceShipOne's historic flight to win the X-Prize to be one of the more significant historical events in my lifetime. Watching SpaceX's Falcon rocket almost reach orbit gave me chills. If one day I get the chance to ride Virgin Galactic to a Bigelow space hotel, I'm SO there. And mankind just bloody better have colonized Mars by the time I die or I'll be pissed.

When the rumors started about a new X-Prize I was assuming that it would be for orbit. After all, as critics were quick to point out, SpaceShipOne's achievement, while impressive, was a LONG way short of what orbit would require - and orbit is kind of a prerequisite to getting anywhere else.

But nope. With the help of Google they've gone one better - the new X-Prize will be $30 million for putting a robotic lander on the moon. Impressive! I wonder how long it'll take to be won...


 
RSS