flitzwald

Really nice demo. But there's one semi-unrelated thing I noticed (disclaimer: yeah, I don't like Flash either, but): This demo, with a handful of animated bezier curves drove one CPU to 40% (using Chrome on a Mac). And this is something that I repeatedly encountered with graphics rendering done in Javascript. The whole "less flash"="less cpu-usage with animation"-thing might be a little premature.

Ah, I get it. Convenient container-syntax is only found in toy scripting languages for stupid people like -uh- Haskell? :)

There is one thing in Objective-C that still gets my goat, even after 8 years of working with it: it's the lack of syntax for container-types:

[NSMutableDictionary dictionaryWithConstructorIDontWantToType:...]

is just a huge pain in the ass. Other problems with the syntax have been solved by introducing sugar at the right place. Why not

  id hash=@{ @"key" : @"value };

and

  id array=@[ @"value1", @"value2", @"value3"];

That's not half as exciting as to write into the raw, uncharted territory of your virtual address space...

The only problem I see with this approach is the Javascript-interpreter seeing through your pointer system and holding a reference to the object pointed to - which defeats the purpose of creating a possibility to segfault...

I guess, this has taken "minimum viable" to the next level.

This is a recent talk by him about scalable programming language analysis. And yes, he's still at google.

http://vimeo.com/16069687

Comparing anything to Kod isn't really fair at this point. It is currently at 0.0.3beta and not feature complete (I hope ;)

Sorry, but the only thing more painful to read and edit than pure regular expression syntax is string-escaped regular expression syntax. I still cringe when I remember writing this in C and Java.