2 thoughts on “The Website Obesity Crisis

  1. Rob Caldecott

    I just finished reading the whole thing and it’s absolutely bang on. I spend most of my time working on web apps nowadays and am surrounded by people dropping as many JS frameworks into their code as possible. It’s infuriating. Not only is it often a sign of laziness but your web app soon becomes a lumbering unmaintainable horror show that 6 months down the line no one will be able to figure out. And the fact it takes 10s to render the fucking thing over a 3G connection on a three year old iPhone is simply brushed under the carpet. Simplicity is actually frowned upon: like you can’t be doing it properly unless you drag in the latest github JS flavour of the week. I have worked with people that basically cannot code for toffee and instead spend all their time trying to make framework A coexist with framework B in between trawling Stack Overflow for help with a JavaScript console error they simply do not understand.

    I don’t miss C++ (still use it now and then – one of my projects is still going strong and I started it in 1997), and I *love* coding for the web, but by Christ do people love complicating things. Keep it simple ffs.

    1. cleek Post author

      i’m just starting to get back into web dev at work. the last time i did any, AJAX was still a bit exotic, JSON hadn’t really caught on, and JS was still primarily for client-side validation or simple UI activities. now, i have to figure out OpenUI5 and Typescript with a company-specific layer on top of it all.

      there’s just so much stuff in there, i don’t even know if optimization is possible.

      looks good on the resume, i guess.

Comments are closed.