weebull

5 ms·

1.
by weebull 1mo ago
I found that they didn't want to call tools in the same way as other models, and it led to bare tool calls in the response.
2.
by weebull 1mo ago
...or...just hear me out now...we could limit it in the harness. Don't give it shell access, just predefined tools.
3.
by weebull 6mo ago
Two different philosophical approaches with Zig and Rust. - Zig: Let's have a simple language with as few footguns as possible and make good code easy to write. However we value explicitness and allow the developer to do anything they
4.
by weebull 6mo ago
Clock rate isn't the only factor. A design can be power hungry at a low clock rate if designed badly, and if it it is... you're never getting that think running fast.
5.
by weebull 6mo ago
All of those things are solved with modern extensions. It's like comparing pre-MMX x86 code with modern x86. Misaligned loads and stores are Zicclsm, bit manipulation is Zb[abcs], atomic memory operations are made mandatory in Ziccamoa
6.
by weebull 7mo ago
Wtf‽ I didn't know that was possible.
7.
by weebull 7mo ago
> Yet ironically getting Claude Code to run at 60fps is way way harder in a TUI? That's what happens when you vibe code your app.
8.
by weebull 7mo ago
Given that Mandarin has many forms of "yes", isn't the problem that all those forms map on to our singular "yes". For a native speaker "yeeeessss" means something very different to "yes", but the
9.
by weebull 7mo ago
How about we leave "...shoring" alone?
10.
by weebull 7mo ago
> Question: Did photoshop kill photography? Because honestly, this AI discussion to me sounds very much like the discussion back then. It killed an aspect of it. The film processing in the darkroom. Even before digital cameras were ubiqu
11.
by weebull 8mo ago
> Why you think the net was born? > Porn porn porn
12.
by weebull 8mo ago
My biggest complaint is there's no way to name a signal because a wire isn't a thing. You instance gates and give those names, but wires are anonymous connections between gate pins. I think this is backwards. Knowing that a signal
13.
by weebull 8mo ago
I think it's more likely you become a danger for others. A safe space for malware
14.
by weebull 8mo ago
If you're using dlopen(), you're just reimplementing the dynamic linker.
15.
by weebull 8mo ago
As Blair got most institutionalised to the world of politics he became more and more authoritarian. Starmer appears to be listening to Blair who is now even worse than he was as PM. Labour generally has a "paternalistic authoritariani
16.
by weebull 8mo ago
> "We don't need destructors, defer/errdefer is enough" is Zig's stance, and it was mostly OK. There's more than that. Zig has leak detecting memory allocators as well, but they only detect the leak if it ha
17.
by weebull 8mo ago
A 50-ish MB build time dependency that doesn't need any special privileges or installation to run? That's over engineering? A binary release of just CMake is bigger than all of Zig.
18.
by weebull 9mo ago
There's one area I wish we did differently which I think is a hang-over from big-endian. It's the order of bytes when we write out hex dumps of memory. You'll always get something like this: ``` 00000000 : 00 01 02 03 04 05
19.
by weebull 9mo ago
> - we have authentication everywhere in our stack, so I've started including the user id on every log line. This makes getting a holistic view of what a user experienced much easier. Depends on the service, but tracking everything
20.
by weebull 9mo ago
> Zig, for all its ergonomic benefits, doesn’t make memory management safe like Rust does. Not like Rust does, no, but that's the point. It brings both non-nullable pointers and bounded pointers (slices). They solve a lot of problem
21.
by weebull 9mo ago
It is intended for release builds. The ReleaseSafe target will keep the checks. ReleaseFast and ReleaseSmall will remove the checks, but those aren't the recommended release modes for general software. Only for when performance or size
22.
by weebull 9mo ago
And hardware access. You absolutely can't write a hardware driver without unsafe.
23.
by weebull 9mo ago
I personally feel the Zig is a much better fit to the kernel. It's C interoperability is far better than Rust's, it has a lower barrier to entry for existing C devs and it doesn't have the constraints the Rust does. All whils
24.
by weebull 9mo ago
So if you're writing a device driver in rust... - Hardware access is unsafe - Kernel interface is unsafe How much remains in the layer in-between that's actually safe?
25.
by weebull 9mo ago
I don't understand why. Working with hardware you're going to have to do various things with `unsafe`. Interfacing to C (the rest of the kernel) you'll have to be using `unsafe`. In my mind, the reasoning for rust in this sit
26.
by weebull 9mo ago
Learn rust to a level where all cross language implications are understood, which includes all `unsafe` behaviour (...because you're interfacing with C). Yes it does.
27.
by weebull 10mo ago
That just highlights that the way people are interpreting the word `master` is wrong. You've named your most important branch "teacher".
28.
by weebull 10mo ago
I hope you never come across a repo that has an old out-of-date `master` branch, because they moved to using `main` in a bad way.
29.
by weebull 10mo ago
Master of Puppets -- Metallica To be fair, the song is about control and the abuse of power.
30.
by weebull 10mo ago
I'm also wondering what payload people want. There's already an error handling trace (similar but different to a normal stack trace) that captures the how the error propagates up to the point it's being handled so shows you e

More ›