In Relation To

This is the second installment in a series of articles introducing the Ceylon language. Note that some features of the language may change before the final release.

InfoQ posted a video of my presentation in China. This being the first time I had ever tried to talk about the language in front of other people, I'm quite disfluent, and even say some stuff that isn't even correct. I certainly don't do a great job of explaining some things. Well, I'm sure that with all the conference invitations that have suddenly started filling up my inbox, I'll be getting plenty of practice. :-/

This is the first installment in a series of articles introducing the Ceylon language. Note that some features of the language may change before the final release.

There's a point I make in my Introducing the Ceylon Project presentation that's been widely misunderstood (perhaps mainly by people who're trying to misunderstand). Since I've been criticized over this in several venues, it merits a response. The offending statement is the following:

Alex Blewitt of InfoQ has published my answers to his questions about Ceylon.

So Marc Richards and then slashdot picked up on my presentations at InfoQ China. I wasn't quite expecting this level of exposure at this point, and I imagine that things will quiet down pretty quickly at least until we do an initial release of the compiler. All we have right now is a specification, an ANTLR grammar, and an incomplete type checker. Work on the backend bytecode generation is just beginning (though we'll be able to reuse a bunch of code from javac).

I'll be at QCon Beijing, talking about some stuff I've been working on. Wow, this is like my first conference talk for a very long time. A year and a half, I think...

Andy Gibson and Rick Hightower have announced the CDISource project.

Speechless.

Some people have wondered why CDI requires an explicit @Named annotation before a bean can be accessed using EL? Why not just give all beans names by default?