Enjoying the moment!

I reworked the output of the build: nix build -L .#cargo-0_88_0-bin-fafc14832178210d --impure This shows: * build-script-build execution * usage of environment variables coming from the said execution And for the first release soon I'm very happy with the output as it is clean

Replaced the battery in my Samsung S10E myself 🧐👨‍🎓🪐 and I disconnected from charging at 9:30 and at 22 it still got 70% when normally would be around 30-40%. Too bad the battery replacement breaks the water seal and is waaaaay more complicated than on my Samsung S2. Was using

Rust error messages are just amazing. Referenced the wrong directory using a const elektrolyseur_diagram: &str = include_str!("assets/ElektrolyseurDiagram.svg");

I might be late to the party but worldguessr.com is amazing. Always wanted to have a easy alternative to the overprized geoguessr.com Enjoy!

I live in Germany and we are known to print the internet. Turns out I learnt something cool about CSS which might change _your_ life also: You can add a style.css like below and all DIVs with this class won't show up in print. I've simply added this to the menu and footer. It is

Just discovered that you can ask grok about what people discussed in the comments. Outstanding! X Thank you!

Finished my work on h2wasserwende.de/tool using rust+leptos and now getting back to libnix. The plan is to integrate the nix build part directly into 'cargo build' in the coming days.

The biggest issue when using git, everyone just commits. If your lucky, then there is a branch with a meaningful name. Virtually nobody maintains a README.md update what is going on in the branch. I wish there was a branch description or branch log feature.

Just discovered that you can click RMB (right mouse button) on any line in vscode and it will generate a link you can share with others. Amazing!

When building a rust crate using a build.rs script in vanilla cargo: it will be executed as build-script-build and cargo parses the output. Cargo keeps running and spawning Work tasks, parse the output and continue with Work tasks. The cargo nix backend I'm

I'll try this next: 'cargo build' generates target/nix/debug/derivations (same for release) and the generated documents are a symlink to the nix store. So 'cargo build' uses 'nix store add-path /path/to/my/files'. I still have no good idea how to enable the user to tweak the

libnix update for cargo/rust: Seems I can't use flakes in my 'dynamic' build system for debug/release as a) they must be at the project root b) they assume files are commited to git at times c) they have dynamic properties, like build debug (different folder) than build release

Just realized that the humans casualties counter in Terminator 2 are floats. So terminator OS is not s strict in terms of type safety. 🤣

'cargo build' using the nix-backend is now online at github.com/nixcloud/cargo and after the build it will print something like shown in the screenshot below. just add a /bin/cargo-target-symlinks to the path and execute it, it will symlink the 'cargo' binary into