3 ms·
TL;DR: Serving static assets is faster than using ruby to serve those assets. (how did this article get 43 points?)
by mceachen 15y ago
TL;DR: Serving static assets is faster than using ruby to serve those assets.
(how did this article get 43 points?)
- victork2 15y agoAt the risk of being downvoted, there's a big herd of 37signal followers on HN. Every article they post get a lot of points... Anyway I agree with your TL;DR, not much to see here!
- tomblomfield 15y agoCan you tell that 37 Signals is gearing up to a new product launch?!
- batista 15y agoYeah, they're gearing up to a new product launch. Is this supposed to be bad? Besides, that only tells up that they post a lot of new content for their blog. Nothing about how this content is voted up on HN --which, I, presume, is simply by folks finding it relevant and upvoting it. Or, do you think that they have their employees doing the voting to their own articles. Because certain people certainly imply that. To which, I respond: 1) HN is a social news site for hackers, people vote on stuff the like, and DHH et co are popular in Ruby/Rails hackers to say the least. 2) HN is a social news site for hackers. You really think a company like 37 Signals thinks they'll gain something regarding new customers by having it's articles linked and discussed here, and so much that they'll devise such a scheme?
- lrobb 15y agoThe next blog post will be about the speedup obtained with serving static assets via CDN?
- ludwigvan 15y agoIt is news when arguably a company that created the most well known web framework posts a blog entry titled "No framework needed". If you look for a TL;DR it would be "Use the right tool for the job. Do not be dogmatic about your technological choices."