When something goes wrong in technology, knowing who to blame is a surprisingly difficult problem. Despite having dealt with thousands of bug reports for over 1...
Some of these points are valid - if questionable for what is ostensibly a company blog and not a personal one, given eyebrow-raising finger-pointing at current or potential customers - but others? Maybe not so much.
Crashes in the browser
Didn't you choose to make a browser-based IDE?
Changes in the OS caused by OS updates
Didn't you choose to sell the software on that OS?
The network performance of third-party services we use
Didn't you choose to use those services?
Bugs in third-party libraries we use
Didn't you...etc.
The relevant parts of this post are the parts about making tradeoffs (making different choices would have a separate set of issues), how all software will face similar issues (you could ask similar questions of any software out there facing any issues), and the fact sometimes there is no easy or quick solution.
if questionable for what is ostensibly a company blog and not a personal one
Yet posted on Ashley's blog post who always made posts about technical aspects of his work and his perspective, on "his" blog hosted on the company's website.
Dealing with community members/bug reports is a technical aspect of his job.
Explaining where, in his experience, they go wrong is opinionated for sure, but clearly backed enough and made clear throughout the article.
I invite you to read it open-mindedly again.