skavi

9 ms·

61.
by skavi 7mo ago
blends
62.
by skavi 7mo ago
Since Geekbench 5, the single threaded benchmark scores have aligned pretty well with those from the industry standard SPEC benchmark.
63.
by skavi 8mo ago
thank you. TFA is just an awful read.
64.
by skavi 8mo ago
I’m curious what issues people were running into with Swift’s built in C++ interop? I haven’t had the chance to use it myself, but it seemed reasonable to me at a surface level.
65.
by skavi 9mo ago
Just yesterday someone was telling me xmake does a lot of what bazel can do (hermetic, deterministic, optionally remote builds) while being easier to use. I took a look at the docs later and couldn’t find a direct comparison. But there does
66.
by skavi 9mo ago
These guys aren’t going to use L4T. ACPI compliant, standard GPU drivers. They’ve also upstreamed a lot of the L4T patches. See DGX Spark.
67.
by skavi 9mo ago
In Nix (and, I’d assume, for Guix) you can go the other way around: https://mitchellh.com/writing/nix-with-dockerfiles . As a side benefit, the generated docker image can be very tiny.
68.
by skavi 9mo ago
Dunno about Skip, but I can always tell when an app is Flutter. They feel like crap. Everything's a bit off with the native looking widgets. And fully custom designs still animate a bit weirdly. And they definitely still stutter. Someh
69.
by skavi 9mo ago
I’m not sure if the GUI in that image is real or a placeholder, but I really like what I see. Reminds me a lot of the skeuomorphism from classic iOS and WebOS, but cleaned up with elements of modern “flat” designs.
70.
by skavi 10mo ago
It feels pretty clear to me that these Contracts should only be used for the “very certain” case. Writing code for a specific compiler flag seems very sketchy, so the programmer should assume the harshest interpretation. The runtime check t
71.
by skavi 10mo ago
There’s no necessary performance hit for closures. The performance cost here is caused by these closures needing to conform to a function pointer looking interface in order to be generally useful in C.
72.
by skavi 10mo ago
I think maybe this post would make more sense if you were familiar to its antecedent [0] which compares existing closure extensions to C. IIRC the comparison was in the context of considering designs for standardization. [0]: https:/&
73.
by skavi 10mo ago
> Rust closures that capture data are fat pointers { fn , data } This isn’t fully accurate. In your example, `&mut C` actually has the same layout as usize. It’s not a fat pointer. `C` is a concrete type and essentially just an anon
74.
by skavi 10mo ago
Cargo does not attempt to solve the same problems as Nix (if you depend on any software not written in Rust). A checked in Nix shell is genuinely great documentation on the expected system environment.
75.
by skavi 11mo ago
I wonder if this would be a simple (limited) example of defeating the watermarking? Surely there's no way SynthID is persisting in what is now a handful of pixels.
76.
by skavi 11mo ago
> Well, I genuinely think the word "feminism" means different thing in Korea to the places I've lived at. It has much more inflammatory undertone there whereas in NZ, its just a term. When I see "anti-feminism" f
77.
by skavi 11mo ago
You caution against a knee jerk reaction to Lee’s anti-feminist views but the background you provide does not actually justify your implication that South Korea may be a special case. A feeling that “the pendulum has swung too much in the o
78.
by skavi 11mo ago
“dying behind bazel walls” is a bit dramatic when it’s a freely available tool that anyone can learn and use. imo, it’s also among the very few options that try to solve the hard problems of build systems (alongside Buck and maybe Nix).
79.
by skavi 11mo ago
Personally, I understand perfectly how it works. But even with the retroactive start, it tends to miss the first five or so minutes. There are also stats on the screen during tracking that ideally should appear as early as possible.
80.
by skavi 11mo ago
Maybe the 2026 Apple Watch will be able to auto detect running as reliably as my 2015 Samsung Gear S2. My 2022 Series 8 is certainly not there yet.
81.
by skavi 11mo ago
I was thinking of this: https://www.theverge.com/news/637469/microsoft-office-speed-...
82.
by skavi 11mo ago
IIRC they started preloading Office application recently as well.
83.
by skavi 11mo ago
Well it's a fairly entertaining read as someone with no current ambitions of solving any of these crises.
84.
by skavi 11mo ago
John Lions is not Lions OS is not is not Clancy the Lion
85.
by skavi 11mo ago
I think the point is that they don’t both work equally well.
86.
by skavi 11mo ago
I think some interesting context is that this person is fascist. https://x.com/RoguesPhilo/status/1990332234029793537 https://x.com/RoguesPhilo/status/1990445865903980759 https:/&#
87.
by skavi 11mo ago
I went to U of I and I’m super curious about that “ I-L-L / I-N-I” option. Any chance someone’s found out what it does?
88.
by skavi 11mo ago
Intel has a reputation of producing relatively high quality drivers for Linux.
89.
by skavi 11mo ago
If do_async_thing was implemented as below, i can’t imagine the futurelock post getting anywhere near this much attention. As for why you might use an async lock in a future which acquires and unlocks in the same poll, there still may be ot
90.
by skavi 11mo ago
futurelock [0] was special specifically because of this aspect where even a future which seemingly acquires and releases a lock in a single poll triggers a deadlock. what you describe is just a standard async deadlock. much easier to spot w

More ›