Japan can now pull most of the lithium out of dead EV batteries, but commenters say the article oversells it.
What the article says
- Japanese engineers found a way to recover most of the lithium in used EV batteries, swapping in recovered lithium hydroxide instead of the usual sodium hydroxide.
- That change also cuts carbon emissions from recycling by close to half compared to older methods.
- Japan imports nearly all its battery minerals, so recycling at scale could ease that dependence.
- Right now only a small fraction of used batteries actually enter recycling, so collection is the real bottleneck.
- The team wants to scale up production by 2027 and hit large annual recovery volumes by 2035.
What HN is saying
- Commenters note lithium recovery from batteries is easier than mining it fresh, since batteries are already high purity, so this result is expected rather than shocking.
- Several people call out the article itself as poorly written and possibly AI generated, and ask for the original source instead.
- A recurring pushback is that lithium is only part of the value in a battery. Nickel, cobalt, copper and graphite matter just as much, and one commenter points to Redwood Materials already recovering most of all those materials, not just lithium.
- The bigger disagreement is about what actually matters. Several argue the real constraint is cost and energy use at industrial scale, not the recovery percentage itself.
- A side thread debates why Japan lags on EV adoption despite being well suited for it, with automaker caution and infrastructure choices cited as reasons.
Git quietly shipped a command that fixes commits and auto-rebases every branch that depends on them.
What the article says
- Git added a new history command with three subcommands: fixup, reword, and split.
- Fixup folds a staged change into an old commit and automatically rebases every local branch built on top of it, further than the existing update-refs option goes.
- Reword lets you edit an old commit message and rebuild the stack on top, without touching your working files.
- Split breaks one commit into two by picking which changes belong where, like a friendlier version of interactive rebase.
- It refuses to run if a rebase would hit a conflict, so it can never leave your repo half broken, unlike jj it does not yet let you carry conflicts through the rewrite.
What HN is saying
- Commenters mostly like the new commands as a lower friction alternative to interactive rebase, without needing to adopt jj.
- The sharpest fight is over whether commit history curation even matters. One commenter says nobody reads individual commits, others push back hard, arguing clean commits matter for code review, bisecting bugs, and understanding why code looks the way it does.
- One user found a real gap. Rewriting a commit with git history strips GPG signatures, which sends them back to plain rebase.
- A few people still prefer full interactive rebase or the older stgit tool for managing large stacks of changes.
- Someone asks whether the split command could eventually split an entire branch, not just one commit.
One developer ships Mac and iOS apps entirely from the terminal, letting Claude Code run the whole Xcode pipeline.
What the article says
- Xcode has to be installed, but you never need to open it. The build tools it contains work fine from a plain terminal.
- A short list of one time setup steps needs the graphical app, like signing into your developer account and creating signing certificates. After that everything is scriptable.
- The core piece is a single release script that archives, signs, notarizes, and installs the app, written once with help from an AI coding assistant.
- A short instructions file tells the assistant the project's conventions, so it can repeat the same release process for future apps without being walked through it again.
- The secrets involved, like signing keys and passwords, stay in the system keychain rather than the code repository.
What HN is saying
- Commenters split sharply on running coding agents with full access to a real machine. Several worry about a recent case where an AI tool uploaded someone's home folder including private keys, and argue for sandboxes or separate user accounts instead.
- Some pointed out lightweight ways to sandbox agents anyway, using free virtualization tools built into modern Macs, or running the agent in a container with limited permissions.
- A recurring joke was that a post about avoiding Xcode was written with heavy AI help and kept telling readers to just ask their AI for help too.
- One experienced developer pushed back hard, arguing the official Xcode tooling actually works better for many tasks now and that skipping it is bad advice.
- Others suggested alternatives entirely, like building with React Native, Expo, or Linux based toolchains that avoid Xcode from the start.
Apple quietly built a speech engine that beats Whisper, and a developer actually ran the numbers to prove it.
What the article says
- A transcription app maker benchmarked Apple's new on-device speech engine against Whisper and Apple's old engine using a standard speech dataset.
- The new engine beat every Whisper model they tested, including the largest one, while running about three times faster.
- It also crushed Apple's old speech engine, cutting mistakes by roughly three to four times.
- Whisper still wins on covering far more languages, since Apple's engine only handles English well for now.
- The team published their raw transcripts and methodology so others can check the results themselves, and even found a bug in their own app while testing.
What HN is saying
- Commenters mostly agreed the improvement is real, but pushed back on the choice of Whisper as the benchmark, since newer open models from Nvidia and others now lead on quality.
- Several people praised Apple's new engine for streaming results as you talk, instead of making you wait for a finished recording like most competitors.
- A recurring complaint was that Apple still can't auto detect which language you're speaking, forcing you to pick one manually before dictating.
- Multiple users pointed to third party apps already built on top of local speech models as proof that on-device transcription is basically solved for personal use.
- One thread debated how to even talk about accuracy gains, since a small percentage of errors dropping to almost none matters more than the raw multiplier suggests.
An 1830s Englishwoman sketched India with a curiosity photography never quite managed to replace.
What the article says
- Emily Eden traveled across northern India in the 1830s while her brother served as governor general, and she filled her time sketching everyone she met.
- She drew princes and generals but also servants, travelers, hill communities and even the animals along the way, which made her work unusually broad for the time.
- Her sketches captured the court of Maharaja Ranjit Singh near the end of his reign, a moment of real political change in Punjab.
- A new exhibition in Delhi gathers the full set of lithographs made from her original drawings.
- She was a sharp, funny writer too, though she also saw colonial rule as a civilizing mission, a view the piece doesn't shy away from.
What HN is saying
- Commenters pointed to further reading, including the Empire Podcast's episode touching on Eden and William Dalrymple's books on the period.
- One reply linked her Wikipedia page and a 1844 book of her lithographs, plus an archive.org scan of the originals.
- Someone drew a parallel to Frederick Catherwood, who was sketching Mesoamerican ruins around the same era.
- The thread's sharpest turn came when a comment about modern Indian pollution set off a long, heated argument over how much colonialism, partition, and centuries of earlier conquest explain India's present state.
- No single explanation won out. Replies ranged from blaming extractive colonial policy to noting many Western cities were just as polluted a few decades ago.
Scientists made a metal twice as strong as steel just by changing how it cools, not what it's made of.
What the article says
- Researchers mixed five metals, including hafnium and tantalum, then cooled the blend slowly instead of the usual fast quench.
- That slow bake let the atoms settle into small, tightly packed, defect free grains rather than a messy structure.
- The result held up far better under stress than the same alloy made the normal way, while staying bendable instead of brittle.
- The bigger claim is that how atoms arrange themselves during manufacturing matters as much as which elements you use, a shift from a century of alloy design focused mainly on composition.
- It is still early stage. The team wants to understand why the atoms self organize this way before the method can be widely applied.
What HN is saying
- Commenters were skeptical of the headline comparisons, pointing out the article never says whether the new alloy is easier to weld, machine, or resist corrosion, just that it is strong.
- One reader flagged that comparing a new five metal alloy to plain steel is comparing different materials, not just different methods, which muddies the actual result.
- Several people linked the original Science paper and noted superalloy is already a defined term for a different family of materials, so the headline is misleading.
- A materials scientist explained the mechanism in more detail: the metals self assemble into nanoscale crystal structures because of size mismatches between the elements.
- Someone pointed out the exotic ingredients, tantalum, niobium, and hafnium, are expensive, so this will likely stay a niche material rather than a steel replacement.
California may outlaw infinite scroll and other addictive app design for teens
What the article says
- The article text wasn't available, so this is pieced together from the headline and comments.
- California is weighing a law against psychologically addictive app design, including infinite scroll.
- It would target users under sixteen, which likely means some form of age verification.
- Supporters frame it as protecting teens from apps engineered to be hard to put down.
What HN is saying
- Most people agree infinite scroll is genuinely bad design that swallows footers and permanent links.
- The sharpest fight is whether addictive design can be legally defined without sweeping in ordinary good UX.
- Several would rather platforms be forced to offer a chronological feed option than ban a specific pattern.
- Some doubt age verification is worth the privacy cost, and a few argue the real fix is banning targeted ads outright.
How a cheap Sega CD add-on faked jaw-dropping 3D video using tricks that squeezed it into almost no bandwidth
What the article says
- Sega's CD add-on for the Genesis had a slow chip and almost no bandwidth, yet the game Silpheed made video that looked like live 3D rendering.
- The developers built up from the hardware's limits rather than cramming a movie into it, using flat shaded polygons and a tiny color palette that still looked great.
- Their big trick exploited the console's tile based screen. Many tiles in a frame were solid colors, so they stored each one once and reused it across the whole image.
- A rarely used graphics feature meant for rendering text let them cheaply expand two color tiles too, squeezing out even more space.
- The author wrote the whole piece using an AI coding framework instead of coding it himself, and plans to open source that workflow soon.
What HN is saying
- Longtime fans agree the presentation held up better than the gameplay itself, several singling out the soundtrack as still worth hearing today.
- One commenter spotted that the story looked auto resubmitted from an old RSS feed, and the author himself showed up to say he was just fixing a typo.
- A deep side thread corrected how audio actually gets mixed between the Genesis and the CD add on, with several people adding hardware details.
- The author's note about using an AI framework to research this sparked debate, some calling it a huge boost for prototyping, others worried it kills the joy of a side project.
A tool turns a shared Dropbox folder into a way for non-coders to share AI skills, and HN immediately argues about it.
What the article says
- A new app called sx lets teams share AI skills, the reusable prompts and instructions that power tools like Claude and Codex, without touching git or a terminal.
- You just point the app at a shared Dropbox, Google Drive, or iCloud folder and drag skills in as plain text files.
- The app auto translates each skill into the right format for whichever AI tool a teammate uses, and keeps version history alongside the files.
- It adds an extension system that can flag duplicate or stale skills, show who is actually using them, and schedule reviews.
- The maker built the original CLI version for developers, then realized marketing, legal, and sales teams wanted skills too but had no interest in learning git.
What HN is saying
- Several commenters are wary of using Dropbox for something that needs real version control, worried teams will end up with drifting, untracked copies of the same skill.
- Others say they already run a similar setup with a shared synced folder and it works fine, as long as people don't overwrite each other's files without asking.
- A recurring question is why not just use a private GitHub repo, since one shared skill could teach any team to sync there in minutes.
- The author pushes back that non-technical teams genuinely won't touch git, and says he built a tool that uses AI to merge duplicate skills back into one clean version.
A guitarist got tired of paying for tabs, so he built a tool that just rips them straight off YouTube lesson videos.
What the article says
- This is a command line tool that turns a YouTube guitar lesson into a printable PDF of the tab.
- It downloads the video, grabs frames every couple seconds, and uses Claude's vision to find where the tab sits on screen.
- It reads the bar number printed on each line to tell duplicate frames apart from new ones, keeping only one crop per line.
- Those unique lines get stitched together into a single PDF you can print or scroll through.
- The builder admits it is early and untested across many different video styles.
What HN is saying
- Commenters mostly loved the idea, especially people frustrated with paying per tab on other sites.
- The sharpest fight was ethical. Some argued this quietly strips income from tab makers who rely on paid PDFs to fund free videos, while others said the maker is just repackaging information that was already public.
- A few pointed out real limits. It won't work on videos where the tab scrolls behind a fixed playhead, and printed sheet music is often more accurate than YouTube transcriptions anyway.
- One Soundslice cofounder chimed in, curious how it handles scrolling tab formats.
- Others swapped ideas for related tools, like scraping tabs from Ultimate Guitar or auto suggesting playable chord fingerings.