0 users browsing Discussion. | 1 guest | 6 bots  
    Main » Discussion » Dear modern UXtards...
    Pages: First Previous 1 2 3
    Posted on 21-07-20, 12:07 (revision 1)

    Post: #359 of 449
    Since: 10-29-18

    Last post: 9 days
    Last view: 13 hours
    This seems to fit here...

    Hahahahaha. The content itself is in the fucking HTML - but hidden behind a <noscript> tag! So if you're browsing the site without JS, you just see the content immediately, but if your browser has JS enabled, you have to wait for the HTML to load completely (including the content), for the browser to parse the HTML and send a request to a javascript source file, wait for the javascript to load, get parsed, get to the point in execution where it sends a GET request to an API which serves the content, wait for the GET request to complete, the giant JSON payload to get parsed, and then finally JavaScript can do the DOM operations necessary to populate the body.

    So with JavaScript disabled:

    1. GET request to /hillelwayne/archive/i-ing-hate-science/
    2. The response contains the post contents, so rendering of content starts even before all the HTML is downloaded

    With JavaScript enabled:

    1. GET request to /hillelwayne/archive/i-ing-hate-science/
    2. Once the entire HTML body is downloaded, GET request to /.../main-<hash>.js
    3. Once the entire JS script is download, parsed and executed, GET request to /api/emails/...
    4. Once the entire JSON payload is downloaded, parse the JSON payload
    5. Once the entire JSON payload is parsed, populate the body

    Why do people make websites like this?

    The funny thing is: The script which actually loads the e-mail is at the very bottom of the HTML. Normally, putting scripts at the bottom of the HTML is good practice, because you want the content to be loaded first, and JavaScript to be loaded after the content. But in this case, the javascript loads the content, so it's critical to start downloading it as soon as possible. The script tag should've been close to the very top of the HTML. But it's not, so the script which loads the actual content of the page is going to be loaded with essentially the lowest priority possible by the browser, and the browser won't even know about it before the entire post body is loaded (due to that aforementioned noscript tag).



    EDIT: formatting

    My current setup: Super Famicom ("2/1/3" SNS-CPU-1CHIP-02) → SCART → OSSC → StarTech USB3HDCAP → AmaRecTV 3.10
    Posted on 21-07-20, 15:21
    The Sufferer

    Post: #563 of 598
    Since: 10-29-18

    Last post: 86 days
    Last view: 9 hours
    Holy shit that's horrifying.
    Posted on 21-07-20, 18:10
    Dinosaur

    Post: #972 of 1282
    Since: 10-30-18

    Last post: 4 days
    Last view: 22 hours
    Places like MercadoLibre do exactly the same shit:

    - Static HTML for rendering the pages, which works even with JS off (but NOT inside NOSCRIPT tags!)
    - Plus a unhealthy big blob of JSON (we're talking of several hundreds of kilobytes just for a product listing page) for re-rendering the pages with their abomination of homebrew JS framework

    I learned this the hard way when I was having the unexplained CPU hogs on Seamonkey - turns out this malpractice breaks all hell loose in browsers' rendering engines and JS engines (in the case of SM, handling of timers and the NS-era throbber got involved, IIRC), for no good reason at all.

    JavaScript is one of mankinds' worst mistakes, make no doubt of it. And now, deranged nerds funded by unlimited VC money are trying to rewrite the world in JavaScript, one module at a time.

    $DEITY have mercy of us...

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 21-11-23, 12:06

    Post: #369 of 449
    Since: 10-29-18

    Last post: 9 days
    Last view: 13 hours
    https://i.imgur.com/rKdPM0Z.png (filen)

    One of these is a zero, the other one is a lowercase "o"...

    My current setup: Super Famicom ("2/1/3" SNS-CPU-1CHIP-02) → SCART → OSSC → StarTech USB3HDCAP → AmaRecTV 3.10
    Posted on 22-02-27, 14:27
    Dinosaur

    Post: #1056 of 1282
    Since: 10-30-18

    Last post: 4 days
    Last view: 22 hours
    Speaking of serial UX offenders: a bunch of GNOMEs believe noone needs subpixel rendering anymore because They Say So:
    https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/3393

    In particular the excuses given by this snowflake are downright stupid, and can be condensed down to this pile of manure:

    - "Everybody is buying UHD displays these days"
    - "Google/Apple stopped doing it, so we should do so too"
    - "Control panels and preferences are harmful for users"


    I'm glad I am not a GNOME user, but sadly all this assbackwardery also hits GTK4, so...

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 22-02-27, 21:47 (revision 1)
    Custom title here

    Post: #1060 of 1150
    Since: 10-30-18

    Last post: 6 days
    Last view: 1 day
    Good riddance. Subpixel antialiasing is a misfeature that has caused me nothing but trouble as everything tries to re-enable it over my express command not to.

    --- In UTF-16, where available. ---
    Posted on 22-02-28, 02:11
    Dinosaur

    Post: #1057 of 1282
    Since: 10-30-18

    Last post: 4 days
    Last view: 22 hours
    Well, I can't live without subpixel aliasing - it's the first thing I setup on any new PC that doesn't ship with that enabled out of the box, and thankfully modern, non-braindamaged Linux DEs allow some degree of tweaking over it.

    What we need is to empower the user to do whatever the fuck he/she/it wants, AND RESPECT HIS/HER/ITS FUCKING ORDERS, not to convince that Apple/Google is always right and the user is dumb. If you don't want subpixel AA but your computer insists into reenabling it out of the blue, something is really wrong with UX. Same as any developer insisting that nobody needs $FEATURE and everybody inside their bubble is buying $2000+ in new computer gear every year.

    My computer, my rules. Let me have my cake AND eat it.

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 22-02-28, 02:29
    Custom title here

    Post: #1061 of 1150
    Since: 10-30-18

    Last post: 6 days
    Last view: 1 day
    Well, part of the problem is browsers having their own text rendering engine with its own antialiasing functions. And then, even if the browsers check and respect the OS settings, offering websites the choice to override browser text antialiasing settings.

    And even if you fix the browsers and kill their site overrides, there's all the applications that use an embedded, nonconfigurable HTML rendering engine as a part of them.

    --- In UTF-16, where available. ---
    Posted on 22-03-03, 10:03

    Post: #389 of 449
    Since: 10-29-18

    Last post: 9 days
    Last view: 13 hours
    https://old.reddit.com/r/programming/comments/t5gsaf/why_japanese_web_design_is_so_different_cultural/

    Apparently the consensus isn't as clear-cut as one might think.

    My current setup: Super Famicom ("2/1/3" SNS-CPU-1CHIP-02) → SCART → OSSC → StarTech USB3HDCAP → AmaRecTV 3.10
    Posted on 22-03-03, 12:23 (revision 1)
    Dinosaur

    Post: #1060 of 1282
    Since: 10-30-18

    Last post: 4 days
    Last view: 22 hours
    The Japanese Internet surely its a product of its time, and I guess that for a native, all that clutter is actually an advantage, as Japanese (and Chinese) are languages whose pictographic character sets give them an unique advantage that our Latin-based alphabets can't (doesn't meant the West hasn't been trying... but we got the emoji disease instead!). On the flip side, Japan sees pointless whitespace as a bug, not a feature~

    And even then, that doesn't mean that Japan is Modern Webshit™-free, as the Chromeisms are silently infecting the land of the rising sun, slowly but steady:

    - Pixiv has become a glorified SPA: bloaty, slow, and unusable without JavaScript
    - Fanbox goes even further, and completely breaks without Google WebComponents®
    - I've even seen doujin-related sites following this horrible trend of adopting the latest Chromeisms: for example, as of the 2021 edition, you couldn't vote anymore on the Touhou Popularity Contests if you weren't using Holy Chrome or latest Firefucked (again: Google WebComponents®)

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Pages: First Previous 1 2 3
      Main » Discussion » Dear modern UXtards...
      This does not actually go there and I regret nothing.