Rucadi

Passwords are a pain in the ass, I just wished that having a cryptographic key installed in your device (and linked to it) to login to stuff or having an external crypto-device to login was easier and more common.

For local access, biometrical is fine, and a "super-secure" password for if something happens that can only be used once would be the way.

Best tool I've seen for diagrams in a long time, Congratulations! I'll use this anywhere.

Regardless of that, the only function that requires this extension is the "except" macro, if you are willing to not short-circuit, you can still use the other functionality of this library.

RVO/NRVO are valid and are not affected.

We are dealing with std::variant, and the move semantics are defined by the alternative. https://en.cppreference.com/w/cpp/utility/variant/operator%3...

The main problem with IIFE is the same as with a normal function:

You cannot return the caller function from inside the closure, making the "short-circuit" mechanism provided by questionmark (?) operator not possible.

With the GCC Extension, we get around that using a construct that is pretty similar to IIFE, it allows to return a value from an immediate expression created by a block of code that is surrounded by ({})

The nice thing about this block ({}) is that the last statement is used as the "return value" without an explicit return, this disambiguates between the "expression" return and the "function" return.

Without compiler support, the short-circit is not possible, but with this feature + macros we can create a function that behaves like that.

Python's "mistakes" are my weapons in my restricted corporate production system.

Hacked pretty fast a version with json support, not pretty but just as a concept: https://github.com/Rucadi/lc

And just use concepts and call it a day.

John Ericson (@Ericson2314)

You can read a post on that here: https://lastlog.de/blog/libnix_roadmap.html

I don't think nix is that awful, while there are some tasks that are more difficult or can be a little bit verbose (if you want to play a lot with the attribute sets / lists or string manip) When using nix most of the time you'll end up just writing bash or using it as a templating language.

Why are flakes such a deal-breaker? While not ideal, you can still tag your versions in the .nix file instead of the lockfile.

I even had to avoid flakes in a system I developed used by ~200 developers since it involved a non-nixos OS and it involved user secrets (Tokens etc...) So with flakes I had to keep track of the secrets (and was a pain point, since they obviously didn't have to push them into the git repo) but nix flakes doesn't handle well omitting files on git (it ignores them also on nix commands). In the end, the workarounds were too messy and had to drop flakes entirely.

For me the killer feature is Windows Support, Ericsson is doing a great job bringing nix into Windows, but the process it's understandably slow, If this project is similar enough to nix that I can kind-off translate easily the zb derivations to nix derivations, I'm willing to use it in windows (It's not like nix has windows programs in the nixpkgs either way I have to bring them in my own).

The problem for me is that I see no benefit on using this over nix language (which I kinda like a lot right now)

Nice tool :) I did something similar in a hackathon some years ago. https://github.com/Rucadi/wsld

It's totally unmaintained and forgotten :D

In general, what I do now to generate WSL images is to docker run a container, and then export it to a .tar, finally, install that tar, is that easy.

However, if I had your tool installed, for sure I would use that for ease of use.

I like the newest* introduction of allocators, PMR, I use it quite a lot.

It can transform the society into a poor one with shortage of goods.

at this point Oracle is no different than ransomware

If a message platform is gov controlled, criminals will use other alternatives that are not monitored, which they probably already do.

What you end up is just having the gov having all information about private citizens, which can be used against us.

For example, the government of Spain constantly shares private citizen data of people near political adversaries for political reasons, also, I don't want people knowing what I share with my girlfriend, regardless of it they do something or not with it publicly.

It's just an usually bigger password.

People are already in power to ban single-use plastic, they can buy stuff that is more expensive or less convenient to get.

This gives a signal to the market that if a lot of people does it, they should move in that direction to meet the demand.

However, this is not what it's happening, and that's because people appreciate that something is cheaper thanks to single-use plastic of because they are not so interested in single-use plastic that they are willing to do an effort to go around it.

Basically, what people reveal when in the everyday use is that they are fine with single-use plastic, and if they say otherwise is to signal some kind of virtue because they decide not to put effort into it.

The only exception is people that know the consequences on their every-day life.

I want to share a tool I've been using recently, which I think is fantastic.

It's an OverlayFS driver for Docker that lets you mount a host machine folder into your containers. The cool part is that it behaves like a volume, allowing the container to modify the folder's contents, but these changes remain isolated to the containers that use that volume.

It shares the same semantics of a Docker container, so it's pretty usable, I'm using it so much that I'm surprised this is not a default driver in docker.

If you mark a derivation as impure with __impure=true; and activate "ca-derivations flakes nix-command" as experimental features, you can access the internet.

I agree sometimes is a pain tho.

But most of the time, If you need internet access, if you can specify the "hash" of the result file, anything that you do to achieve that file can have internet access.

I assume they thought that OpenAI and Google would have used that data anyways without a clear way to prove otherwise.

That's what NASA wants us to think.

Now that Linux has a rather good NTFS support, it should be possible to just have a folder in C:\Linux with the plain rootfs in there without any kind of virtual disk.

A lot of people trash about bun, but I think that they are highly motivated people bringing a lot to the table.

I mean, the performance would be abysmal.

This seems to be from 2 years ago, a lot of things could have changed.

He seemed quite opinionated on flakes, but the only bad thing that I can see to flakes is that you cannot pass args to them, for imo no valid reason, you have to use the file+file protocol and update the inputs each time to have a reasonable way to pass parameters...

One useful webpage this project provides is this godbolt for nix:

https://bolt.tvix.dev/

really useful.

I couldn't test this because it fails to install on nixos inside a venv (some error with onnxruntime? when calling termax).

It seems fine, but I would appreciate a nixos package for this.

on the other hand, How is the LLM configured? Does it support llama etc...? Does it provide an automatic way to install the LLM?