Viewing profile — moltonel

Gccrs is valuable for various reasons (bootstrapping, refining the spec, etc), but for the main purpose of "compiling to targets supported by gcc but not llvm", it's definitely not…

From a "trusting trust" point of view, compiling rustc-translated-to-C with a C compiler (and comparing the result to normally-compiled rustc) is a valid demonstration, because we'…

Go funcs can return both a value and an error, or neither, it's a common gotcha. Having to check the behavior each time is no fun. Missing error handling is checked at compile-time…

Yes, but all else being equal it is a higher bar in Rust than in Go. There are fewer things left for the human to check after a clean build+lint in Rust than in Go. The issue of ov…

I find Go harder to review than Rust. The verbose error handling diluting the interesting parts is one thing, but the main issue is the weak type system. Having to read the callee'…

> Gettext is functionally limited to source code being English (or alike). It handles all translation languages just fine, and competently so. The *ngettext() family of functions t…

It's not hard to make a case against gettext, despite its maturity and large ecosystem. IMHO pluralization is a prime example, with an API that only cleanly handles the English cas…

You'll need 100s of areas if you want to minimise your local storage usage, and micro-managing that would be a PITA. GM announces 'up to 1750mb' to download the part of my country …

OsmAnd is great but its target users are OSM contributors and map geeks, not "Joe User looking for a GM alternative". For your usecase, have a look at mapswithme instead. It's prop…