HN user

_kidlike

267 karma
Posts2
Comments113
View on HN

cholesterol is one of the most crucial molecules for survival. It's used to create and maintain cell membranes, and other critical functions. The vast majority is created by the liver, and there are a lot of regulating signals for how much, which is where usually things go off. Low cholesterol production is an extremely serious condition. The "only" problem with high cholesterol is that it builds up inside artery walls, which eventually may or may not dislodge and may or may not cause a heart attack or an embolic stroke. (I'm not a doctor. I just get medication for high cholesterol and have done some research)

this is not a new system... my father had it 20 years ago, sold for dirt cheap by the local stationary shop (not leather of course).

I've set up sunshine + moonlight on Fedora KDE Wayland, and I've played remotely from a different country with unnoticeable input lag (using a gamepad, playing Cyberpunk). The whole thing is even behind WireGuard.

I have very fast internet on both sides, both fiber to the home, with only the tablet running moonlight being on WiFi.

Mistral OCR 4 29 days ago

interesting... I have never seen such a benchmark before, where it forces the model to use a json schema for parsing a document. Sounds a bit counter intuitive to me, but I'm not that deep in the field. I usually just "ask" the model for information that is inside an image pdf. I haven't run any sophisticated benchmarks though...

Mistral OCR 4 29 days ago

I assume you mean for coding, for which I would agree. But for OCR Mistral is SOTA :)

But it's not "Claude" at fault here, it's "Claude Code" the CLI tool.

Claude Code is actually far from the best harness for Claude, ironically...

JetBrains' AI Assistant with Claude Agent is a much better harness for Claude.

interesting... for me JetBrains Mono won, which is the one I already use. But I discovered Atkinson Hyperlegible, which looks awesome for reading books. I guess I have a minor reading issue that I wasn't aware of!

Plasma has been a bit buggy since v6 :(

they tried to do something with remembering "how you left things" between sessions, and even when disabled things are still weird...

Also some power management related hooks are not working as well as before. Like if you put the computer to sleep at night, and wake it up in the morning, the automatic dark-to-light theme switch doesn't trigger. at least not always.

Still the best system to work with though!

I just used it here to approximately convey the scale.

the original function was full of mutable state (not required), full of special cases (not required), full of extra return statements (not required). Also had some private helper methods that were mocked in the tests (!!!).

All of this just for a "pure" function. Just immutable object in - immutable object out.

and yes, he was a junior.

I'm very surprised by these comments...

I regularly review code that is way more complicated that it should.

The last few days I was going back and forth on reviews on a function that had originally cyclomatic complexity of 23. Eventually I got it down to 8, but I had to call him into a pair programming session and show him how the complexity could be reduced.

putting aside accessibility, I believe that the usefulness of icons boils down to brain efficiency.

Considering that the brain has hard-wired neurons (since birth) to automatically count/recognize up to 3 objects, we need some icons as anchor points. With emphasis on some.

You can have max of 3 icons in a row, and a max distance of 6 items without icons.

Then you can VERY quickly find any menu item, by doing "+/-3 from X anchor" math, which your brain does extremely efficiently.

Further, this means that an action is represented by a relative path (e. g. save as = 1 down from the save icon). This further helps the brain to store these associations, because it's also extremely efficient at storing relative paths. So, long time users automatically become more and more efficient at using your software.

the two things are unrelated...

The pay-per-crawl thing, is about them thinking ahead about post-AI business/revenue models.

The way AI happened, it removed a big chunk of revenue from news companies, blogs, etc. Because lots of people go to AI instead of reaching the actual 3rd party website.

AI currently gets the content for free from the 3rd party websites, but they have revenue from their users.

So Cloudflare is proposing that AI companies should be paying for their crawling. Cloudflare's solution would give the lost revenue back where it belongs, just through a different mechanism.

The ugly side of the story is that this was already an existing solution, and open source, called L402.org.

Cloudflare wants to be the first to take a piece of the pie, but also instead of using the open source version, they forked it internally and published it as their own service, which is cloudflare specific.

To be completely fair, the l402 requires you to solve the payment mechanism itself, which for Cloudflare is easy because they already deal with payments.