RaitoBezarius

30 ms·

1.
by RaitoBezarius 2mo ago
I'm part of the sysadmin team who studied the migration paths for the Dendrite in question in this blog post and unfortunately as a volunteer it's hard to find the time to invent migration paths (even if we have the knowledge) and
2.
Misadventures in DTrace: how to debug the macOS kernel(jade.fyi)
2 points by RaitoBezarius 1y ago|0 comments
3.
by RaitoBezarius 1y ago
Hello, we already have the name: http://lix.systems/ . It'd be great if you would consider another name otherwise we will have to compete for the SEO and confuse a lot of our userbases :(. Good luck with your product!
4.
by RaitoBezarius 2y ago
https://git.lix.systems/lix-project/lix/src/branch/main/src/...
5.
by RaitoBezarius 2y ago
> The security team is composed of unpaid volunteers who work on numerous time-sensitive projects simultaneously. You may not be aware, but since a group of maintainers and contributors left earlier this year to form their own fork calle
6.
by RaitoBezarius 2y ago
Tvix is compatible with Nix, thus it follows the /nix/store/$hash-$name naming scheme.
7.
by RaitoBezarius 2y ago
(Tvix developer here) 2 years after, Flakes are still what they are, IMHO, a pile of layering violations. I do not see a path forward for them in Tvix before we get to fix them layer by layer, which Nix is trying to do (slowly?). At some po
8.
by RaitoBezarius 2y ago
Tvix developer here; Tvix is quite different from Nix and is a clean restart, in my humble opinion, it would be quite hard to integrate some features of Tvix in the current Nix because you have two targets: (a) getting the feature in the ex
9.
by RaitoBezarius 2y ago
Tvix developer here; we do have Windows in mind. Rust makes a bunch of things easier regarding this, but _not everything_. It's not a priority. The location of the store is not really the main blocker in those sorts of situations, IMHO
10.
by RaitoBezarius 2y ago
Tvix developer here; correctness is still not guaranteed, there's nothing to use here except if you already understand well Nix concepts to pick parts and build stuff on the top of it and accept the inherent instability :).
11.
by RaitoBezarius 2y ago
Not ready, so not a good reason to use it yet.
12.
Building Ubuntu Images in Nix(linus.schreibt.jetzt)
5 points by RaitoBezarius 3y ago|0 comments
13.
by RaitoBezarius 3y ago
I moved to npins which has slightly more features that niv. But niv has been great, I wish we can have patching natively so all my tons of patches can be bolted on faster.
14.
by RaitoBezarius 3y ago
For example, Flakes have no concept of cross compilation and makes this use case extremely tedious to use. Flakes were a RFC then merged as an experimental feature and shilled too much to the community to the point they are now a quasi stan
15.
by RaitoBezarius 3y ago
Honestly, we are an open source project, not a company. If we have the money, of course, we would prefer to spend it there and do better and more with it. If this is threatening in a serious countenance, our growth and ability to conduct ou
16.
by RaitoBezarius 3y ago
It is also probably impossible given some sources completely disappeared.
17.
by RaitoBezarius 3y ago
Did you mention sandboxed builds? Actively preventing pip to execute code arbitrarily at install time? Same for Node.js? I cannot live without that anymore, that's the new golden standard.
18.
by RaitoBezarius 3y ago
Those benchmarks are wrong and misleading. Tvix contributor (but mostly reviewer I would say) here. We still don't have finished the integration with our own store, using the Nix store forces us to be slower than Nix, therefore the cla
19.
NixOS 23.05 beta is released(github.com)
4 points by RaitoBezarius 3y ago|1 comments
20.
by RaitoBezarius 3y ago
Nix. :-)
21.
by RaitoBezarius 4y ago
Flox has some solution for this. Other than that, this is being worked on :).
22.
by RaitoBezarius 4y ago
It really is interesting. What was shown was the ability of systemd to have restart policies of units and the ability to load secret over some sort of Unix socket primitive. Plus, it does not even try to do topological sorts, it restarts ev
23.
Linkal: Calendar Aggregation Server in Rust(github.com)
3 points by RaitoBezarius 4y ago|0 comments
24.
by RaitoBezarius 4y ago
No you cannot fit their whole tree of dependencies, their semantics and their failures modes in a single HN comment. People use basic tools because they have much more understandable semantics, everyone do not need a gigaton pile of Go code
25.
by RaitoBezarius 4y ago
You can use something like Nix or Guix for example. Bonus: it produces OCI images also.
26.
by RaitoBezarius 4y ago
I definitely not believe that Docker images are boring, they are full of constant issues and stuff you have to keep track on the top of the fact they are not composable in many ways. Rootfs is the boring technology, their semantics is clear
27.
by RaitoBezarius 4y ago
Well, Guix is also mentioned when someone talks about Nix, seems fair to me (and of course, Guix may be more relevant sometimes!).
28.
by RaitoBezarius 4y ago
Then, you had disaster recovery plans, you devised a strategy of what is an acceptable data loss, execute the reconstruction plan on the new big server , under some hours, the new big server is up again. You apologize, offer some financi
29.
by RaitoBezarius 4y ago
I'm tired to read this as if it was impossible. > How do you implement healthcheck? Most applications implement a simple endpoint which returns a known answer (whether it's an HTTP 200 code, a banner, etc.) You can just hit thi
30.
by RaitoBezarius 4y ago
Ha, that's something I was working on and I had a little proof of concept with Aleph.

More ›