Blog of the Hibernate project and its developers, including Gavin King, covering Hibernate releases and his Ceylon language articles.
HN links it for Hibernate release news and Gavin King's Ceylon writing; one commenter quotes King's replies on Ceylon syntax when explaining why they chose Kotlin.
I can tell you my main reason for going with Kotlin after looking into Ceylon[1]:
14. Apr 2011, 01:44 CET Gavin King | gavin.king(AT)gmail.com
> 1. 'variable' keyword is to long use var instead
We've so far avoided abbreviations. In practice the IDE will
type this annotation name for me.
I don't want a language designed to require an IDE – if the language is so cumbersome that you need a tool to write it for you, then you might as well just use Java. With Kotlin, I can write in Emacs if I feel like it, since being concise is one of their explicit design goals.
(Ironic, I guess, that the language developed by an IDE vendor is the better one to use without an IDE.)
Edit: To elaborate, the Ceylon docs say[2] that "one of the goals of the language is for most code to be immediately readable to people who aren't Ceylon programmers, and who haven't studied the syntax of the language."
I think this is a very misguided goal. No programmer is going to be confused about what "var" means, so making everyone type "variable" gains you nothing. And at the same time, that very same introduction page has plenty of syntax that you won't understand without studying it first, so it still wouldn't achieve their aim, even if those concessions to verbosity had somehow helped.
[1] http://in.relation.to/2011/04/13/ceylon/
[2] https://www.ceylon-lang.org/documentation/current/introduction/
http://in.relation.to/Bloggers/FirstHibernateOGMReleaseAka41Final