Subscriptions are a mechanism to attract developers, who then advocate that their company should use the API.

Facebook used the same strategy to compete with Google Maps. The company became one of the biggest contributors to OpenStreetMap, which everyone has benefited from downstream.

Submitting projects like this to HN is a good way to get them nerfed.

If they're optimizing for SVG generation, then that's an excellent outcome in my opinion. Vector images shouldn't be "pretty niche".

And SVG is fantastic to draw easter eggs or hidden messages. Just a insult to the top of the 4 in 404.

Please it's almost my primary bench for drafting understanding.

I'm almost about to post that xkcd 810

It's an interesting example of the metric becoming a target. Simon started drawing pelicans because it wasn't something that existed before.

There’s a small albeit nonzero chance that frontier labs want Simon to stop using the pelican thing so they can draw attention to better benchmarks

As far as I can tell they all still understand that it's a joke.

Another format that's worth investigating is Asciidoc. It supports the richness of Docbook XML but has fewer quirks than rST in my eyes.

would it make sense to just go for pandoc instead?

Sorry if this is somewhat pedantic, but I believe that only US companies (and possibly only Delaware corporations?) are bound by the requirement to maximize shareholder value and then only by case law rather than statue. Other jurisdictions allow the directors more discretion, or place more weight on the company's constitution/charter.

References only have a single bit available as a niche (the null byte), which Option makes use of for null pointer optimization (https://doc.rust-lang.org/std/option/index.html#representati...).

In principle, you Rust could create something like std::num::NonZero and its corresponding sealed trait ZeroablePrimitive to mark that two bits are unused. But that doesn't exist yet as far as I know.

There are also currently the unstable rustc_layout_scalar_valid_range_start and rustc_layout_scalar_valid_range_end attributes (which are used in the definition of NonNull, etc.) which could be used for some bit patterns.

Also aspirations to use pattern types for this sort of thing: https://github.com/rust-lang/rust/issues/135996

Asciidoc corresponds directly to DocBook XML. They're two formats with exactly the same semantics.

MCP is an example of "worse is better". Everyone knows that it's not very good, but it gets the job done.