4 ms·
Why won't they do these things? At the very least, you will only need to provide one binary, rather than one per architecture.
by stavros 3y ago
Why won't they do these things? At the very least, you will only need to provide one binary, rather than one per architecture.
- lolinder 3y agoBecause the burden of compiling a binary per architecture is microscopic when you're dealing with something like postgres or redis or memcached. Someone sets up a CI pipeline that compiles binaries for the supported platforms. The pipeline produces the required binaries with each release. These projects care far more about performance than they do about ease of compilation or even of installation, because they're compiled once and run trillions of times in performance sensitive contexts. As I noted in reply to a sibling, I could see it being useful to run in a browser as a sort of learning playground, but that is not how people are going to deal with their production DBs—the bottleneck represented by WASI is not going to be worth it.