HN user

odo1242

1,025 karma
Posts17
Comments434
View on HN

Looks good overall. My main complaint is that the animations don't all seem to go together - the "Jelly" style of the toggle switch or button (which has squish animations that respond to pointer location) is WAY different from the "Jelly" style of the checkbox (which just resizes), for example.

Also, some Jelly buttons animate correctly when you move your mouse over them mid-click, while some remain stuck in the original position when you clicked them.

The article in the comment I was replying to wasn't talking about age verification laws, they were talking about "parents protecting kids", a.k.a. content filtering.

As for the other part, I'd just assume that they wanted to switch to a registrar more used to adult content websites and less likely to be impacted by the Texas govt. Just like pirate sites switch TLDs to the ccTLD of the country least likely to prosecute them all the time.

I was mostly just talking about the fact that registering a domain with a registrar that is about "XXX sites should help empower parents to keep their kids away from adult content" isn't necessarily a bad thing.

The language also does not support goroutines, locks, or channels, except through using the C threading libraries.

(I think the original author meant type safety when they made that statement. Though it still doesn't make all that much sense to me)

The answer is apparently "you don't":

- Everything in the language is statically allocated or stack-allocated. You have to call a malloc / free function to get heap allocated things

- The language is not memory safe (you can't return slices, pointers, or interface types from a function if the thing was created inside the function, unless you used heap allocation)

- Interfaces (the only variable size struct Go has) are implemented by creating a struct of function pointers. Arrays and maps (the non-struct variable size types) are implemented as stack-only and maps are limited to 1024 keys. You can opt into heap-based arrays / maps in the standard library to bypass this.

This is similar to my experience with (8-bit quantized, non-MOE, 26b) Qwen locally on my computer. It’s really good for small tasks, but the first time I tried to do a major task with it it straight up forgot what agent harness it was in and started using the wrong format for tool calls lol

(If you’re curious, it was running in Pi, but somehow convinced itself it was running in Claude instead and started trying to call Claude tools that didn’t exist)

I did not know this actually; I guess the more accurate statement is that Apple just didn't write emulation code for 32-bit apps for them

One of the big things here is that Intel and ARM processors are backwards-compatible with 32-bit instructions, even if they are 64-bit processors. Apple Silicon on the other hand is not, which is why Apple completely dropped support before switching.

It depends a lot on the hackathon/what the judges are looking for. A few are run by technical people who pick the coolest technical architectures, a few are run by casual users who pick the best looking result.

The majority of the ones I’ve been in have tended to be run by people who judge based on their notion of how useful the app will be societally, with the tie breaking factor being the UI/architectural design.

Socialism is public ownership of the means of production. If there isn’t a way for regular people / “the proletariat” to influence the government, it’s not socialism because an autocratic government isn’t “the public”

I don’t think Anubis proves the idea much though. I feel the main reason it’s worked is that AI companies haven’t yet tried to bypass it.

And AI companies still scrape Anubis protected websites, it just forces them to not DDOS the website

Honestly, a lot of devices that use cloud apps for things could be improved both for the customer and manufacturer by using a "STUN/TURN" style proxy for the cloud service rather than forcing all data to go through a cloud service (to add to the other advantages, you don't need as many developers on the cloud side). But nobody in the engineering departments of these companies seem to be willing to touch WebRTC with a nine-foot pole lol