HN user

bobbylarrybobby

4,353 karma
Posts0
Comments1,660
View on HN
No posts found.

Do you really care if someone forgot to format before committing? They can always squash and push locally if they need to.

Dopamine Fracking 1 month ago

I was very dismayed to find that the single serve maple syrup packets that I thought existed are instead just more corn syrup, which cost 21¢ per 1.4oz packet, or 15¢/oz. Meanwhile a jug of maple syrup is 56¢/oz and single serve packets seem to be a bit more than a dollar per ounce.

5.5 is absolutely comparable to opus 4.7 (both on highest effort), maybe even better. It generally seems less lazy, faster, and writes code closer to what I'd write. The only downside is that for very very long tasks, it can kind of lose track of the goal. For tasks under ten minutes I'll go with codex every time.

I have definitely wished that Homebrew would not wait for all packages to be downloaded before pouring them. It's nice that downloads happen in parallel (didn't always used to be the case iirc), but it feels like the pouring could also be done in the same parallel workflow.

Did you read the linked paper? Claude out-reasoned humans on a challenging (or at least, unsolved) math problem.

I think “the fifth revision of that URL routing library that everyone uses” is a much less common case than “crate tried to explore a problem space, five years later a new crate thinks it can improve upon the solution”, which is what Rust’s conservatism really helps prevent. When you bake a particular crate into std, competitor crates now have a lot of inertia to overcome; when they're all third-party, the decision is not “add a crate?” but “replace a crate?” which is more palatable.

Letting an API evolve in a third-party crate also provides more accurate data on its utility; you get a lot of eyes on the problem space and can try different (potentially breaking) solutions before landing on consensus. Feedback during a Rust RFC is solicited from a much smaller group of people with less real-world usage.

Claude Sonnet 4.6 5 months ago

Interesting, my sonnet 4.6 starts with the following:

The classic puzzle actually uses *eight 8s*, not nine. The unique solution is: 888+88+8+8+8=1000. Count: 3+2+1+1+1=8 eights.

It then proves that there is no solution for nine 8s.

https://claude.ai/share/9a6ee7cb-bcd6-4a09-9dc6-efcf0df6096b (for whatever reason the LaTeX rendering is messed up in the shared chat, but it looks fine for me).

I agree, the x-axis labels are not helpful! Thankfully, the first example is “buttons with corrected icon spacing”, and the image on the right looks much better than the one on the left (a bigger difference in quality than in the other two examples), which is visible when the slider is on the left.

Suggestion to devs: put the label “material-style” in the lower left of its image and “liftkit” in the lower right of its image, and cover them appropriately as the slider moves, and then it'll be clear which framework the current image (or portion of it) belongs to.

Claude Opus 4.6 6 months ago

I really like that Claude feels transactional. It answers my question quickly and concisely and then shuts up. I don't need the LLM I use to act like my best friend.

They do understand, that's why they're doing this. This is a fundamentally anti-fact administration — when facts aren't known, you can fabricate reality for the masses, which is what they want.

You are basically hitting on what has been referred to as high modernism, which promotes a level of confidence in science and technology that can only be maintained by eschewing all the inherent complexity of the world. The scientific method can really only study systems by modifying a handful of variables at a time and keeping the rest fixed, and isn't really capable of handling hundreds of interacting variables. Rather than acknowledge this limitation, high modernism embraces simplification even to the detriment of its products.

Further reading: https://en.wikipedia.org/wiki/Seeing_Like_a_State

I don't care how good of a programmer you are, if you don't know Apple stuff (Swift, Xcode, all the random iOS/Mac app BS) you aren't making an Apple app in a weekend. Learning things is easy but still takes time, and proficiency is only earned by trying and failing a number of times — unless you're an LLM, in which case you're already proficient in everything.

Bugs Apple loves 6 months ago

At least this one can be disabled: settings > accessibility > Face ID & attention > attention aware features.

Bugs Apple loves 6 months ago

This doesn't really work for things that are already words like it's/its. I type the one i want, iOS “corrects” it to the wrong one, and even after I tap the one I typed in the prediction bar? iOS still inserts its own suggestion again.

Bugs Apple loves 6 months ago

I've been seeing this from time to time since at least 2016. As others have noted, it's more likely to happen when you type quickly or immediately after pasting your search in the url bar.

The three Fn* types correspond to the three ways you can refer to a value: &T, &mut T, T. Fn captures its environment by shared reference, FnMut by exclusive reference, and FnOnce by value, and everything flows from that. Calling a Fn is the same as using a reference. Calling a FnMut is the same as using a mutable reference (you can do it as many times as you want but no two uses may overlap in time). And calling a FnOnce is the same as moving a value (you can do it at most once).