• Maeve@kbin.earth
    link
    fedilink
    arrow-up
    62
    ·
    5 hours ago

    It’s good information about how bad the app really is. People should not dismiss the information because of the crappy website complaints.

    • mr_anny@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      1
      ·
      12 minutes ago

      It’s really hard not to dismiss when having a seizure for just trying to read it.

      I really wanted to read.

          • pentastarm@piefed.ca
            link
            fedilink
            English
            arrow-up
            15
            ·
            4 hours ago

            I run no script on both Firefox desktop and mobile. I’d much rather have to approve things to run, than have them run by default.

            • tal@lemmy.today
              link
              fedilink
              English
              arrow-up
              6
              ·
              edit-2
              2 hours ago

              If one has it set to default-deny Javascript, a lot of websites don’t work, because many web developers don’t develop websites that work without Javascript today.

              Historically, websites did a better job of falling back.

          • orclev@lemmy.world
            link
            fedilink
            English
            arrow-up
            7
            ·
            4 hours ago

            There’s dozens of us. Works great on mobile with NoScript, although the source code snippets don’t load. Since the article describes what they do anyway it’s still readable without them, and the excellent performance is worth leaving JS blocked.

  • mr_anny@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    51
    arrow-down
    4
    ·
    5 hours ago

    I can’t say anything about the content of this blog. It was horribly laggy to scroll on mobile device. And by horribly laggy, I mean like aunt’s 1986 vacation slide show on a projector while having dry cookies and tasteless off brand earl grey.

    I’m sorry if it sounds rude but I had to bring this on out in the open. What even runs under the hood on that blog…

    • XLE@piefed.social
      link
      fedilink
      English
      arrow-up
      4
      ·
      2 hours ago

      Even if the effect didn’t lag, there’s almost no added benefit to it. The title is cut off, and the description is even worse.

      If the author wanted to, they could have done something like this with no scripts, minimum effort, and probably zero lag.

      (If OP’s website chucked for you, I’m curious whether this demo is seamlessly smooth. It is for me.)

    • Snot Flickerman@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      23
      arrow-down
      1
      ·
      4 hours ago

      It’s a bit funny that it’s completely at odds with how they describe their goals (emphasis mine):

      I am thereallo, a web developer who makes things look pretty and work smoothly >w< been building stuff since 2020, mostly frontend but i can do fullstack too! i use react, next.js, and tailwind css because they just work, and motion for animations that don’t feel plastic. i prototype in figma, steal components from shadcn/ui when i’m lazy, and deploy to vercel or cloudflare depending on the vibe~ i used to reverse engineer games (genshin leaks era lol) but now i just make websites that don’t suck. i know typescript, python, go, and dabbled in rust and lua. my goal is making ui that feels human such as smooth feedback, clear buttons, keyboard accessible, no confusing bs. mobile first always! outside coding i listen to vocaloid and play project sekai, which definitely influences my color choices uwu. oh and i care way too much about bundle sizes and performance. currently learning native ios/android development. hmu on discord or github if u wanna chat! ♡

      • nawa@lemmy.world
        link
        fedilink
        English
        arrow-up
        8
        ·
        4 hours ago

        It wasn’t horribly laggy on my Pixel but it definitely was less performant than a page like this should be.

    • floofloof@lemmy.ca
      link
      fedilink
      English
      arrow-up
      3
      ·
      3 hours ago

      Worked fine for me, but I block ads and trackers on my home network so that probably helped.

    • purplemonkeymad@programming.dev
      link
      fedilink
      English
      arrow-up
      3
      ·
      4 hours ago

      Yea for me too, it appears to be something we the title header following your scroll. It’s super smooth just until it tries to pin it to the top.

      Reader mode works until I realised that they did explain the pictures, so just referenced text I didn’t see.

    • MonkderVierte@lemmy.zip
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      4 hours ago

      Not a performance problem. My guess is, they (poorly) emulate native scrolling via JS on mobile. Probably for some progress feature or something.

      JS disabled, scrolling works. Though it was only slightly laggy for me.

      • grinde@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        3
        ·
        3 hours ago

        Unfortunately all of the code blocks are loaded after-the-fact with JS for some asinine reason (highlighting I’d understand… but why the actual text?), so disabling JS also disables all the code snippets on the page.

      • alakey@piefed.social
        link
        fedilink
        English
        arrow-up
        2
        ·
        3 hours ago

        Definitely a performance problem, no HW acceleration on PC produces the same insanely stuttery scroll.

  • MonkderVierte@lemmy.zip
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    1
    ·
    edit-2
    4 hours ago

    Btw, this site has no business doing (laggy) scrolling via JS on a fucking blog.
    No JavaScript for you.