7 ms·
I loathe the modern web. Speed is a secondary to "hey look what we're doing with our frameworks".
by exabrial 7y ago
I loathe the modern web. Speed is a secondary to "hey look what we're doing with our frameworks".
- dmix 7y agoModern front-end toolsets are finally starting to address this by using automated critical css, SSR + "hydrating" on load for interactive elements, webpack treeshaking + chunking of assets into tiny js/css files and only loading code based on what the page/routes asks for, PurgeCSS to get rid of unused css, cssnano/uglify/htmlmin/imagemin, etc. Webpack and these various popular tools has done a lot to make the web better and are default in many starter kits. But we're just beginning to see it go mainstream. The basic shift back to pre-rendering + delivering only what's needed on the actual page is a big deal which hasn't got enough attention yet IMO. We went completely in the other direction for over a decade because we thought networks and browsers could handle it, but it was too easy to abuse and mobile took over. There's no reason even very advanced websites can't load quickly, without having to fully compromise back to the 90s non-interactive websites. News sites and marketing teams still ruin it regardless with all the crap they add on top. But it's far far better than loading a giant blob of 20 jquery libraries plus a big old angular.js or backbonejs app (sometimes both at the same time) encompassing a whole site in one file, even though you just wanted to visit the contact page. I also blame Themeforest type developers because they're still stuck in the "let's add a hundred JS files so I can parallax and animate two divs" mindset.
- wolco 7y agoA modern css framework would increase the font size change the font type make the reply link a fat button. It would put a card around each parent reply thread. Getting rid of unused css helps but the additional markup would make the page 4 or 5 times larger.
- scrollaway 7y agoA "framework" doesn't do that. A designer does. Or whoever decides to implement it.
- dmix 7y agoI see a trend away from that in 'trendy' CSS frameworks like http://tachyons.io/ http://tachyons.io/ and https://basscss.com https://basscss.com The Bootstrap stuff you seem bothered by is better for splashy big-headline marketing sites not high-density content like HN. A lof of web designers cut their teeth designing marketing websites, not app UIs, so it's not surprising when I see it mindlessly used on sites like Reddit's new redesign.
- liability 7y ago> news sites It's really a sad state of affairs when an industry with such a strong historical connection with publishing is now reasonably cited as an industry worse at publishing than most others.
- rangibaby 7y agoNewspapers have always been full of ads fwiw
- liability 7y agoI'm talking beyond the matter of ads. On their websites I can use an adblocker, so in that respect the situation has actually improved. They regularly fail on basic UX. Their ability to turn a kilobyte of text into 10MB of trash is astounding, as is their ability to cripple modern computer hardware, or simply readability, with their latest 'innovations' in totally unnecessary JS/CSS fuckery. uMatrix blocking all JS, including first party, helps. But you've still got bullshit like floating headers that follow you when you scroll down the article to contend with. I find myself creating cosmetic filters to remove pointless floating clutter on news websites more than any other sort of site. The industry seems utterly incapable of presenting a clean and readable article online.
- 18pfsmt 7y agoI would advise using your browser's developer tools to find the irritating web page js, css, or domain/sub-domain responsible, and then using uMatrix/privoxy/hostfile to block that garbage. Many sites are usable by preventing js entirely.
- jdnenej 7y agoReader mode on browsers is the easiest way to make news websites usable
- liability 7y agoI can often get the text of the article in Emacs, so I generally do that. My TTS integration is better in Emacs than Firefox anyway, so I actually prefer it for longer reading. But regardless of our personal work-arounds or workflows, those websites shouldn't be like that. The general public is still subjected to the default experience and that bothers me.
- jasonhansel 7y agoYeah, but those fixes and workarounds are only almost enough to sometimes compensate for the code bloat that the frameworks themselves have caused.
- dmix 7y agoPeople seem to be confusing web 2.0/bootstrap style design (see: Reddit's bad redesign) with the frameworks here but the component based approach combined with webpack/compilation steps, which are very much mainstreaming, are fundamentally different than top heavy JS frameworks I spent most of the last decade using. I dont think people have really seen what server-side rendering (ala Next.js/Nuxt.js), decoupled components, modern treeshaking, minification, and chunking can do for performance. We've yet to have a full web framework designed entirely to encompass this from day one but they're coming and getting better at it. Outside of the endless 3rd party crap the 'business' guys add, if anything, it's no longer the JS framework size and library cruft I'm worried about it's how many object watchers I've got at runtime via Vue.js and reactive style programming (which automatically adds Object.observe style watchers to all data) + component initializers (which can add overhead to simple HTML templates). Fortunately with the new Vue 3 function API there is a clear distinction between observed values vs static/immutable/config data. The amount of observers per page dropped dramatically. Otherwise looking at a Vue project in the performance tab shows it's highly async and efficient. The new Vue functional API (allegedly) is also going to be far easier to treeshake so you really only ever get the library features you're using. Even for something like Lodash or Ramda where you might use only 10% of the functions it's a big deal. I'm sure React is making similar progress in this direction and it was already smaller than Vue. CSS Frameworks have some ways to go and PurgeCSS isn't perfect but using a functional CSS framework like Tailwind or Tachyons also helps in this regard, so all of the stuff isn't intertwined and can be stripped out. This type of tooling really does massively improve the state of things automatically, even with poor coding practices or large applications spanning multiple pages. SSR, treeshaking, chunking, stripping unused CSS, etc is a 'zero cost' type optimization that I've seen turn 700-1000kb dev assets into loading 100kb base + a few 5-10kb js/CSS files dependent on the page.
- csande17 7y ago
- benologist 7y agoIterating without a destination in mind. Assigning people to work on something vs finish it. This is in stark contrast to games which get released, get stabilized, and stop development. This model would suit a lot of software aside from security or dependencies necessitating updates but if we want we can just iterate forever.
- j79 7y agoI’m always amused when the frameworks being used advertise things like “We make coding fun!” I tend to think “but what about making the web enjoyable for the end user?”
- Aeolun 7y agoThe end user is paid to deal with whatever we provide them. But more importantly, the fact that the page loads 2 seconds longer is a drop in the bucket compared to the insane processes our business people dream up.
- tmh88j 7y ago>I’m always amused when the frameworks being used advertise things like “We make coding fun!” I understand where they're coming from having dealt with a few legacy frameworkless spaghetti code bases that have no documentation. Give me bad code to maintain in a known framework over bad code without a framework anyday. Adding features and debugging in those conditions are no fun at all.
- jdnenej 7y agoEnd users don't care. When they see a slow website they think "Awesome, now I have a reason to buy that new iPhone Jessica has because this one is getting slow"
- dijit 7y agoIt’s interesting to note that iPhones render JavaScript faster than laptops/desktops. https://mobile.twitter.com/codinghorror/status/1049082262854094848 https://mobile.twitter.com/codinghorror/status/1049082262854...
- ummonk 7y agoI love the power of modern web apps built using modern frameworks. I hate that ordinary content websites decide they need to be built using such frameworks.
- boring_twenties 7y agoSecondary? If only. It's more like not even considered at all.
- mistersys 7y agoI understand where this is coming from, however whenever I interact with a app that re-loads the whole window on every major interaction, I start getting frustrated because of the jarring, slow transitions, most modern web apps are faster after the initial page load, albiet on my 15" 2018 MacBook Pro. Stop blaming the modern web. There are plenty of slow PHP and rails sites and plenty of slow React based sites. Of course speed is second priority, I'd much rather have users using my app with a mediocre experience than nobody using my app. However, as the web supports more tooling and frameworks continue to evolve towards web assembly, I believe will start to have web apps approaching native speed. The reality is that requiring a server to render every page limits what you can do with your app. Even if modern tooling is overused, developers will always move towards what allows you to do more. I'd much rather focus on making modern tooling faster than complaining about the modern web.
- zanny 7y agoYou can have a very tiny website with custom onclicks to load / change elements via callbacks. The bloat of JS frameworks to do everything including generate the actual HTML client side is totally separate from having dynamic page content. I always strive to keep the client side stupid. I should be sending as much of the final document as possible from the server and any interactivity needed should also produce as little work for the client as possible.
- muzani 7y agoHonestly, with modern things like Webpack, minify/uglify, CDNs, web speed should be much better on low bandwidth sites compared to the past.
- Aeolun 7y agoMy parcel with a fairly simple app spits out a 10MB release build. We still have some way to go.
- dwheeler 7y agoIt depends on how you use it. Size matters. On a site I manage, we send about 64KB of JavaScript and we are working to make that smaller... and the main site functionality works when JavaScript is disabled. In contrast, many sites seem to think that 1MB of JavaScript, or even 5MB, are acceptable, and they can't even show simple static content when client-side JavaScript is disabled. On a slow link, 1MB of JavaScript means that the user has probably given up. And it's not just the size. 200KB of HTML is far far faster than 200KB of JavaScript; web browsers are highly optimized for handling HTML, while processing JavaScript is necessarily much slower. JavaScript is great for some things, but like a sledgehammer it's not always the best solution. Too many people aren't considering the real end-user experience. "Pretty graphics, but it takes 5 minutes to download" is usually not a worthwhile tradeoff. To paraphrase Goldblum: Your web designers were so preoccupied with whether or not they could use JavaScript, they didn’t stop to think if they should.
- andrepd 7y agoTo a certain extent, it's developers serving themselves, not the user. Your job is not to show off the latest frameworkify.js and get internet points when you blog about it. It's also not to make your life easier (like by including a 1MB js library that saves an afternoon of your time). It's to make the user's life better. Just do your damn job! \end{rant}
- userbinator 7y agoUnfortunately I suspect a lot of the decisions are driven by resume-padding, which is itself a phenomenon started by management who has no idea of the implications of using $latest_web_tech beyond the fact that it's "new and modern" asking for use of the dozen latest frameworks for everything they do. If the companies hiring web devs changed their mindset and listing a dozen different frameworks on your resume was perceived as the negative trendchasing architecture-astronauts that such developers often turn out to be (at least in my experience), and valued simple JS skills and experience instead, I suspect websites would end up being a lot different than they are today.
- scarface74 7y agoIf HR departments wouldn’t set hard limits on percentage raises that are allowed and then hire new developers at market rates causing salary compression and inversion, developers wouldn’t have to be constantly on the look out for their next job and always stay focused on Resume Driven Development.
- jdnenej 7y agoSaving an afternoon of your time means spending an afternoon working on more things the user wants. With that logic we should be writing web apps in pure assembly to shave off as much loading time as possible despite the fact that in the time you could have built the whole application, you are still working on the login page.
- dymk 7y agoDAE javascript is bad???