Dessalines: :bugs-no:
I'm sure his ideas have advantages and the lemmy devs can be frustrating to work with but he literally showed up yesterday spamming the matrix chat and now this
Dessalines: :bugs-no:
I'm sure his ideas have advantages and the lemmy devs can be frustrating to work with but he literally showed up yesterday spamming the matrix chat and now this
Two different minds, guy is going about it the complete wrong way certainly. Not sure why they went with a CI tool without artifact caching though. If the builds are reproducible, I'm not super familiar but I think Rust at least should be and then the frontend is just JavaScript stuff so that should be too, I'd just take advantage of the faster CI process and do whatever (probably very) small changes are needed in the future to keep the two in sync.
Yeah. I'm a little bit conflicted but the guy is enough of a douchenozzle that it's like no, nobody is going to bow down to your powerful logic brain man, fuck off
He's in the matrix saying "oh its just a proof of concept I wasn't asking them to merge/use it now"
communication skills on redditors; :not-good:
Rust compilation units are much larger than those in C / C++. A C compilation unit is an individual source file. All the source files get compiled, then this is followed by a linking stage. You can edit one C source file, recompile that single source file, then re-link against all the other pre-compiled objects. In Rust, the entire module (library or binary) must be compiled as one unit. There is no distinction between headers and source files, so when you edit a source file, it impacts everything else which imports from it. It is much more convenient to program IMO, but the compilation process is for small changes is notably slower.
Hopefully they're not re-compiling all the dependencies every time though.