4 ms·
Loading a page of text is effectively instantaneous. If the user's goal is to read that text, then anything else on the page that slows it down is bloat (from t
by hdctambien 5y ago
Loading a page of text is effectively instantaneous. If the user's goal is to read that text, then anything else on the page that slows it down is bloat (from the user's perspective).
All the stuff that is extraneous to the reason you visited the webpage would be bloat.
Think about a news article on [insert your favorite news website]. Often before you can see the article, you have to process a bunch of JS (SPA framework, tracker code, etc) before the text loads and you can get the info you were looking for.
- debarshri 5y agoLoading the page instantaneous is again can be solved by adding spinner. Sure, adding tracker and other stuff might be a jarring experience. But I think you can have all the stuff in your app and make it async so that it does not impact the core functionality of the app.
- hdctambien 5y agoAdding a spinner is just putting lipstick on the bloat. Progressively loading a page can at least hide the bloat from the end user. A page of text should just be a page of text. That's the beauty in sites like hackernews and craigslist. They are down-and-dirty, just-the-facts, we'll-get-out-of-your-way websites. You see bloat when you start adding stuff that obscures that core functionality and/or slows down/degrades the experience. Of course, the core functionality changes depending on who you are. The customer might just want to read the article, but the sales team wants to get you to see/click on ads and the marketing team wants you to signup for their newsletter. So, one person's bloat is another person's core functionality.
- mr_sturd 5y agoEvery time I'm taken to an NPR article, I'm offered a choice to accept or reject their non-essential cookies. When I click reject, I'm given a text-only version of the article. It's glorious.