Tvix explicitly targets stable Nix features, so supporting Flakes is a non-goal.
Many users have a poor understanding of what Flakes _actually_ are: They are a bit of UX glue on top of existing Nix features:
- Input/output schemas for `flake.nix`
- A lock file format
- CLI features to work with the two above
It's entirely feasible to build out a Flake user interface & evaluation support on top of Tvix without making it a first-class evaluator feature.
See https://github.com/edolstra/flake-compat for prior art.
The key point of Tvix _not_ having support for Flakes is to not make special snowflake evaluator features that are tied in with it.
This is only true if use a Docker based workflow using `FROM nixos/nix`.
This image exists mainly as a way for people to try out Nix with, not to build production images on top of.
We ship many things which bloat the image size but makes it nicer for interactive usage.
Using dockerTools from nixpkgs is much better and gives you much smaller images closer to Alpine size.
Lenovo's paid warranty has been fantastic for me in the multiple countries where I've used it (Sweden, Hong Kong and Mexico).
In all three they sent out a local service technician that fixed the problem on-site.
Once it was a a worn out SSD that was replaced with one twice as big as that was the only thing they had in stock (Sweden), another time it was a broken connector on the motherboard (Hong Kong) and the third time it was a broken display (Mexico, Cozumel).
I was most impressed by the service in Mexico as it's pretty far from any major cities and the technician came out after only a day.
If good warranty service is important to you I cannot recommend enough to get a Lenovo (T, P or X series) laptop and shell out for the extra warranty.
I exclusively use the trackpoint for mouse input and configuring the edge scroll to occupy the entire touchpad meaning that I can use my thumb to scroll without moving my hand away from the trackpoint.
In libinput the edge scrolling is hard coded to 7mm and previous attempts at making it configurable were rejected.
Many users have a poor understanding of what Flakes _actually_ are: They are a bit of UX glue on top of existing Nix features:
- Input/output schemas for `flake.nix`
- A lock file format
- CLI features to work with the two above
It's entirely feasible to build out a Flake user interface & evaluation support on top of Tvix without making it a first-class evaluator feature. See https://github.com/edolstra/flake-compat for prior art.
The key point of Tvix _not_ having support for Flakes is to not make special snowflake evaluator features that are tied in with it.