but pipeline problems are different, for all the above reasons! the online and interdependent properties motivate using parallel threading when the source and sink of a data flow are meaningfully distinct. copying a file onto the same filesystem can often be done with a single syscall, but writing it into a network request requires buffering, even if the OS can cheat there too. that's because the filesystem and the network depend on distinct hardware resources!
Discussion
Loading...
Discussion
hell fucking YES we are adding support for x86 cygwin. ran emacs in that shit when i interned at microsoft. deep behind enemy lines
of course the fucked up little config format says hey you know what makes perfect sense to add along with specifications of what output formats to build for? that's right!! host-specific binary paths
oh you're building our programming language on your own computer instead of rented software on rented hardware? that's so cute!!! i love retro stuff like that
you cannot be fucking serious https://forge.rust-lang.org/infra/other-installation-methods.html#source-code this link is hidden in the middle of the bootstrap.example.toml. not mentioned anywhere in the fucking INSTALL.md that negs you about building from source. no they actually have fucking source tarballs too. jesus fucking christ they're up to date links too
for context, the bootstrap.example.toml file is >1000 lines of commented text
they also provide gpg signatures the way everyone else does (except pypi because they had a corporate offering to sell)
1+ more replies (not shown)
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled