Hacker News: jstrong

New comment by jstrong in "C# strings silently kill your SQL Server indexes in Dapper"

jstrong — Sat, 07 Mar 2026 06:56:15 +0000

optimizer can't inspect the value? pretty dumb optimizer, then.

New comment by jstrong in "A distributed queue in a single JSON file on object storage"

jstrong — Tue, 24 Feb 2026 12:03:15 +0000

that's A choice.

New comment by jstrong in "Micropayments as a reality check for news sites"

jstrong — Fri, 20 Feb 2026 05:42:39 +0000

I feel like the less tolerance I have for ads (as time goes on), the more desperate they get in trying increasingly aggressive ways of making you watch ads. I'm never watching ads again, ever! I'm willing to pay, but not with my time for your terrible, horrendous, bullshit ads!

New comment by jstrong in "Micropayments as a reality check for news sites"

jstrong — Fri, 20 Feb 2026 05:37:45 +0000

I don't know, man, glossy magazine ads were glamorous. sure there was stupid stuff, but the comparison between the "one weird trick" era and magazine ads of someone looking cool so you have a positive impression with some brand name is pretty stark.

New comment by jstrong in "Company as Code"

jstrong — Fri, 06 Feb 2026 00:39:16 +0000

man, I can't wait to wrangle a giant YAML file to be able to take a sick day!

New comment by jstrong in "Postgres Postmaster does not scale"

jstrong — Thu, 05 Feb 2026 23:55:28 +0000

redis is single-threaded but handles lots of connections (i.e. > 500) with much better performance vs. postgres. there's zero chance someone building postgres in 2025 would do one process per connection, I don't think there's any argument that it's a good design for performance. it's just a long-ago design choice that would be difficult to change now.

New comment by jstrong in "Postgres Postmaster does not scale"

jstrong — Thu, 05 Feb 2026 07:59:02 +0000

From the article:

> The real bottleneck is the single-threaded main loop in the postmaster.

A single-threaded event loop can do a lot of stuff. Certainly handle 4000 tasks of some sort in under 10s. Just offhand it seems like it would be eminently possible to handle incoming connections on the scale they describe in a single-threaded event loop.

Clearly the existing postgres postmaster thread is a bottleneck as it is implemented today. But I'd be interested to go deeper into what it's doing that causes it to be unable to keep up with a fairly low workload vs. what is possible to do on a single thread/core.

New comment by jstrong in "Postgres Postmaster does not scale"

jstrong — Thu, 05 Feb 2026 07:52:38 +0000

can't believe postgres still uses a process-per-connection model that leads to endless problems like this one.

New comment by jstrong in "Google flags Immich sites as dangerous"

jstrong — Thu, 23 Oct 2025 01:14:39 +0000

google: we make going to the DMV look delightful by comparison!

New comment by jstrong in "Ripgrep 15.0"

jstrong — Sat, 18 Oct 2025 17:27:58 +0000

ripgrep is one of the main reasons I got interested in rust. it worked so well, it piqued my interest that it was written in rust. many years later, very glad about that. been using `rg` daily since then as well!

New comment by jstrong in "We already live in social credit, we just don't call it that"

jstrong — Tue, 02 Sep 2025 21:36:30 +0000

... some stuff we have kinda resembles china's social credit score if you really think about it ...

ok, maybe

... so yeah, it's totally fine lets do it ...

WHAT

New comment by jstrong in "No Moar Cookies"

jstrong — Mon, 28 Jul 2025 15:59:01 +0000

imagine some people started using hammers as weapons, leading to some gruesome murders vividly depicted by the news. as a result, construction companies started advertising that this house was built without the use of ANY hammers. that's how I feel about cookies.

cookies are not the problem. spyware is the problem. the way cookies work is, the server includes a "SET-COOKIE" header in its response. it is literally a request, which has no power, other than your computer deciding to store the data locally and include the cookie as a header in its subsequent requests.

somehow instead of us collectively relying on our own user agents to not comply with requests from remote servers that are not in our interest, we settled on deciding the cookie itself is a dangerous mechanism, which is stupid.

New comment by jstrong in "Why Does My eBPF Program Work on One Kernel but Fail on Another?"

jstrong — Wed, 23 Apr 2025 17:29:51 +0000

wow that sounds like a PITA to deal with

New comment by jstrong in "Embedding Python in Rust (For Tests)"

jstrong — Wed, 22 Jan 2025 14:41:58 +0000

was expecting to see examples of python tests you would use, presumably for testing the rust code? like, how would writing the tests in python be easier?

New comment by jstrong in "100x defect tolerance: How we solved the yield problem"

jstrong — Fri, 17 Jan 2025 18:37:51 +0000

a man can dream

New comment by jstrong in "100x defect tolerance: How we solved the yield problem"

jstrong — Thu, 16 Jan 2025 17:36:27 +0000

I would like a workstation with 900k cores. lmk when these things are on ebay.

New comment by jstrong in "Designing Code for Forward Progress"

jstrong — Fri, 10 Jan 2025 07:13:35 +0000

man, the python examples in there .. I am always low-grade irked by those! until now I wouldn't have been able to describe the problem. great piece.

New comment by jstrong in "What Parler Saw During the Attack on the Capitol"

jstrong — Mon, 06 Jan 2025 23:10:11 +0000

https://a57.foxnews.com/static.foxnews.com/foxnews.com/conte...

New comment by jstrong in "I Followed the Official AWS Amplify Guide and Was Charged $1,100"

jstrong — Thu, 14 Nov 2024 08:13:16 +0000

unrelated rant, but I'm still salty about it.

needed to send "raw" http requests instead of using their bloated sdk for reasons, and requests failed with "content-type: application/json" header, but succeeded with "content-type: application/x-amz-json-1.0". get out of here with that nonsense.

New comment by jstrong in "Building a highly-available web service without a database"

jstrong — Sat, 10 Aug 2024 21:05:36 +0000

like you I'm more open to the idea of keeping data in memory than most of the responders here. when I got to the part of the article about how they are using common lisp with hot reloading, I was thinking, well you guys can do whatever you want, but not everybody is working on that team, ha.