8 ms·
Or... maybe it's not AMPs fault (not that I'm a fan of AMP). Maybe it's just that Ruby is quickly going out of vogue and you're just seeing the signs.
by canada_dry 8y ago
Or... maybe it's not AMPs fault (not that I'm a fan of AMP). Maybe it's just that Ruby is quickly going out of vogue and you're just seeing the signs.
- richjdsmith 8y agoAh good, I was hoping for the "Hurdy Hur Hur Ruby is slow so Rails is slow crowd to show" Ruby "going out of vogue" has nothing to do with the authors problem. It wouldn't matter if the author was using TrendyNewFramework.js™, PHP, Django or some GO framework. The issue seems to be the terrible user experience that comes with using AMP. I know I personally hate it and tend to drop off when I see it begin loading. Also FWIW, there's plenty of slow SPA's built on the latest and greatest, and there's plenty of fast rails sites (have you been to https://dev.to https://dev.to recently? It's like ️). Rails is doing just fine.