There's a lot of value here for anyone who does language design and development. It's important to see the challenges early language projects face, how users respond to them, and how the community responds in turn. If you examine this piece not from a perspective of the language wars or a language user, but from a perspective of "What can this tell us about what challenges early languages face" then this is a very good article. At its core, this article is about someone who was interested in a language, used it enough to find many bugs, found the motivation to write a blog post about it, and the community and devs responded in good and not so good ways.
For the right reader (early-stage language devs) this is a great resource. It's like an archaeologist uncovering a 10,000 year old pot. Sure it's not relevant to most users of pots today, but makers of pots could maybe learn something from it.
For the right reader (early-stage language devs) this is a great resource. It's like an archaeologist uncovering a 10,000 year old pot. Sure it's not relevant to most users of pots today, but makers of pots could maybe learn something from it.