It's a shame there's no alternative to Meli. I'm shopping around for a macbook and I would much rather have a marketplace with verified identities and profiles than the shady whatsapp groups and contacts I'm finding.

People have cheaper phones here, so devs are naturally more exposed to low end hardware.

It's been awesome for me! I have a fairphone 4 which isn't top of the line at all anymore but the apps work MUCH better here on average than when I was in the US. Websites also load quicker too for similar reasons.

I'm making something like Paseo and hax is very interesting as a Pi replacement.

[1] https://fx.sh/docs/using-fx/acp

[2] https://pi.dev/docs/latest/rpc

When doing the last streaming of the wal from the primary the article mentions that the nodes will catch up to replication time `T`.

How do the nodes coordinate this time `T`? Is it simply just choosing a time in the future (after the backup has started) and waiting till they all catch up or is there more realtime coordination happening?

Also, in another part it's mentioned that "Time T is saved to ensure we know the precise time, down to the second, included in this backup." My question is that if 1 second is granular enough? I'm assuming that this is a simplification for the sake of explanation and Time T is a timestamp with at least millisecond granularity. I regularly play with otel data that can have nano-second granularity so I'm assuming is millisecond or more

On the model. Really cool that it can act every 70ms. That's more than 10x faster than TTFT in most inference APIs. It HAS to be a local model. No idea which family or which one it is or what hardware it runs in. These would be nice details to tease!

A refreshingly pragmatic take on the bounds of usefulness on type system features vs their complexity.

Comments URL: https://news.ycombinator.com/item?id=49097974

Points: 5

# Comments: 1

It's not practical to use it though. It counts almost 8x more towards your quota than glm 5.2!

https://opencode.ai/docs/go/#usage-limits

Not the best security practice but thought you should know!

There's no newer upstream changes to merge with the fork

I've been using windows for the past 5 years or so. I was using Linux before that. I used to complain about things breaking in Linux but the situation in Windows is way worse than it ever was in Linux. A couple of days ago my co-worker turned on his computer and windows has locked him out somehow. He had to disable secure boot, recover his bitlocker passphrase from his microsoft account, and only then could he get past the boot screen. The theory is that his laptop turned off while updating. I'm thinking, why doesn't the update abort when it realizes it's not plugged in or on low battery. He said it had never happened to him before and I have also never seen it.

The other side I notice is with google products. Barring android, GCP, and the less than yearly occassional outage, I would never see a bug in google products. Now I notice them often in drive, sheets, gmail, and specially meet. The other day I joined a meeting and all participants couldn't log in. NEVER have I seen such a bad production bug from google.

Profits over wonderful products I guess

Lots of frontend devs (and vibe coders) just want a "deploy my code" service.

Implementing, running, maintaining, scaling a module registry is probably not worth the time. Unless there's a clear technical requirement from the runtime. I would think there isn't since npm protocol compatibility is a stated goal/feature.

Just to give an example, I ingest otel trace spans individually and in a materialized view calculate the total duration of the whole trace among other things.

https://www.supremecourt.gov/opinions/25pdf/25-112_0am4.pdf

"Modern cell phones, we observed a dozen years ago, are “such a pervasive and insistent part of daily life that the proverbial visitor from Mars might conclude they were an important feature of human anatomy.” Riley v. California, 573 U. S. 373, 385 (2014). Since then, the percentage of Americans who own smartphones has only increased. To- day, more than nine in ten Americans own a smartphone. See W. Bishop, Pew Research Center, Mobile Fact Sheet (Nov. 20, 2025) (91%); compare A. Smith, Pew Research Center, Smartphone Ownership—2013 Update (June 5, 2013) (56%)."