Hacker Newsnew | past | comments | ask | show | jobs | submit | jsolson's commentslogin

Columbo is anything but a failure, though, and the audience knows that. His genius is leveraging humility to convince killers that he's a bumbling idiot, while in reality he's onto them from the first encounter.

_Slow Horses_ came up in another thread. I'd argue that Columbo has more in common with Jackson Lamb than with Charlie Brown.


There's similarities between Columbo and Slow Horses. Lamb is similarly dishevelled, but is the polar opposite of Columbo's charm.

It's so far from comedy that I couldn't make it through the series. When it comes up in conversation, I tend to describe it as "grief porn."

Yes, highly recommend Reynolds, generally, although the third Rev Space book takes some fortitude to get through.

I realize this isn't the meat of your post, but you ate a lobster sandwich at Walmart?

I cannot help but think of https://youtu.be/Pj-D0jc17D0?si=BiEGWr9aacGdAkGW


The walmart experience is so wildly different depending on who they're catering to.

When I lived in poor areas, I've literally been shaken down by gigantic bouncers in the parking lot for "stealing" (but not) a bag of $5 cat litter. Why on earth this is even worth the liability of sending bouncers is beyond me. And everything even remotely valuable and easy to steal is behind locked showcases, but no one gives a fuck to get it out to help you buy it.

In rich areas, it's lobster sandwiches and no one even bothering you for your receipt on the way out, and maybe someone might even help you find something in the store. Nothing you want is behind glass, except maybe something unusually valuable by walmart standards and miniscule like an SD card.


yeah it was pretty central walmart in new rochelle. it looked like a high end store in europe.


“Gas Station Sushi: Fresh one day a week, but no one knows which one…”

I read the post as involving seeing the other family at Walmart, but the buying of things not needed and consumption of lobster as happening elsewhere.


nah it was walmart. just a fancy one


You might have even better precision if you stay away from CPU0 and also set idle=poll in your kernel command line. Lots of things (including other interrupts) often land on CPU0. It would not be my first choice for something where I wanted high timing precision.


I came here to post this. We make a lot of the same sorts of optimizations for our OS distro (debian based) -- disabling frequency scaling, core pinning, etc. Critically, CPU0 has a bunch of stuff you cannot push, and you're better off with using one of the other cores as an isolated island.

This is what the scheduler latency looks like on our isolated core:

# Total: 000300000 # Min Latencies: 00001 # Avg Latencies: 00005 # Max Latencies: 00059 # Histogram Overflows: 00000

(those are uS!)


Very cool. What are you running on it? What's your use case?


Worth a shot! I'll give it a go later today.




I'd say certain countries in Europe give us a run for our money: https://caw.ceu.edu/other-activities/academic-blog/politics/...


This is completely different.

The is the politicians not being able to form a coalition. Imagine your congress not agreeing to fill some commissions or confirm some positions in government.

It is a 'shutdown' of the legislative branch, not the executive.


In the US, the legislative branch controls the budget, so when their budget expires, if the legislative branch is shutdown, so is the money.


Not really comparable because the bureaucratic system kept running. It's just a completely different political system and "there is no government" means a different thing. US-style "government shutdowns" don't really happen in Belgium.


I agree with nearly everything except your point (1).

Periodic polling is awkward on both sides: you add arbitrary latency _and_ increase database load proportional to the number of interested clients.

Events, and ideally coalesced events, serve the same purpose as interrupts in a uniprocess (versus distributed) system, even if you don't want a proper queue. This at least lets you know _when_ to poll and lets you set and adjust policy on when / how much your software should give a shit at any given time.


From a database load perspective, Postgres can get you pretty far. The reads triggered by each poll should be trivial index-only scans served right out of RAM. Even a modest Postgres instance should be able to handle thousands per second.

The limiting factor for most workloads will probably be the number of connections, and the read/write mix. When you get into hundreds or thousands of pollers and writing many things to the queue per second Postgres is going to lose its luster for sure.

But in my experience with small/medium companies, a lot of workloads fit very very comfortably into what Postgres can handle easily.


+1 on connections being the limiting factor. Curious how further a connection pooler can get you


That would make sense.

My first thought was "Arc'teryx will probably adopt this immediately." They (and similar brands) are already pushing as hard as they can on seamlessness or very very tight seams.


Doesn't Arc'teryx make outdoor gear? That's something where I absolutely would not buy a product that I couldn't repair in the field with a needle and thread.


Yes, Arcteryx makes outdoor gear, but more along the line of technical climbing and backcountry skiing, not backpacking. Not likely to carry a needle and thread to repair your 3L Goretex shell.

Of course the brand has been diluted to cater to a more mainstream buyer.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: