We can (must) judge this article on its own merit. While not particularly informative, it is well written and explains the problem very, very clearly. The examp

We can (must) judge this article on its own merit. While not particularly informative, it is well written and explains the problem very, very clearly. The examples and analysis make sense even to people who aren't developers. It helps to raise awareness about an important issue, and is a part of the solution. Telerik's cruft is somewhat different from the cruft referred to in the article. They offer "rich" UIs, which we might hate, but is just what many companies choose when they try to replace their old Windows Forms apps with web apps. With modern browsers, they aren't really that computationally expensive. And in any case, they aren't responsible for the type of issues mentioned in TFA. Like loading from dozens of domains, interstitial ads, social media links, and 200+ requests. Telerik's products cannot be evaluated in isolation without looking at their history. They primarily cater to enterprise-y Microsoft shops, and they been in the business at least from the classic Asp.Net days (10+ years). Their components were DLLs earlier (which they probably still offer), but have now moved to somewhat leaner, modern JavaScript libraries. Their market moves very slowly, and it makes sense for them to move at a similar pace.