[bwarp]

Just as an anti-point to the above...

I'm doing some in depth analysis to see if it's a suitable replacement for C#/.Net framework in our current application stack (message oriented CQRS architecture, web front end). We're doing this by rewriting a chunk of the stack in it and seeing where we get to.

At the moment, it's a very good fit. The time to market is an order of magnitude less than .Net framework. The tooling and mindset is cheaper and easier to maintain and we're not having to invent many solutions to problems - they are already apparent (or just not required).

The only trouble so far has been availabiliy of quality persistence libraries for database engines.

I'm not going to write anything up though until v1 is out and I've ported everything to that and tidied it up.

I don't know if it scales up linearly as the codebase grows yet. This is my only real worry.