HN user

maleldil

1,646 karma
Posts1
Comments1,017
View on HN

The solution to this is editions/epochs, like Rust. You can set your project to the 2025 edition and be sure that, even if future versions introduce breaking changes, they will not affect your project; it will continue to compile as before.

I imagine it could, eventually, if not now. The Bun translation used Anthropic's best model, cost hundreds of thousands of dollars, and still contained a large number of unsafe blocks. Maybe if they left the agent running for longer, using Miri for verification?

translate it to Rust catching all the memory bugs in the process

That's not possible. If it were, you'd just fix the memory bugs directly in the original language.

Your best bet is to have a translation littered with unsafe blocks, so you still have to do the work of nailing down the specifics to make them safe. There's no magic "unsafe language" -> "safe Rust" pipeline, even with GenAI.

Why would you need that? 99% of the time, you'll just grab the BibTeX from where you're getting the paper (Google Scholar, arXiv, ResearchGate, etc.) and paste it on the .bib file. LaTeX will take care of formatting it when you \cite.

What do you mean by "implementation names"? I assumed you meant changing the "implements X", which should be easy for an LSP.

Saying people enjoy exercise is only slightly more controversial than saying "ice cream tastes good".

You might be in a bubble. I know many people who exercise regularly, and I'd say most of them only do it because it's healthy. If they found a way to stay healthy without exercise, they'd drop it in a heartbeat.

Nah, even as a leftist, The Economist is mostly in the "enlightened centrist" area. I'd say they're a reliable source of facts as long as you know where their bias is.

If you live within walking distance of a good shop, you likely would make more trips instead of buying in bulk once a week.

ACL conference papers usually cap the main body at 8 pages, with unlimited appendices. KDD has a hard limit of 9 pages plus 3 for references and appendices.

Claude Science 21 days ago

CS conference papers often have page limits (e.g. ACL ARR is 8 pages double-column), so most paper main bodies are exactly that, as it's seen as sloppy if you don't use the full count. I've had someone point out that it's best to use the entire page 8 without leaving any gaps.

There are also appendices, which reviewers aren't required to read. If there's something relevant that doesn't fit in the main body and you don't put it in the appendix, reviewers will point it out and ask for it, and it will influence their grades.

In the end, publishing papers these days is about convincing reviewers rather than actually writing a good paper. And you usually have reviewers asking for all sorts of things.

Aside from repairability, the MacBooks are the best laptops in every other respect: battery life, keyboards, screens, performance (especially performance per watt) and overall build quality. They're even competitively priced in the current market. Watches have some of the best sensors in their category. iPhones have the best performance and cameras. I can't say much about the AirPods since I've never used them, but people I know report they work very well.