You know the modern web is broken when you visit a website and are greeted with this text:
@hund I really love this message. Thanks.
@hund But how should I lazyload everything then?! 😧
@Ghosty Say what now?
@hund Instead of loading all the text/content at once when you load the website up you load it lazily after the website was rendered and put the content in afterwards. And thus "reducing loading times"
@Ghosty It's plain text and maybe a few images, not the Lord of the rings trilogy on Bluray.
@hund It was meant to be ironic :P
@Ghosty It wasn't obvious. :P
@hund I know. I’m bad at writing :D
There's native lazy loading for img since Firefox 75
However, it seems this works only when js is enabled
Because there's some app logic behind this "plain text"? I, personally can't wait to see HTML dead and replaced with some GUI API. The Internet stopped being hypertext since long ago.
If you want to offer app functionality, please do so to those who asked for it. If in your first visit to a website you are "greeted" with this kind of message we all know what kind of "app logic" is behind it! 🙄
@VikingKong @ckoul @hund I think the main disconnect is that some people want interactive apps, some people want to consume documents and media, and both groups of people think the web is perfect for what they want.
@hund couple of reasons:
1. UI Design team over design
2. Incompetence, the market needs so many developers that my mother could be hired if I teach her the buzz words because many people hiring only know the buzz words
3. Resume driven development
4. Not challenging demands
5. Managers telling developers what to do. And developers not finding creative solutions (see 2. And 4.)
I probably missed a couple :P
Most of the time it's just as you describe.
I have a million better things to do with my time but in the end it was less trouble to do my company's sites myself rather than the alternatives, which are either someone who copy pastes from that stack overflow site or wait for that one in a million guy who actually knows what he's doing.
Mind, the web is filled with terrible and outdated advice on #HTML as with so many other things.
That is precisely when you have an #HTML application (say a game, an editor of some description or a database front-end) for which it would not be economical to support and maintain a backend-served fallback. It is 2020 after all and there's a reasonable expectation that people will have a choice to enable scripting if they so wish. In those cases, a <noscript/> is fine.
@hund Exactly that. Thank you!
@hund Sorry, could not resist! 😁
@hund everything is an app now. Also there's no more internet, only cloud~
How else can they drop the drive-by trojan keylogger cryptominer cookie?
@space_cadet That's true. Silly me!
At least they bothered to include a <noscript> warning at all. That's always nice of them. It makes me less resentful at the website knowing why the stupid shit doesn't work.
I would think that such behaviour would be incredibly shitty for SEO rankings. Just like content-blocking login portals. But apparently not? Sounds like big search engines need options to filter this bullshit.
@rvk I guess it's something. :P
@hund So what do you recommend for a static site w/out JS?
@dokoissho HTML? What else?
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.