Hemera @Hemera@meow.social

Once again using #nix is a joy.

I've got some rust library I need to build for both linux and windows platforms on x64. With nix its as easy as saying 'please build the linux version' and 'please build the windows version with this linker'.

French Train stations:
- They scan your ticket before getting on the train
- People everywhere helping you getting on the correct wagon/place
- You actually feel like if there's an issue you will know about it and can respond

German train stations:

- You can find information about arrivals on the left side of this station
- You can find individual train information on the right side of the station

🤔

Would love to hear some opinions on this! (With a potential boost?)

Some possibilities:

If one writes an application that is ultimately meant to be run as a system service, how should one handle the 'interactive' situation w.r.t. error handling and help?

For example, imagine that on error you were given an 'error explorer' but of course in a non-interactive context (i.e. as a service) this is not useful and instead the complete error is printed.

How should this be handled? I am not a huge fan of doing terminal detection...

https://blog.dbsmasher.com/2022/05/24/not-my-job.html

Good read

The joys of nixos :D

> Switch from channel to flakes in my home-manager
> forget rebuilding on my other machine
> Fix a small thing
> sudden 2GiB update

It's what I asked for, but man

Generics are not an option here sadly, unless there is a way to 'erase' them here (without unsafe ;) )

I wish I could let an external crate control behavior without introducing trait objects and unnecessary derefs in between...

But at the same time, that feels like a hack to me, since you can certainly CREATE an ARTICLE on a PLACE, but how will that federate? And how will others consume and display this?