Considering half the comments are “Proxmox” and “Virtualbox/Parallels” are so much better anyway, I’m guessing most commenters in here are extremely naive and not aware of the IT landscape.
This is the classic "golden goose" strategy. Why wait around all week for steady returns when you can just rip the thing open and see what you can get for the internal organs.
This is exactly the problem with optimizing metrics though. It seems like they’re getting more money from less customers but it puts them at might higher risk that those big customers will churn and tank the company which also increases as the price goes up as it will eventually hit a point where they can find something cheaper.
You obviously didn't read what I wrote or understand it. I specifically said this:
>Sure you can load scripts in-line for stuff below the fold, but make sure it doesn't actually get parsed by the browser until that feature is likely to be visible on the screen."
I specifically said you could load a script in-line for stuff "below the fold" as long as the browser doesn't parse it until it's used. That's very different than doing an HTTP request for a script file while scrolling.
But you know what? Forget it. I'm done trying to explain things to people who think they already know it all and didn't even understand my original comment.
> users can wait an extra second [every time they scroll to load new content]
which is exactly the bad experience the commenters above are talking about.
They understood your comment, and they disagree. This is not the good advice you think it is, unless your main goal is to score 100 on lighthouse for SEO purposes, not UX.
The loading spinner is specifically for people with shitty internet connections when loading dynamic data after the initial page load. And you're completely misunderstanding practically everything I wrote and replacing what I wrote with your assumptions. Go ahead, it's the internet, bash away all you want. But I know what I did, I know it works, and I know it's not janky at all - it's your assumptions that are wrong. The advice is good, your understanding of it is not. You don't need to reply, I won't be trying to explain any of this any further just so you can misunderstand everything I wrote, again.
People scroll pages to skim. This also sounds like it might break CTRL-F.
If I can't skim your page instantly I will more than likely churn my visit.
Doesn't matter that I have a good computer on a 1Gbps connection, you ruined my experience. I'd rather wait 1 sec for the full page to load, than wait a series of 100msecs on what should've been a fully loaded page to actually load at an arbitrary point in time.
Maybe you missed the part where I said we're using SSR for content? That solves the CTRL-F problem easily.
You (and a lot of others here) are making a ton of wrong assumptions, imagining things I never said, and making up your own problems that don't exist in my code just to try to bash me, without even really understanding anything that I wrote in my comment. This entire thread sucks and is full of low-quality trolls. I've been doing front-end for ~30 years, I know what I'm doing. Don't bother replying, I won't be responding to further wrong assumptions and bashing.
And XLST... Actually pretty cool, a standardized way to render XML files. Too bad XML was way too verbose and clunky that everyone basically walked away from it.
In my car (BMW from 2012), the engine does not shut off when you press the start/stop button when you're driving. It only shuts off the engine when you press it AND you're stationary. This seems like a totally obvious interlock to me, it puzzles me that Ford didn't think of this and as a solution moved the button instead.
I run a small time wireless network for a business (about 100 concurrent clients at any given time), I had to disable PMF because some devices simply wouldn't work.
Edit: also, from my notes at setup time, some devices could connect but then had trouble roaming.
Invalid UTF-16 with unpaired surrogates. Or rather WTF-8 is an alternate encoding of UCS-2. The subset of UCS-2 that is valid UTF-16 encodes to valid UTF-8 when encoded with WTF-8. The encoding is invertible, valid UTF-8 decodes to valid UTF-16, otherwise any byte sequence decodes to UCS-2.
> WTF-8 (Wobbly Transformation Format − 8-bit) is a superset of UTF-8 that encodes surrogate code points if they are not in a pair. It represents, in a way compatible with UTF-8, text from systems such as JavaScript and Windows that use UTF-16 internally but don’t enforce the well-formedness invariant that surrogates must be paired.
It’s the unpaired surrogate code points. That’s the whole thing. It’s about encoding ill-formed UTF-16, which is distressingly common in the real world.
broken emojis? There apparently are known issues that some frameworks break Unicode at wrong boundaries, maybe the author saw it regularize into a deeper mess
It’s not just broken emoji, it’s straight up broken content: UTF-8 can not represent unpaired surrogates.
WTF-8 is necessary for Rust’s compatibility with Windows filesystems (it underlines OsString on Windows) as e.g. file names are sequences of UTF-16 code units (and thus may contain unpaired surrogates).
reply