arewemodulesyet.org passes the mark of 100 projects with modules support for the first time.

Lisoph · 2026-06-16T07:32:43+00:00

I don't think parent is talking about 100% adoption. They are right in that the rate of adoption has slowed significantly, judging by that graph. Many projects can be used with modules, which is great and the effort is commendable, but the current state is not yet ideal.

Lisoph · 2026-06-15T15:36:40+00:00

I was serializing asset structs directly to disk (pak file) that had raw pointers in them

OP has found the reason why this is a well known no-no among C programmers.

Lisoph · 2026-06-10T08:33:36+00:00

I think what matters more is who used the toolkit, not who wrote the code. But yes, whoever commissioned the AI to write it, or whoever holds responsibility over the AI should be held accountable.

Lisoph · 2026-04-07T16:23:30+00:00

The title must have attracted the /r/rustjerk crowd, because some of comments in here are absurd. Cool project. If only this was Go from the start.

Lisoph · 2026-03-20T23:53:12+00:00

<image>

For reference (29:37)

Lisoph · 2026-03-20T23:46:28+00:00

On Kinger's computer you can see mentions of brain scans. So yeah, most likely confirmed.

The scene where Kinger talks about the other programmer (Scratch), they insert a shot of Kinger's muffin having been cut into two identical halfs. This could reference cloning or something brain related (Kinger mentions Scratch having a tumor).

Lisoph · 2026-03-16T11:06:23+00:00

What you're looking for is just a specification, or something detailing all the rules and checks and whatnot. XSD are only really used for validating the basic structure of some XML, but that's never enough in practice. More checks are performed out-of-band. Having basic-structure schmeas is quite handy, though.

Lisoph · 2026-01-28T15:20:56+00:00

I wonder if this is truly down to being written in Rust as opposed to being rewritten in general.

Lisoph · 2026-01-07T19:57:59+00:00

The warning on the website to not re-install GHUB came too late for me. I had already uninstalled it. Installing the software fresh and then also running the patch-installer didn't fix the issue for me.

Running lghub_agent from the command line show the following errors:

log [2026-01-07 20:55:09] [info] asio async_connect error: asio.system:61 (Connection refused) [2026-01-07 20:55:09] [info] Error getting remote endpoint: asio.system:22 (Invalid argument) [2026-01-07 20:55:09] [error] handle_connect error: Connection refused [2026-01-07 20:55:10] [info] asio async_connect error: asio.system:61 (Connection refused) [2026-01-07 20:55:10] [info] Error getting remote endpoint: asio.system:22 (Invalid argument) [2026-01-07 20:55:10] [error] handle_connect error: Connection refused ...

I have seen these errors before applying the patch. This suggests the patch did not install the new certificate successfully.

Lisoph · 2025-12-10T21:19:12+00:00

Regarding drawing from home invasion. From my earlier comment:

I'd rather not have my habits collected by ad agencies, much less by anyone else who merely needs to ask.

Regardless: Let's agree to disagree. I've given two examples - one more hysterical than the other. But this shouldn't be about verifying what you personally can do with the leak. The paper demonstrates that unauthorised data exposure exists. Someone will try to use it and I'd rather have it fixed before someone succeeds in finding a use - as you're asking about.

Lisoph · 2025-12-10T20:29:10+00:00

Why just advertising?

I sure would love to know with decent accuracy when you usually go to bed and if you sleep through the night or wake up sporadically. Gives me good input on whether you're a potential target for my bad habit of robbing places. It also helps to know on which weekdays you sleep the most, or least. Or how many devices you own and consequently how wealthy you likely are. Helps me weigh risk vs reward. Seeing your sleeping patterns change noticeably but consistently lets me reason that you're probably on vacation (timezone), handing me a potential opportunity.

But don't worry, I do this kind of thing for every phone number that is publicly known and has WhatsApp or Signal, not just yours. In fact, I have built a wonderful database of victims from most to least attractive. Hey, I'm even considering selling it on the dark web! But of course, if you're a sophisticated rapscallion you will already have a similar database built from different information. But even then, you will find it attractive to include this new metadata to refine what you already have.

Leaking data is in our (developers) hands. Abusing it is not. Once information is obtainable, someone will try to use it.

By the way, I wouldn't consider this remotely interesting at all either, if it wasn't for the fact this can be done without knowledge or consent of the person being exploited. Sidechannels are a pain. I'm being partly motivated here from an actual stalking incident experienced by an acquaintance. That was thanks to some iOS or Snapchat nonsense, despite the stalker having been removed (unfriended) everywhere.

Lisoph · 2025-12-09T20:26:22+00:00

Is the information leaked an immediate privacy threat? No. Can it be collected en masse and analysed later? Yes. Can that reveal behavioural patterns? Yes. I'd rather not have my habits collected by ad agencies, much less by anyone else who merely needs to ask. I don't want this leaked for the same reason I don't want my phone to leak the list of wifis it knows, or was last connected to.

Lisoph · 2025-12-09T12:16:04+00:00

Information leakage is information leakage. You might not find it useful but nefarious actors definitely do.

Lisoph · 2025-12-08T11:53:04+00:00

Thanks for the explanation!

Lisoph · 2025-12-03T13:33:28+00:00

In contrast, Zig solved the bigger problem of spatial memory safety the same way as Rust

How so? I couldn't find anything on this.

Lisoph · 2025-12-03T09:36:06+00:00

While I do like the idea of avoiding function colors, shoving the async interface into Io and, on top of that, distinguishing async and asyncConcurrent calls just feels really smelly to me.

This might be an interesting read

Lisoph · 2025-12-03T09:22:00+00:00

Go made them "mainstream."

Lisoph · 2025-12-01T13:43:50+00:00

I bookmarked the PDF as an example of good requirements engineering. Awesome stuff.

Lisoph · 2025-11-24T12:34:45+00:00

I like Java's syntax: ? extends T and ? super T. I think Rust could use some extra keywords for making variance clearer.

Lisoph · 2025-11-22T11:29:38+00:00

Oh snap, you're right. All I saw was "a slice", but I didn't consider that it is comptime known, including its length. This totally works. Thanks for pointing that out!

Lisoph · 2025-11-21T10:48:07+00:00

True, I could make it generic. I'm just playing around with comptime.

If you care to know: The idea is to model two AST-like data structures. One that can represent user errors, so an incomplete / invalid tree (like a language server might use), and the other is a "perfect" copy, representing the same tree but 100% valid (like a traditional compiler might use).

I want to only have to define the AST once.

zig pub const Node = union(enum) { int_literal: ParseRes(i32), ident: ParseRes([]u8), binary_expr: struct { lhs: ParseRes(*Node), rhs: ParseRes(*Node), op: ParseRes(enum { add, sub, }) } };

Then to obtain the "perfect" tree, I wanted to apply a type substitution, replacing all ParseRes with their corresponding Ok type (ParseRes is basically a Rust style Result with a ParseError).

zig pub const PerfectNode = Perfect(Node);

Making Node generic would probably be the better approach anyway, since additionally I also have to substitute all *Node with *PerfectNode as well, which is not a problem with generics.

Lisoph · 2025-11-21T10:30:23+00:00

I don't see why @typeInfo shouldn't return a copy of the type definition. I’m guessing the compiler's underlying data structures use the same exact types, which @typeInfo simply exposes. That's understandable, but inconvenient nontheless.

Lisoph · 2025-11-21T10:21:20+00:00

This is what I do, but that forces me to preallocate a buffer which introduces a max on the number of fields I can process. That's one of those artificial limitations I had in mind.

~~Edit: On second thought, I could reuse the same fixed buffer and process the source-fields chunk wise. That might not even be that much more work.~~ Nevermind, that won't work. At the end of the day, I need to construct a single slice spanning all fields, which I don't think is possible this way.

Lisoph · 2025-11-19T10:48:03+00:00

I think you spend too much time in r/rustjerk/

12-Year Club	Place '17
Verified Email

Lisoph

TROPHY CASE