Oddbean new post about | logout
▲ ▼
d39f688e | 1 years ago (raw) | root | parent | reply | flag 
 @4ebb1885 I think it's because it should be in Rust these days (and can still provide a C API). No shade on the author or the algorithms, but I saw enough C things to make me skeptical.
▲ ▼
Simon Willison | 1 years ago (raw) | root | parent | reply | flag 
 @0609534c I feel like implementing that kind of a library in Rust would reduce its potential impact, because integrating Rust libraries into other languages, while possible, still isn't nearly as well trodden a path as C
▲ ▼
Simon Willison | 1 years ago (raw) | root | parent | reply | flag 
 @0609534c plus the README seems to be making the right noises in terms of "100% coverage using memory sanitizer and Valgrind"
▲ ▼
d39f688e | 1 years ago (raw) | root | parent | reply | flag 
 @4ebb1885 Mmm, I think you are wrong here. It is really not difficult to give a Rust library a C API. You give the structs a C layout via an annotation, and then provide functions as a C library would.
▲ ▼
Simon Willison | 1 years ago (raw) | root | parent | reply | flag 
 @0609534c I didn't say it was hard, I just said it was a path less trodden - for something as fundamental as a base library for this kind of geospatial work C feels like a defensible choice to me