beautiful demo - is it running fully locally or talking to 3rd party API’s? That box was jaw dropping small
HN user
AnthOlei
What do you have going on the hardware side? I want to plug this into hass but don’t know what hardware I need for reasonable latency
I switched my parents onto Linux a couple months ago, after my mom kept getting confused between edge and chrome - not being to uninstall edge was the last straw, but the massive amount of adware slowing down her capable-but-old laptop was a close second.
So far so good! Some smaller hiccups, like chrome won’t use dolphin, but I installed rustdesk so I can help them through whatever.
Over Christmas the in-laws were asking about Linux because of windows issues, which was surprising since they’re technologically literate but in a layman sense. I didn’t try to switch them over since the parent experiment is still ongoing but a couple more months of seamless use and I’ll consider it a success.
All this to say I’m very glad for Microsoft leadership!
Does anyone else think this method of discourse incredibly rude? This poster posted a quasi researched comment that looks surface credible. A HN user took the time to respond to each point - only for the response to the response to be “whoops sorry, wasted your time!”
Feels like a breach of social contract. I used to see help requests that were well written as a signal of effort - as in “I’ll put in the effort to help since they did”
I also asked claude to roast it for fun. this one made me lol:
The use case is Chef's Kiss levels of overengineering. They want to avoid Git commits... so they built a custom S3 server... that runs in a container... that gets rebuilt on every NixOS rebuild... to serve static files... to FluxCD. At some point, just make the damn Git commits.
The nix file is besides the point - it gives you a totally hermetic build environment. Not OP, but it’s the only way I know how to get gcc to use a static glibc. All you should pay attention to is that it’s using a static glibc.
$out is a magic variable in nix that means the output of the derivation - the directory that nix moves to its final destination
They’ve now removed your second example from the testing set - I bet they won’t regenerate their benchmarks without this test.
Good sleuthing, seems someone from OpenAI read your comment and found it embarrassing as well!
Oh my this is awful - could you post a source?
I’ve recently spent time truly learning git, and I’m realizing how much better it is to take care of your commits in a PR even if you squash to main.
My reviewers love when I write “review commit by commit” in the PR description. Then each individual commit has its own reasoning, and you can mentally switch into reviewing if that commit does it’s one thing it’s supposed to do correctly. I will accept the argument that each commit should be its own PR though :)
I was under the impression that you were referring to a specific event that happened over the weekend, not a general vibe you were feeling
What’s the source of this? Where can I read more?
Ha, I think this site is styled by a single-sheet CSS called Tufte.css
Oh wow. I went though some of the perl book you linked and I was noticing the examples were really familiar; I then realized you were the same guy who wrote the awk book I have been going though.
Your work is excellent! Thank you, I’ll buy a copy soon.
this is amazing! I guess I was searing the wrong keywords. Thanks, I’ll evaluate these.
I wonder: if we set a TTL on the image, and also make it require a signed link that gets copied the same way, is it now a secure & ephemeral service?
Gerrit for really fine grained control
How have meta employees stolen money?
If you're experienced using nix, this article may be too simple - but hopefully this is helpful for people struggling to figure out some nix features.
For those of you who have a modern serverless architecture (lambda, dynamo, firebase etc.), how do the costs compare there? I’ve always thought serverless is cheaper, but I’ve never ran anything at scale.
I read your write up, but I’m not entirely clear on one part: how do cloudflare workers handle websocket connections? Are they automatically terminated after the worker spends too much time active? If so, doesn’t handling the WS handshake have a lot more overhead than a fetch call? Maybe I’m misunderstanding something here. One of my biggest issues with serverless is its inability to handle websockets in a sane way, so this would be huge.