I'm mentioned in the article. I had nearly the exact same experience as the author from a different side of the planet -- and we even overlapped on i18n/l10n is

I'm mentioned in the article. I had nearly the exact same experience as the author from a different side of the planet -- and we even overlapped on i18n/l10n issues. I actually raised some of these issues in a blog/Reddit post from a rewrite I did in 2016, where this was one of the biggest pain-points (back when native code was cryptic but legal). After that thread was closed without real answers or a way to reply, I stopped participating in any meaningful way to the community and did all side projects in something else. I've been afraid to even ask the community for any sort of assistance because of the hostility I've encountered for suggesting something was wrong or incomplete. You can see in the authors constant preapologies in the article that he's really afraid of the tact chosen for this so he doesn't get any flack to put him in even worse standings with community; this is absurd, and it's the reason it needed to be aired out in a long blog post after bottling frustrations. I've switched jobs since, but we've discussed migrating from Elm to PureScript for the last like year without having a big enough reason to pull the trigger, but maybe this would be a good time since it seems a lot of people are frustrated in the community and I've had to come up with a few too many 'clever' solutions to get around limitations. I think Elm is the best playground to learn functional programming, but I wouldn't recommend it to anyone for anything other than a learning opportunity or a narrowly-scoped weekend SPA project.