HexDecOctBin

When western politicians and media lectures the world on human rights, I can't help but wonder how funny it is that because westerners front loaded their genocidal violence, they now get to feel superior to others that didn't completely wipe out the conquered.

Yeah, but then I'll have to deal with Embarcadero.

Does this support declaring variables anywhere (as opposed to only in the beginning of a function)? That was my primary complaint when using Lazarus.

How do people find Lightning cables robust? Every single one I got from Apple failed around the one year mark. So much so that I finally started buying cheap knockoffs that only lasted 6 months but cost a tenth of official ones. To compare, I haven't seen a single Micro-USB or USB-C cable fail on me whether expensive or cheap. Am I simply uniquely unlucky in the matters of Lightning cables?

> "Abrahamic bad", "Eastern good"

Is that what you read in my comment? Because that is not what I wrote. People sympathise with those who are similar to them. Europeans sympathise with Ukrainians, Muslims with Palestinians, Abrahamics with other Abrahamics. How you got from that to your "Abrahamic bad", I can't even fathom.

Abrahamic societies will naturally be sympathetic to the acts of other Abrahamic peoples and antagonistic to pagan and polytheistic cultures, especially if the non-Abrahamic culture rejects the Abrahamic proselytising that purports to "civilise the heathens" as many Indic societies did. To expect anything else under some expectation of fairness or empathy is nothing but childish naïveté.

iPads have M-series chips in them that support hardware virtualisation. But Apple goes out of its way to disable the hypervisor for its iOS/iPadOS builds[1]. All they have to do is stop doing that and allow apps to make use of the virtualisation APIs. UTM hypervisor already exists in App Store, so Apple is clearly not against the principle of it. As soon as that happens, running macOS (or Linux) will become elementary.

[1] https://x.com/utmapp/status/1708907045314035986

Is Pijul implemented in form of a library (a la libgit2)?

What physics do I need to know to follow this book?

I was attacked in this way a couple of months back. I use a different email address for each account (of the pattern product@example.com), and use a separate address for Git commits (like git@example.com). It was this second one that was attacked and I ended up with some 500 emails within 12 hours. Fortunately, since I don't expect anyone to actually email me on the Git address, I just put up a filter to send them all to a separate folder to go over at my leisure.

After 12 hours, the pace of emails came to a halt, and then I started receiving emails to made up addresses of a American political nature on the same domain (I have wildcard alias enabled), suggesting that someone was perhaps trying to vent some frustration. This only lasted for about half an hour before the attacker seems to have given up and stopped.

Strangely, I didn't receive any email during the attack which the attacker might have been trying to hide. Which has left me confused at to the purpose of this attack in the first place.

The classic Doug Lee's memory allocator[1] has explicit heaps by the name of mspaces. OP, were you aware of that; and if yes, what does your solution do better or different than dlmalloc's mspaces?

[1] https://gee.cs.oswego.edu/pub/misc/?C=N;O=D

> will improve

If only I was capable of such divination.

When I read an article, I am expecting to read the author's own experiences and insights they gained from them. Not the regurgitation of an industrial scale word generator.

> She still needed to know what questions to ask and prompts to give

Then publish the prompts. Let me enter them in an LLM of my choosing and see what bullshit it hallucinates and diff it against the 'article'.

> hopefully steered it right when it made up falsehoods.

"Hopefully"? Publishing something a stochastic parrot dreamed up under your name is ghost writing at best and spreading misinformation at worst.

If someone from Teardown dev team is here, did you guys ever tried to do the physics in voxel space? If I understand correctly, Teardown convert each physics chunk into a mesh and feeds all the meshes into a traditional physics engine. But this means that the voxel models remain constrained to the voxel grid only locally but not globally.

I have been trying to figure out a way to do physics completely in voxel space to ensure a global grid. But I have not been able to find any theory of Newtonian Mechanics that would work in discretised space (Movable Cellular Automata was the closest). I wonder if anyone in the Teardown dev team tried to solve this problem?

Is there a similar document for the memory arena feature? I tried searching the official documentation, but found scant references and no instructions on how and when to use it.

You can't scroll without moving the cursor.

> Language features like templates are not the issue – the Standard Library is.

What sins does STL commits that make it slow if templates themselves are not slow, and what kind of template code doesn't bloat compile times? In my experience, C++ libraries are usually one order of magnitude or more slower to compile than equivalent C ones, and I always chalked it upto the language.

Why do they use the bottom bit for tag and not the top bit?

Teardown calculates collision meshes and does physics on those. Not on voxels directly, and definitely on in voxel space.

So how would you do destruction physics on voxels without meshing? This is how even Teardown does it, and it uses raymarching.

One issue with Voxel-based physics destruction games is that the physics happens in continuous space (as opposed to voxel space). This means that the moment you break off a chunk of geometry, it has to be converted into a mesh and simulated like any other mesh-based model will. This makes voxels seem like more complicated Voronoi-noise based fractures. If you want the modelling workflow or the looks of voxels, it's fine. But assuming that voxels will somehow help with the destruction physics seems not to be a valid assumption.

Ideally, we would be able to do physics in voxel space itself (sort of like a cellular automata based classical mechanics), but that doesn't seem to be possible.

I often wonder what a Prolog implemented as an Objective-C like extension to C would look like. Since WAM has proper stack and heap IIRC, it might be possible to plug that in through some region-based memory management on C side. Is there some prior art like this?

Linux syscall interface is actually stable and can easily be targeted. It’s BSDs (and Mac OS) that force everyone to link to only libc.

The entire README reads like it was AI generated.

> Because what's at question in this case is the actual impact size, which to me seems quite limited.

It was widely covered in media. Some of the most popular games and software broke:

1. https://www.gamingonlinux.com/2025/02/the-glibc-2-41-update-...

2. https://www.phoronix.com/news/Glibc-WA-Steam-Exec-Stack

This is the attitude that will always prevent GNU/Linux from becoming prevalent for personal computing. There is a such a lack of empathy for users' hardships and it shows.

There are C codebases many decades old still being actively maintained and used. I don't think the same is true for Python on the same scale. It's easy to remodel when you are on the top of abstraction layer, but you don't want to mess around with the foundational infrastructure unnecessarily.

Another alternative is that the programmer write their own C compiler and be free of this politics. Maybe I am biased since I am working on exactly such a project, but I have been seeing more and more in-progress compiler implementations for C or C-like languages for the past couple years.

I wish FreePascal would allow declaring variables anywhere and loop local variables. I just can't program like C89 anymore and without these two basic quality-of-life features, Pascal simply feels stuck in history.

> Lua excepted, with conditions

Where can I read more about this? Is Lua's garbage collector tuned for real-time operations?

> The glibc people are so serious about backward and forward compatibility, you can in fact easily look up the last time they broke it

What? There was a huge breakage literally last year: https://sourceware.org/bugzilla/show_bug.cgi?id=32653

Glibc has been a source of breakage for proprietary software ever since I started using Linux. How many codebases had to add this line around 2014 (the year I brought my first laptop)?

    __asm__ (".symver memcpy, memcpy@GLIBC_2.2.5");