prospero

My point is that the creator/user dichotomy exists at every level of software.

Show me a software developer who isn’t an end user for someone else’s code.

Here’s one in Java: https://github.com/lacuna/bifurcan/blob/master/src/io/lacuna...

Yes, and that is used as an example for the general point: a network transparent API doesn’t help us understand the network when it inevitably fails.

The point is that an interface should help you to both ignore and understand the underlying implementation. I'm not sure I understand your point about data and transport, since most interfaces (e.g. names) don't touch the network. Are these just synonyms for interface and implementation?

It's very plausible that these techniques could be used to fix the output of a CSG library that uses floating point math, but I'm not sure what the specifics would look like. If anyone has ideas in that vein, I'd be very interested to hear them.

Hi, author here. I looked into that side of things, but CGAL only offers exact precision implementations for lines and circular arcs. The fact that Bézier curves are left as an exercise for the reader is further proof of the disconnect between computational geometry and modern computer graphics.

By forcing the GC to run in between tests, basically. The README for the benchmarking tool describes it in more detail: https://github.com/hugoduncan/criterium.

I tried to include these, but it wasn’t immediately obvious how to construct them from outside Scala without CanBuildFrom. If anyone wants to open a PR or even provide a few hints, I’d be happy to update the benchmarks.

Guava’s “immutable” collections are effectively read-only indices, and do not support efficient updates.