[adamwk]

I can’t think of a worse announcement for your road to 1.0. Who cares? Without localization or accessibility support, it doesn’t make sense to call your UI framework production ready with a 1.0 version. I think limiting what third-party contributors can bridge from browser APIs killed Elm’s momentum for anything but toy projects. It now seems more like a sandbox for Evan to play around with compiler ideas than something meant for production use.

[shamsartem]

I don't think what you say is accurate. I maintain an Elm app and it is fully localized and I think it has a pretty good accessibility

Localization is done using one big record for each language, that I just pass into each part of the aplication that uses strings. It's very convenient cause I can use simple functions in the record where they make sense for plurals and special cases in different langauges

Accessiblity is achieved with a combination of good html, ports and in some complicated cases (autocomplete-typeahead) - web components

[kubb]

I say let him cook. The real ones will know when it's good and ready, and hype driven folks can't be saved anyway.

[crote]

On the one hand, it's good to see Evan's doing fine. He has some pretty good ideas about language development, and Elm has inspired quite a bunch of very interesting projects.

On the other hand, seven hears of absolutely nothing, then a small compiler performance bump, and calling it the "road to 1.0"? No offense, but why bother? She's dead, we've grieved, and we've long since moved on. Until there's something genuinely mindblowing to release, I don't think many people are going to care.