Ssnake Posted September 5, 2025 Posted September 5, 2025 Ah, the fifth circle of Dev Hell (specifically, "the terrible solution that holds everything together") Â
Ivanhoe Posted September 6, 2025 Author Posted September 6, 2025 Oh Gawd, the Java/Javascript thing.Â
Ssnake Posted October 1, 2025 Posted October 1, 2025 ...or the surprise release of carrot 2.0 which now tastes like onion, and has a strange dependency on beef 1.52, the ONLY version of beef that with a security issue that was reported years ago, but apparently carrot developers didn't read the memo (or maybe they are actually planning some nefarious supply chain attack). So, better substitute Carrot 2.0 with SweetPotato 3.5? At least it tastes similar to Carrot 1.0, but now you need to set up new compilers since SweetPotato demands support for TPM and AVX512 (which dramatically reduces cooking time, but only for SweetPotato).
Ivanhoe Posted October 1, 2025 Author Posted October 1, 2025 Yes, but SweetPotato 3.5 has extensive code base in Rust, for which the compilers check the coders' social credit scores to determine if they are politically worthy of executables. Has anyone ever tried statically linking Carrot 2.0? At least that way, future Github perfidy will not pollute legacy executables.Â
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now