HNHacker News
TopNewBestAskShowJobs

wusspuss

133 karma · joined January 25, 2022

submissionscomments
wusspuss··on Ask HN: Why does the modern web hate users?
>Back in the day you could just send everyone the same HTML/JS/CSS rendered on your server and it would work for everyone.

HN itself works perfect on mobile or anywhere for that matter and is very lightweight. I don't think it's because they optimized it. They just didn't fuck with it.

>Now things are more complicated: people want "native apps" on their Android and iOS

Do people want those? I believe it's just companies shoving those down people's throats

wusspuss··on Ask HN: Why does the modern web hate users?
If voting changed anything, they'd make it illegal.

You can't vote twitter or youtube out of power.

You can't code their wealth away https://www.youtube.com/watch?v=FEU632_Em3g

wusspuss··on Ask HN: Why does the modern web hate users?
Because network effect. Because alternative services not only don't have the vast user bases to begin with, they also don't have the capital to spend on marketing. When they do, it's pretty obvious they aren't benevolent.
wusspuss··on Ask HN: Why does the modern web hate users?
Getting you to click on ads does not takes megabytes of JavaScript diarrhea.
wusspuss··on Ask HN: Why does the modern web hate users?
That doesn't explain over-engineering. I would understand building slower and less efficient systems if that took less resources. Or more complex systems if it achieved something. But modern web takes more resources to develop and achieves nothing
wusspuss··on Ask HN: Why does the modern web hate users?
Pretty sure reddit or twitter would be just as hellish to use if you had their frontend files stored locally

Oh wait, they already are cached locally.

wusspuss··on Ask HN: Why does the modern web hate users?
>CloudFlare Pages and GitHub Pages are bringing in a new era of fast, static websites.

Static site hosting with a brand name smashed onto it is a new era? GitHub itself btw is broken on palemoon for one thing. Not here to defend palemoon but it does show one thing: GitHub's frontend is over-engineered.

wusspuss··on Ask HN: Why does the modern web hate users?
>Modern front end javascript frameworks are made to offload the compute from the server to the end user. This saves the company money

Does it? I doubt hiring people to produce dozens of megabytes of compressed (!) javascript costs less than the cpu cycles it takes to produce html, especially if that's succinct html, not said megabytes of diarrhea. And "people" here almost definitely does not mean "that one guy who makes the frontend" - no single human could ever produce such abomination. For one thing he just wouldn't have the time! And then if we're frank there are no traces of humanity in twitter's front end - only the pungent smell or festering corporate development.

wusspuss··on IETF should keep XMPP as IM standard, instead of Matrix
Tbh if a client is dumb enough to put xhtml-im directly into DOM with no verification that is the client's problem, not the XEP's, and that should be no reason to cancel it.
wusspuss··on IETF should keep XMPP as IM standard, instead of Matrix
>XML is best used for markup,

Funny enough, the one thing XMPP does not use xml for is markup! See

https://xmpp.org/extensions/xep-0393.html - an ad hoc markup format

https://xmpp.org/extensions/xep-0394.html - a laughably perverse usage of the already perverse XML format I don't know why they did this but I guess they had reasons - perhaps XML doesn't actually do that well even for markups

wusspuss··on IETF should keep XMPP as IM standard, instead of Matrix
> in JSON there can be many ways to implement a collection of name/value pairs.

Are there? JSON has dicts and lists. I mean you could store a collection of name value pairs in a list, maybe even a list of lists, but that's just stupid and an incorrect usage of the format. Where as in xml there really are tons of ways to do that, and ALL of them are awkward

wusspuss··on IETF should keep XMPP as IM standard, instead of Matrix
>JSON maps well to javascript types, but not anything else.

Except it does. Take python. Ruby. Any language that has a notion of dicts, lists and strings/ints/floats. That's basically every high level language ever. Even exotic stuff like tcl. And e.g. C, a low level language, has a thousand implementations of those same structures.

wusspuss··on IETF should keep XMPP as IM standard, instead of Matrix
>Now I need to find out which type of JSON an application uses (does it always use UTF8 or does it break the standard?

Utf-8 isn't standard to XML, it's required by XMPP. So in this scenario the same could be required from json.

>Which version of the JSON Schema does it use?

No one uses those and everyone is happy. As for XML schemas, xmpp makes even harder to use than it makes everything else. Because it has this endless xml document that you end up having to parse with a streaming parser and those understandably don't support schemas. You end up having to build the little DOMs yourself, for every stanza. This isn't me theorizing, this is what clients (dino, gajim, tkabber) do. Now with the homebrew DOM you're unable to use xpath (unless again you implement it yourself which is no easy feat) which makes xml's awkwardness i.e. the fact that xml doesn't map into common language structures like dicts and lists so, so much worse.

> How should I deal with duplicate keys?

Generally you don't because libraries don't even support that, and people generally are decent enough to never use those.

>All serialization formats are stupid and messy in some way but I think XML gets a bad rep because of the defaults many parsing libraries picked (and the vulnerabilities they introduced).

And because it is messy. Not pushing for json in particular but even json doesn't have dtds, entities and so on and so forth. Thus parsing libraries don't implement such features, thus fewer vulnerabilities. Whereas vulns in xml parsers are basically the norm - look at python's out of the box xml parsers - there are four of them and each one has at least some vuln marked in the table in official python docs! Again, I'm no json fan, but it's already light years better than xml. "Any damn fool could produce a better data format than XML." Look at bittorrent's ad-hoc format, bencode. Even that is much better than xml. And in a high level language an entire parser would take you one evening to write with no prior knowledge of the format. And that implementation would be probably about the size of those ad-hoc DOM implementations in xmpp clients, that don't even do any parsing themselves, and would be much more pleasant to use.

← PreviousPage 2 of 2