billybolero

3 ms·

1. 1.▲
   by billybolero 11y ago

   Progressive enhancement work well for simple stuff. Like progressively enhancing a form post, or a "like" button which just sends an Ajax request. But as the complexity grows, progressive enhancement doesn't really scale and
2. 2.▲
   by billybolero 11y ago

   I read another blog about someone who tested that (don't have the url, but it was easy to find), and their conclusion was that the crawler won't wait for any Ajax request to finish to let you render that content. If you want to re
3. 3.▲
   by billybolero 11y ago

   I mostly agree, but at the same time, the rise of native apps has raised the bar of what people expect in terms of UX. Take Hacker News and Reddit, primarily content based sites and a good fit for the classic server rendered HTML approach.
4. 4.▲
   by billybolero 11y ago

   Because that singleton will serve multiple requests on the server, requests from different users. Singletons are more okay on the client because you know you'll only serve one user, so the singleton can make that assumption as well. Bu
5. 5.▲
   by billybolero 12y ago

   Yes, that's an ES2015 (formerly known as ES6) feature called destructuring. It's just one of the great features of ES2015. You can use ES6 today by transpiling to ES5 with https://babeljs.io