I'm not completely sold on the syntax, but I find the design and runtime interesting. I'd like to find an excuse to build something with it, to see if it can live up to its potential.
I started thinking about how I would design a language recently, then I came across rust, and I saw quite a lot of the same conclusions I came to myself. Abstract classes, multiple inheritance, Interfaces with versioning, combining 3rd party libraries... With rust, you define the layout of memory without inheritance, and the implementation of interfaces for types without defining the layout of memory. Neatly side-stepping some of the issues faced by other languages.
All resources and object lifetimes are managed, avoiding
Since there's no NULL, there's no NullPointerException. There's no unchecked exceptions, or any exceptions at all for that matter. Though, I might prefer to have them. Sure, there's the try! macro. But that's just syntactic sugar for checking the return code of every function.
If your machine is not connected to an atomic clock, your measurement in UTC is likely to be slightly off anyway. So tweaking the rate of time passing so that every day has the same number of seconds is a reasonable compromise. I remember hearing that google do this in their data centres.
If you do have a local atomic clock, record timestamps against TAI and convert to UTC. But even there you have to deal with clock drift, though the error bar should be much smaller.