About enshitification of web dev.

  • vext01@lemmy.sdf.org
    link
    fedilink
    arrow-up
    76
    arrow-down
    6
    ·
    edit-2
    4 hours ago

    Yep.

    On a rare occasion I hit a website that loads just like “boom” and it surprises me.

    Why is that? Because now we are used to having to wait for javascript to load, decompress, parse, JIT, transmogrify, rejimble and perform two rinse cycles just to see the opening times for the supermarket.

    (And that’s after you dismissed the cookie, discount/offer and mailing list nags with obfuscated X buttons and all other manner of dark patterns to keep you engaged)

    Sometimes I wish we’d just stopped at gopher :)

    See also: https://motherfuckingwebsite.com/

    EDIT: Yes, this is facetious.

    • who@feddit.org
      link
      fedilink
      English
      arrow-up
      8
      ·
      edit-2
      14 hours ago

      Another continual irritation:

      The widespread tendency for JavaScript developers to intercept built-in browser functionality and replace it with their own poor implementation, effectively breaking the user’s browser while on that site.

      And then there’s the vastly increased privacy & security attack surface exposed by JavaScript.

      It’s so bad that I am now very selective about which sites are allowed to run scripts. With few exceptions, a site that fails to work without JavaScript (and can’t be read in Firefox Reader View) gets quickly closed and forgotten.

    • luciole (he/him)@beehaw.org
      link
      fedilink
      arrow-up
      3
      arrow-down
      2
      ·
      edit-2
      9 hours ago

      having to wait for javascript to load, decompress, parse, JIT, transmogrify, rejimble and perform two rinse cycles

      This is whole sentence is facetious nonsense. Just-in-time compilation is not in websites, it’s in browsers, and it was a massive performance gain for the web. Sending files gzipped over the wire has been going on forever and the decompressing on receival is nothing compared to the gains on load time. I’m going to ignore the made up words. If you don’t know you don’t know. Please don’t confidently make shit up.

      EDIT: I’m with about the nags though. Fuck them nags.

    • Typewar@infosec.pub
      link
      fedilink
      arrow-up
      1
      ·
      11 hours ago

      Having 2 loads gives the illusion that it’s fast, aka. not waiting staring at something not doing anything for too long.

      From a business perspective, isn’t it best to just yeet most stuff to the front end to deal with?

      • vext01@lemmy.sdf.org
        link
        fedilink
        arrow-up
        12
        ·
        edit-2
        1 day ago

        The key idea remains though. Text on a page, fast. No objections with (gasp) colours, if the author would like to add some.

      • GreatBlueHeron@piefed.ca
        link
        fedilink
        English
        arrow-up
        8
        ·
        1 day ago

        I prefer the original. The “better” one had a bit of a lag (only a fraction of a second, but in this context that’s important) loading and the “best” one has the same lag and unreadable colours.

        • Zagorath@aussie.zone
          link
          fedilink
          English
          arrow-up
          4
          arrow-down
          1
          ·
          22 hours ago

          The original is terrible. It works ok on a phone, but on a wide computer screen it takes up the full width, which is terrible for readability.

          If you don’t like the colours, the “Best” lets you toggle between light mode and dark mode, and toggle between lower and higher contrast. (i.e., between black on white, dark grey on light grey, light grey on dark grey, or white on black)

          • GreatBlueHeron@piefed.ca
            link
            fedilink
            English
            arrow-up
            2
            ·
            19 hours ago

            OK, I was on my phone. Just checked on my desktop and agree the original could do with some margins. I stand behind the rest of what I said - the default colours for the “best” are awful - the black black and red red is really garish. If I didn’t notice the dark/light mode switch and contrast adjustment does it really matter if they were there or not? There is also way to much information on the “best” one - if I’m going to a web site cold, with no expectation at all of what you might find, I’m not going to sit there and read that much text - I need a gentle introduction, that may lead somewhere.

            • Zagorath@aussie.zone
              link
              fedilink
              English
              arrow-up
              1
              ·
              7 hours ago

              I actually really like the black black. And they didn’t use red red (assuming that term is supposed to mean FF0000); it’s quite a dull red, which I find works quite well. I prefer the high contrast mode though, with white white on black black, rather than slightly lower-contrast light grey text. I’m told it’s apparently evidence-based to use the lower-contrast version, but it doesn’t appeal to me.

              Though I will say I intensely dislike the use of underline styling on “WRONG”. Underline, on the web, has universally come to be a signal of a hyperlink, and should almost never be used otherwise. It also uses some much nicer colours for both unclicked and visited hyperlinks.

      • Lucy :3@feddit.org
        link
        fedilink
        arrow-up
        3
        ·
        1 day ago

        What’s the difference between 1 and 2? And 3’s colors hurt my eyes, and flimmers while scrolling (though, color weirdness may come from DarkReader)

        • grue@lemmy.world
          link
          fedilink
          arrow-up
          5
          ·
          23 hours ago

          What’s the difference between 1 and 2?

          “7 fucking [CSS] declarations” adjusting the margins, line height, font size, etc.

        • Zagorath@aussie.zone
          link
          fedilink
          English
          arrow-up
          4
          arrow-down
          1
          ·
          22 hours ago

          The most important difference between 1 and 2 is, IMO, the width limiter. You can actually read the source yourself, it’s extremely simple hand-written HTML & (inline) CSS. max-width:650px; stops you needing to crane your head. It also has slightly lower contrast, which I’m told is supposedly better for the eyes according to some studies, but personally I don’t really like as much, which is why “Best” is my favourite, since it has a little button to toggle between light mode and dark mode, or between lower and maximum contrast.

    • MonkderVierte@lemmy.zip
      link
      fedilink
      arrow-up
      8
      ·
      1 day ago

      My usual onlineshop got a redesign (sort of). Now, the site loads the header, then the account and cart icons blink a while and after a few seconds it loads the content.

      • vext01@lemmy.sdf.org
        link
        fedilink
        arrow-up
        15
        ·
        1 day ago

        Ah yes, and the old “flash some faded out rectangles” to prepare you for that sweet, sweet, information that’s coming any… moment… now…

        No, now…

        Now…