Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That would be what I’d care about the most. Smaller file size, but not an order of magnitude difference? Meh.

Easier for the browser to process? Well that’s going to have a tonne of useful ramifications.

Honestly that’s what annoys me about web services in general. (Rant mode enabled). The human readability aspect is moot because conversion is cheap, yet everything these days is built on XML, JSON and YAML.

The increasing use of middleman services whose entire job is to parse these formats into native types, then process the data, then serialise back into the same inefficient format, makes the issue a whole lot worse.

I mean, sure, this stuff is used so heavily that some amazing work has gone into parsing with SIMD at ridiculously high rates, but this is still orders of magnitude more time and effort for a CPU to perform the same thing with a native format. Even for things like strings, an actually-sensible representation like [length][body] would save all kinds of hassle by avoiding processing delimiters, searching for quotes, etc, and would make loading a value as simple as allocating the ALREADY KNOWN size and reading it.

Anyway, that’s my rant. The more parse-friendly formats out there the better.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: