🔥
Hacker News 每日精选
2026年5月4日星期一 · 共 141 条 / 8 个分类 · Claude AI 翻译整理
头版热文 (10)近期最佳 (25)经典精选 (14)社区互动 (10)活跃讨论 (9)精选评论 (30)新品发布 (30)热点技术 (13)
头版热文 (10)
1.
Article URL: https://www.firgelli.com/pages/humanoid-robot-actuators Comments URL: https://news.ycombinator.com/item?id=48004380 Points: 99 # Comments: 20
📄原文 ·  💬HN讨论  · 05/04 11:42  · ofrzeta
2.
Article URL: https://xogium.me/the-text-mode-lie-why-modern-tuis-are-a-nightmare-for-accessibility Comments URL: https://news.ycombinator.com/item?id=48002938 Points: 196 # Comments: 82
📄原文 ·  💬HN讨论  · 05/04 07:59  · SpyCoder77
3.
Article URL: https://letsbuyspiritair.com/ Comments URL: https://news.ycombinator.com/item?id=48002777 Points: 310 # Comments: 300
📄原文 ·  💬HN讨论  · 05/04 07:36  · bjhess
4.
Article URL: https://jdgr.net/the-hidden-costs-of-great-abstractions Comments URL: https://news.ycombinator.com/item?id=48002607 Points: 148 # Comments: 51
📄原文 ·  💬HN讨论  · 05/04 07:12  · jdgr
5.
Article URL: https://github.com/aattaran/deepclaude Comments URL: https://news.ycombinator.com/item?id=48002136 Points: 405 # Comments: 147
📄原文 ·  💬HN讨论  · 05/04 06:13  · alattaran
6.
Article URL: https://validator.w3.org/feed/docs/atom.html Comments URL: https://news.ycombinator.com/item?id=48002089 Points: 86 # Comments: 27
📄原文 ·  💬HN讨论  · 05/04 06:08  · susam
7.
Article URL: https://www.smithsonianmag.com/smart-news/attributed-to-banksy-a-new-statue-of-a-suited-man-blinded-by-a-flag-and-walking-off-a-ledge-appeared-in-central-london-180988662/ Comments URL: https://news.ycombinator.com/item?id=48000152 Points: 367 # Comments: 323
📄原文 ·  💬HN讨论  · 05/04 02:54  · dryadin
8.
Article URL: https://wiki.alcidesfonseca.com/blog/why-tuis-are-back/ Comments URL: https://news.ycombinator.com/item?id=48000028 Points: 319 # Comments: 333
📄原文 ·  💬HN讨论  · 05/04 02:42  · rickcarlino
9.
Ever wanted to control Ableton with just your voice? Me too! I made this MCP server so I could just ask Codex to do anything in Ableton Live for me, while I was nap-trapped by my baby. The chat messages I sent to Codex to make this: in ableton, make a self reflective song, with audio vocals (via macos say) and chip tunes and 80's drum machines. should be a real edm banger i want midi for everything but vocals please, with ableton devices. not prerendered audio for instruments needs some fills and should hit way harder after "3-2-1 i become the sound" the vocals are squished too much (read too
📄原文 ·  💬HN讨论  · 05/04 02:05  · bschoepke
10.
Article URL: https://partyon.xyz/@nullagent/116499715071759135 Comments URL: https://news.ycombinator.com/item?id=47999636 Points: 348 # Comments: 113
📄原文 ·  💬HN讨论  · 05/04 02:03  · nullagent
近期最佳 (25)
1.
Article URL: https://larsfaye.com/articles/agentic-coding-is-a-trap Comments URL: https://news.ycombinator.com/item?id=48002442 Points: 335 # Comments: 240
📄原文 ·  💬HN讨论  · 05/04 06:52  · ayoisaiah
2.
After years of flying Southwest, I recently had the opportunity to tour the headquarters in Dallas. I particularly enjoyed seeing the full-motion 737 simulators, Network Operations Center, and TechOps maintenance hangar up close. Comments URL: https://news.ycombinator.com/item?id=47998946 Points: 232 # Comments: 72
📄原文 ·  💬HN讨论  · 05/04 01:02  · KatiMichel
3.
Article URL: https://www.thegamer.com/mgs2-hd-edition-source-code-massive-leak/ Comments URL: https://news.ycombinator.com/item?id=47998790 Points: 262 # Comments: 120
📄原文 ·  💬HN讨论  · 05/04 00:48  · rishabhd
4.
Article URL: https://isene.org/2026/05/Audience-of-One.html Comments URL: https://news.ycombinator.com/item?id=47997947 Points: 309 # Comments: 139
📄原文 ·  💬HN讨论  · 05/03 23:32  · xngbuilds
5.
Article URL: https://www.drive.com.au/news/mercedes-benz-commits-to-bringing-back-phycial-buttons/ Comments URL: https://news.ycombinator.com/item?id=47997418 Points: 670 # Comments: 380
📄原文 ·  💬HN讨论  · 05/03 22:43  · teleforce
6.
Article URL: https://acai.sh/blog/specsmaxxing Comments URL: https://news.ycombinator.com/item?id=47994012 Points: 266 # Comments: 278
📄原文 ·  💬HN讨论  · 05/03 14:33  · brendanmc6
7.
Article URL: https://thinkpol.ca/2026/04/30/an-open-weights-chinese-model-just-beat-claude-gpt-5-5-and-gemini-in-a-programming-challenge/ Comments URL: https://news.ycombinator.com/item?id=47993235 Points: 360 # Comments: 216
📄原文 ·  💬HN讨论  · 05/03 12:05  · bazlightyear
8.
Article URL: https://www.nytimes.com/2026/05/01/business/surveillance-pricing-groceries-maryland.html Comments URL: https://news.ycombinator.com/item?id=47992349 Points: 223 # Comments: 237
📄原文 ·  💬HN讨论  · 05/03 09:24  · doener
9.
Article URL: https://www.theguardian.com/technology/2026/apr/30/ai-outperforms-doctors-in-harvard-trial-of-emergency-triage-diagnoses Comments URL: https://news.ycombinator.com/item?id=47991981 Points: 374 # Comments: 312
📄原文 ·  💬HN讨论  · 05/03 08:30  · donsupreme
10.
Article URL: https://blog.haskell.org/a-couple-million-lines-of-haskell/ Comments URL: https://news.ycombinator.com/item?id=47991802 Points: 410 # Comments: 207
📄原文 ·  💬HN讨论  · 05/03 08:01  · unignorant
11.
Article URL: https://electrek.co/2026/05/02/this-tesla-owner-won-10k-in-court-for-teslas-fsd-lies-tesla-is-still-fighting-him/ Comments URL: https://news.ycombinator.com/item?id=47991350 Points: 275 # Comments: 139
📄原文 ·  💬HN讨论  · 05/03 06:45  · breve
12.
Article URL: https://www.david-smith.org/blog/2026/04/29/maps-on-watchos/ Comments URL: https://news.ycombinator.com/item?id=47990606 Points: 429 # Comments: 114
📄原文 ·  💬HN讨论  · 05/03 05:14  · valzevul
13.
Article URL: https://ladybird.org/newsletter/2026-04-30/ Comments URL: https://news.ycombinator.com/item?id=47990318 Points: 486 # Comments: 140
📄原文 ·  💬HN讨论  · 05/03 04:46  · richardboegli
14.
Article URL: https://www.universiteitleiden.nl/en/news/2025/07/neanderthals-ran-fat-factories-125000-years-ago Comments URL: https://news.ycombinator.com/item?id=47990284 Points: 282 # Comments: 155
📄原文 ·  💬HN讨论  · 05/03 04:42  · andsoitis
15.
Article URL: https://github.com/microsoft/vscode/pull/310226 Comments URL: https://news.ycombinator.com/item?id=47989883 Points: 1469 # Comments: 820
📄原文 ·  💬HN讨论  · 05/03 03:57  · indrora
16.
Article URL: https://nethack.org/v500/release.html Comments URL: https://news.ycombinator.com/item?id=47988776 Points: 506 # Comments: 168
📄原文 ·  💬HN讨论  · 05/03 02:03  · rsaarelm
17.
Article URL: https://www.bbc.com/news/articles/clypjx3rg2go Comments URL: https://news.ycombinator.com/item?id=47988742 Points: 317 # Comments: 349
📄原文 ·  💬HN讨论  · 05/03 01:59  · geox
18.
Article URL: https://donottrack.sh/ Comments URL: https://news.ycombinator.com/item?id=47988592 Points: 515 # Comments: 162
📄原文 ·  💬HN讨论  · 05/03 01:40  · RubyGuy
19.
Article URL: https://code.videolan.org/videolan/dav2d Comments URL: https://news.ycombinator.com/item?id=47988504 Points: 601 # Comments: 174
📄原文 ·  💬HN讨论  · 05/03 01:32  · dabinat
20.
Article URL: https://www.cnbc.com/2026/05/01/roblox-rblx-stock-child-safety-earnings.html Comments URL: https://news.ycombinator.com/item?id=47988261 Points: 245 # Comments: 147
📄原文 ·  💬HN讨论  · 05/03 01:10  · 1vuio0pswjnm7
21.
Article URL: https://arxiv.org/abs/2509.00462 Comments URL: https://news.ycombinator.com/item?id=47987256 Points: 329 # Comments: 178
📄原文 ·  💬HN讨论  · 05/02 23:28  · laurex
22.
Article URL: https://www.wsj.com/articles/americas-expanding-domestic-surveillance-08b73187 Comments URL: https://news.ycombinator.com/item?id=47987006 Points: 268 # Comments: 143
📄原文 ·  💬HN讨论  · 05/02 23:02  · Brajeshwar
23.
Article URL: https://www.bettedangerous.com/p/russia-poisons-wikipedia Comments URL: https://news.ycombinator.com/item?id=47986083 Points: 262 # Comments: 204
📄原文 ·  💬HN讨论  · 05/02 21:07  · exceptione
24.
Article URL: https://github.com/nexu-io/open-design Comments URL: https://news.ycombinator.com/item?id=47985750 Points: 221 # Comments: 91
📄原文 ·  💬HN讨论  · 05/02 20:16  · steveharing1
25.
Article URL: https://eclecticlight.co/2026/05/02/how-fast-is-a-macos-vm-and-how-small-could-it-be/ Comments URL: https://news.ycombinator.com/item?id=47984852 Points: 272 # Comments: 101
📄原文 ·  💬HN讨论  · 05/02 17:30  · moosia
经典精选 (14)
1.
Article URL: https://ambrook.com/offrange/environment/a-forest-in-your-pocket Comments URL: https://news.ycombinator.com/item?id=48000507 Points: 91 # Comments: 17
📄原文 ·  💬HN讨论  · 05/04 03:31  · bookofjoe
2.
Article URL: https://www.youtube.com/watch?v=8jNQDcpHc68 Comments URL: https://news.ycombinator.com/item?id=47999460 Points: 98 # Comments: 23
📄原文 ·  💬HN讨论  · 05/04 01:45  · cyrc
3.
Article URL: https://simpleobservability.com/docs/alert-driven-monitoring Comments URL: https://news.ycombinator.com/item?id=47997056 Points: 111 # Comments: 40
📄原文 ·  💬HN讨论  · 05/03 22:02  · khazit
4.
https://en.wikipedia.org/wiki/Nuclear_receptor_4A1 Comments URL: https://news.ycombinator.com/item?id=47995757 Points: 119 # Comments: 95
📄原文 ·  💬HN讨论  · 05/03 19:12  · pseudolus
5.
Hi HN, author here. SHARP is Apple's recent single-image 3D Gaussian splatting model ( https://arxiv.org/abs/2512.10685 ). Their reference code is PyTorch + a pretty heavy pipeline; I wanted to see if it could run in a browser with no server hop, so I exported the predictor to ONNX and ran it via onnxruntime-web with the WebGPU EP. What works: drop in an image, get a .ply you can download or preview live, all on your machine — your image never leaves the tab. The model is large (~2.4 GB sidecar) so first load is slow on a cold cache, but inference itself is a few seconds on a recent Mac. Cavea
📄原文 ·  💬HN讨论  · 05/03 17:14  · bring-shrubbery
6.
Article URL: https://easel.games/blog/2026-rollback-physics Comments URL: https://news.ycombinator.com/item?id=47981979 Points: 115 # Comments: 39
📄原文 ·  💬HN讨论  · 05/02 08:12  · BSTRhino
7.
Article URL: https://samcollins.blog/underdrawings/ Comments URL: https://news.ycombinator.com/item?id=47977990 Points: 177 # Comments: 50
📄原文 ·  💬HN讨论  · 05/02 02:07  · samcollins
8.
Article URL: https://www.nytimes.com/2026/04/29/arts/roger-sweet-dead-he-man.html Comments URL: https://news.ycombinator.com/item?id=47977510 Points: 41 # Comments: 8
📄原文 ·  💬HN讨论  · 05/02 01:29  · ChrisArchitect
9.
Article URL: https://phys.org/news/2026-04-usindian-space-mission-extreme-subsidence.html Comments URL: https://news.ycombinator.com/item?id=47974682 Points: 145 # Comments: 59
📄原文 ·  💬HN讨论  · 05/01 21:38  · leopoldj
10.
Article URL: https://github.com/earthtojake/text-to-cad Comments URL: https://news.ycombinator.com/item?id=47970497 Points: 109 # Comments: 30
📄原文 ·  💬HN讨论  · 05/01 09:48  · softservo
11.
Article URL: https://blog.stuffedcow.net/2019/09/hard-disk-geometry-microbenchmarking/ Comments URL: https://news.ycombinator.com/item?id=47968187 Points: 64 # Comments: 3
📄原文 ·  💬HN讨论  · 05/01 05:02  · TapamN
12.
Article URL: https://aruljohn.com/blog/macos-created-tar-files-linux-errors/ Comments URL: https://news.ycombinator.com/item?id=47961208 Points: 92 # Comments: 64
📄原文 ·  💬HN讨论  · 04/30 20:03  · heresie-dabord
13.
Article URL: https://www.scd31.com/posts/diy-hair-electrolysis-machine Comments URL: https://news.ycombinator.com/item?id=47943632 Points: 225 # Comments: 58
📄原文 ·  💬HN讨论  · 04/29 10:42  · y1n0
14.
Article URL: https://www.sourcefeed.app/ Comments URL: https://news.ycombinator.com/item?id=47939149 Points: 34 # Comments: 9
📄原文 ·  💬HN讨论  · 04/29 03:12  · bjhess
社区互动 (10)
1.
Comments URL: https://news.ycombinator.com/item?id=47771145 Points: 2 # Comments: 6
📄原文 ·  💬HN讨论  · 04/15 04:35  · Bender
2.
Comments URL: https://news.ycombinator.com/item?id=47543948 Points: 2 # Comments: 0
📄原文 ·  💬HN讨论  · 03/27 23:31  · Zigurd
3.
Comments URL: https://news.ycombinator.com/item?id=47385325 Points: 2 # Comments: 1
📄原文 ·  💬HN讨论  · 03/15 16:15  · chistev
4.
Comments URL: https://news.ycombinator.com/item?id=47282783 Points: 4 # Comments: 1
📄原文 ·  💬HN讨论  · 03/07 08:06  · consumer451
5.
Comments URL: https://news.ycombinator.com/item?id=47210537 Points: 10 # Comments: 3
📄原文 ·  💬HN讨论  · 03/02 04:51  · amelius
6.
Comments URL: https://news.ycombinator.com/item?id=47203860 Points: 1 # Comments: 4
📄原文 ·  💬HN讨论  · 03/01 12:56  · bwestergard
7.
Comments URL: https://news.ycombinator.com/item?id=47043735 Points: 2 # Comments: 3
📄原文 ·  💬HN讨论  · 02/17 12:33  · Austin_Conlon
8.
Comments URL: https://news.ycombinator.com/item?id=46886457 Points: 3 # Comments: 1
📄原文 ·  💬HN讨论  · 02/04 22:48  · Ariarule
9.
Comments URL: https://news.ycombinator.com/item?id=46866688 Points: 5 # Comments: 20
📄原文 ·  💬HN讨论  · 02/03 12:55  · andrewstuart
10.
Comments URL: https://news.ycombinator.com/item?id=46809755 Points: 2 # Comments: 7
📄原文 ·  💬HN讨论  · 01/29 21:11  · sam_lowry_
活跃讨论 (9)
1.
Article URL: https://www.lelanthran.com/chap15/content.html Comments URL: https://news.ycombinator.com/item?id=47999520 Points: 113 # Comments: 101
📄原文 ·  💬HN讨论  · 05/04 01:51  · lelanthran
2.
Article URL: https://gizmodo.com/the-oscars-just-banned-ai-from-winning-acting-and-writing-awards-2000753740 Comments URL: https://news.ycombinator.com/item?id=47999346 Points: 72 # Comments: 49
📄原文 ·  💬HN讨论  · 05/04 01:34  · ZeidJ
3.
Article URL: https://chromium-drift.pages.dev/ Comments URL: https://news.ycombinator.com/item?id=47999006 Points: 176 # Comments: 59
📄原文 ·  💬HN讨论  · 05/04 01:05  · skaul
4.
Article URL: https://old.reddit.com/r/vibecoding/comments/1srfqm0/uncle_bob_its_over/ Comments URL: https://news.ycombinator.com/item?id=47998601 Points: 58 # Comments: 84
📄原文 ·  💬HN讨论  · 05/04 00:29  · lopespm
5.
Article URL: https://christophermeiklejohn.com/ai/personal/phish/flow/agents/2026/05/03/rift.html Comments URL: https://news.ycombinator.com/item?id=47998225 Points: 217 # Comments: 172
📄原文 ·  💬HN讨论  · 05/03 23:55  · azhenley
6.
Article URL: https://mobeigi.com/blog/security/security-through-obscurity-is-not-bad/ Comments URL: https://news.ycombinator.com/item?id=47997486 Points: 152 # Comments: 164
📄原文 ·  💬HN讨论  · 05/03 22:49  · mobeigi
7.
Article URL: https://www.tomshardware.com/software/vpn/utah-becomes-first-us-state-to-target-vpn-use-with-age-verification-law Comments URL: https://news.ycombinator.com/item?id=47997358 Points: 215 # Comments: 248
📄原文 ·  💬HN讨论  · 05/03 22:36  · GavinAnderegg
8.
Article URL: https://newsroom.porsche.com/en_US/2026/motorsport/porsche-will-contest-laguna-seca-in-historic-colors-of-the-apple-computer-livery.html Comments URL: https://news.ycombinator.com/item?id=47997138 Points: 111 # Comments: 50
📄原文 ·  💬HN讨论  · 05/03 22:13  · Amorymeltzer
9.
Article URL: https://www.ft.com/content/9921f2b5-c910-4cec-a50f-cad453935a1a Comments URL: https://news.ycombinator.com/item?id=47995125 Points: 122 # Comments: 170
📄原文 ·  💬HN讨论  · 05/03 17:26  · JumpCrisscross
精选评论 (30)
1.
Interestingly I’ve learned more about languages and systems and tools I use in the last few years working with agentic coding than I did in 35 years of artisanal programming. I am still vastly superior at making decisions about systems and techniques and approaches than the agentic tools, but they are like a really really well read intern who knows a great deal of detail about errata but have very little experience. They enthusiastically make mistakes but take feedback - at least up front - even if they often forget because they don’t totally understand and haven’t internalized it. The claim y
📄原文 ·  💬HN讨论  · 05/04 08:56  · fnordpiglet
2.
#!/bin/sh export ANTHROPIC_BASE_URL=https://api.deepseek.com/anthropic export ANTHROPIC_AUTH_TOKEN=sk-secret export ANTHROPIC_MODEL=deepseek-v4-flash export CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1 exec claude $@
📄原文 ·  💬HN讨论  · 05/04 07:16  · aftbit
3.
I'm not exactly sure what the point of this is. Deepseek already has instructions to use its API with many CLI's including Claude Code directly: https://api-docs.deepseek.com/quick_start/agent_integrations...
📄原文 ·  💬HN讨论  · 05/04 07:07  · vitaflo
4.
The point is not just that he's blinded by the flag: He's boldly marching into the void, confident. "wrapped in the flag" is a great saying.
📄原文 ·  💬HN讨论  · 05/04 04:18  · ggm
5.
I'd be very very hesitant to trust studies like this. It's very easy to mess up these benchmarks. See for example this recent paper where AI managed to beat radiologists on interpreting x-rays... when the AI didn't even have access to the x-rays: https://arxiv.org/pdf/2603.21687 (on a pre existing "large scale visual question answering benchmark for generalist chest x-ray understanding" that wasn't intentionally messed up). And in interpreting x-ray's human radiologists actually do just look at the x-rays. In the context the article is discussing the human doctors don't just look at the notes
📄原文 ·  💬HN讨论  · 05/04 03:29  · gpm
6.
I think part of it is also that we're able to still LARP as full developers of complex systems while vibe coding by seeing an interface that makes us look like l33t h4xx0rs even though we're just pressing continue 15 times
📄原文 ·  💬HN讨论  · 05/04 03:18  · schmorptron
7.
Obscurity can be fine but it's not security. I think of it like cover and concealment in the military. Security is cover. Something you can get behind so the bullets don't hit you. Obscurity is concealment. Harder to see, harder to find, so the enemy doesn't know where to shoot, but it's not stopping any bullets. Both have advantages and disadvantages and can complement each other depending on how they're used.
📄原文 ·  💬HN讨论  · 05/04 03:00  · rascul
8.
I would like to see all "desktop" applications that use Electron listed and how big of a Chromium drift is there, especially how many applications are shipping runtimes with unfixed vulnerabilities.
📄原文 ·  💬HN讨论  · 05/04 01:19  · butz
9.
'He also explained that "I'm a big believer in screens, because I really believe if you want to connect, you have to make the magic work behind the screen." ' I am a big believer in keeping "product people" away from UI design for dangerous machinery. The eyes and the attention of the driver should be on the road. All the audio visual noise from the car is just plain dangerous. I don't want my car to draw my attention to itself for anything less than a critical engine/tyre pressure failures. I do not want beeps on anything else distracting me while I am driving. My Volvo will, for instance, fl
📄原文 ·  💬HN讨论  · 05/03 23:57  · aenis
10.
I’m quite suspicious that they do that not because they understood or learned something, but because China requires physical buttons starting next year. And they simply don’t want to lose one of their biggest markets.
📄原文 ·  💬HN讨论  · 05/03 23:17  · nokeya
11.
I am completely baffled by this wave of new laws and proposals... they feel dystopic and can seemingly only lead to brutal restrictions on the internet. What will we end up with? Only attested modems / endpoints in the home? With DPI? And a government issued smartcard to use it? It comes across as if this is what some legislators are actually after... they must have some technical advisors who can explain to them that the solutions they propose will not work and I am a bit worried they will morph the public discussion into enforcing at a lower level otherwise "the bad guys still circumvent"??
📄原文 ·  💬HN讨论  · 05/03 22:52  · mvdwoord
12.
I recently got locked out of my machine because logging in with the mandatory Microsoft account-backed primary user of my machine didn't work anymore. It said I was offline and I had to use the "previous password" even though I didn't have a previous password for that account. Hacking around in the recovery console to add another administrator user worked, but then I couldn't reset the original user's password because it was tied to the Microsoft account and you can't change the password locally. I don't need Copilot managing my inbox through AI, nor do I need a more exciting widget experience
📄原文 ·  💬HN讨论  · 05/03 18:49  · sagacity
13.
What people realy want: as little OS as possible to let them run just the things on their computer they want to run. What Microsoft wants: Windows as their straightjacket into the Microsoft services as that is where the revenue is. Why Windows got this bad: incentives and coercion placed on the teams to show uptake on the services no matter what leading to perversion in tactics and complete alienation of the user base. The incentives are alomost perpendicularly misaligned. Regaining trust is extremely hard after you've crossed an edge. People are looking for the exit, finding there is indeed a
📄原文 ·  💬HN讨论  · 05/03 16:01  · PeterStuer
14.
These posts are going to be a constant for the next year, because there's no objective way to compare models (past low-level numbers like token generation speed, average reasoning token amount, # of parameters, active experts, etc). They're all quite different in a lot of ways, they're used for many different things by different people, and they're not deterministic. So you're constantly gonna see benchmarks and tests and proclamations of "THIS model beat THAT model!", with people racing around trying to find the best one. But there is no best one. There's just the best one for you, based on w
📄原文 ·  💬HN讨论  · 05/03 13:31  · 802566433774
15.
Changing the default behavior for all of your users with no notification is pretty unforgivable. Even if this feature worked correctly, it obviously doesn’t, this should at minimum be a prompt after upgrade to let the user confirm that this is what they want. But honestly should be opt in for those that want it. To have it silently just start adding marketing copy to git commit messages is pretty bad. To have that added text not be visible to the user in the UI so they can remove it before commit is just much worse. This kind of thing being released speaks to a greater disfunction over there.
📄原文 ·  💬HN讨论  · 05/03 10:08  · alemanek
16.
I think the constructive criticism is best directed at whatever process you are following. That process allowed a very visible user facing change in a widely used piece of software. How did this change make it to production without some process catching the impact of this change? Was there really no internal discussion from a code review at least? This seems hard for me to believe. I expect more from Microsoft.
📄原文 ·  💬HN讨论  · 05/03 09:15  · somebehemoth
17.
I am the person who approved this PR and would like to acknowledge and apologize for the mistake of turning this feature on by default without sufficient upfront validation. There was no ill intent by evil corporation, but rather a desire to support functionality that some customers expect of VS Code w.r.t. AI-generated code. As folks mentioned here - many similar tools do this as well. Obviously, it should not be on when disableAIFeatures is on and it should not be reporting changes that were not done by AI. I'll work on fixing those and meanwhile revert default to off in 1.119 update. I am o
📄原文 ·  💬HN讨论  · 05/03 08:06  · dmitriv
18.
To everyone who bought the "developer-friendly" Microsoft of VSCode fame from a few years ago: this is what they forever did, and forever will do. This company has been pulling these tricks since the early 90s. If you fell for this once again, there's nobody else to blame but yourself.
📄原文 ·  💬HN讨论  · 05/03 06:27  · artyom
19.
Absolutely, messing with commits is more invasive than messages. It gets worse: "Sent from my iPhone" appears in the authoring view, and you can delete it. Co-authored-by: NEVER appears in the commit message UI - it is added without the user even seeing it.
📄原文 ·  💬HN讨论  · 05/03 06:09  · tln
20.
Principal engineer balks at bad UX when the PM should know better (it's their job) 2023: Ah well I guess we can't do it 2025: you're fired. Hey kid we hired two weeks ago, implement bad idea please
📄原文 ·  💬HN讨论  · 05/03 06:08  · mohamedkoubaa
21.
It's a complete takeover of technically incompetent management that feels like it can finally execute their ideas to the fullest instead of relying on those pesky swengs with their obstructions, complaints and problems. We'll soon get the management utopia everywhere.
📄原文 ·  💬HN讨论  · 05/03 06:04  · storus
22.
This feels like the modern version of 'Sent from my iPhone' but much more invasive. Git commits are legal and technical records. Falsifying who authored a piece of code just to pump up AI usage stats is a huge breach of trust and it is disappointing to see Microsoft prioritize branding over the integrity of the developer's log. I expect my IDE to record what happened, not what the marketing department wants people to think happened.....
📄原文 ·  💬HN讨论  · 05/03 05:36  · yankohr
23.
One fascinating thing about the whole AI phenomenon is how incredibly hostile it is to _standards_. Whether something works properly, or is ethical, or is true, no longer matters at all; all that matters is "pls use our AI". Microsoft spent literal decades rehabilitating their reputation. And then set fire to the whole thing in an offering to their robot gods. And it's not just them. There was a time that Google cared deeply about UX. Now, on macOS Google remaps CMD-G in Google Docs to launch some LLM bullshit (EDIT: huh, they may have fixed this; it was definitely doing it a couple of weeks a
📄原文 ·  💬HN讨论  · 05/03 05:06  · rsynnott
24.
We had to set it up on the parts of VideoLAN infra so the service would remain usable. Otherwise it was under a constant DDoS by the AI bots.
📄原文 ·  💬HN讨论  · 05/03 02:57  · thresh
25.
Not on topic, but wow the internet has very quickly devolved into: click -> "making sure you're not a bot", click -> "making sure you're a human", click -> "COOKIES COOKIES COOKIES", click -> "cloudflare something something"
📄原文 ·  💬HN讨论  · 05/03 02:30  · tensor
26.
I am, in general, hoping AV will reduce road deaths in the future. The last hurdle is regulatory. We can’t let AV manufacturers use “there’s no driver” as a way to escape responsibility, externalizing the harms AC cause onto society. The question is how to achieve fairness. If a human driver commits vehicular manslaughter, they get the book. What about AV? $10 million? Executives go to jail? What if $10 million fine per X AV miles driven is an OK cost of doing business?
📄原文 ·  💬HN讨论  · 05/03 02:26  · callc
27.
Project description: dav2d is the fastest AV2 decoder on all platforms :) Targeted to be small, portable and very fast. If you're out of the loop like me: AV2 is the next-generation video coding specification from the Alliance for Open Media (AOMedia). Building on the foundation of AV1, AV2 is engineered to provide superior compression efficiency, enabling high-quality video delivery at significantly lower bitrates. It is optimized for the evolving demands of streaming, broadcasting, and real-time video conferencing. - from https://av2.aomedia.org/
📄原文 ·  💬HN讨论  · 05/03 02:19  · jzebedee
28.
The control group should still be sleep deprived for 6 months and see what that does to their brain.
📄原文 ·  💬HN讨论  · 05/02 21:43  · jonplackett
29.
The biggest differentiator for me: DeepSeek just does what I ask. I've tried using both GPT and Claude for reverse engineering recently, both refused. I even got a warning on my OpenAI account.
📄原文 ·  💬HN讨论  · 05/02 21:04  · cedws
30.
This is content marketing executed perfectly :) Reading it, I learned something new and interesting and they had an opportunity to show off one of their differentiators against the competition (low leakage flow due to tighter tolerances) and then at the end they casually mention the new product that has just opened for pre-orders.
📄原文 ·  💬HN讨论  · 05/02 15:39  · fxtentacle
新品发布 (30)
1.
Hey! I am Alex and together with my co-founder Tarun built Kampala ( https://www.zatanna.ai/kampala ). It’s a man-in-the-middle (MITM) style proxy that allows you to agentically reverse engineer existing workflows without brittle browser automation or computer use agents. It works for websites, mobile apps, desktop apps. Demo: https://www.youtube.com/watch?v=z_PeostC-b4 . Many people spend hours per day in legacy dashboards and on-prem solutions reconciling data across platforms. Current attempts at automation use browser automations or computer use agents which are brittle, slow, and nondeter
📄原文 ·  💬HN讨论  · 04/16 23:19  · alexblackwell_
2.
Hey HN, we're Willy and Dan, co-founders of Twill.ai ( https://twill.ai/ ). Twill runs coding CLIs like Claude Code and Codex in isolated cloud sandboxes. You hand it work through Slack, GitHub, Linear, our web app or CLI, and it comes back with a PR, a review, a diagnosis, or a follow-up question. It loops you in when it needs your input, so you stay in control. Demo: https://www.youtube.com/watch?v=oyfTMXVECbs Before Twill, building with Claude Code locally, we kept hitting three walls 1. Parallelization: two tasks that both touch your Docker config or the same infra files are painful to run
📄原文 ·  💬HN讨论  · 04/11 00:22  · danoandco
3.
Hey HN! We are Bharath, and Simranjit from Relvy AI ( https://www.relvy.ai ). Relvy automates on-call runbooks for software engineering teams. It is an AI agent equipped with tools that can analyze telemetry data and code at scale, helping teams debug and resolve production issues in minutes. Here’s a video: [[[ https://www.youtube.com/watch?v=BXr4_XlWXc0 ]]] A lot of teams are using AI in some form to reduce their on-call burden. You may be pasting logs into Cursor, or using Claude Code with Datadog’s MCP server to help debug. What we’ve seen is that autonomous root cause analysis is a hard p
📄原文 ·  💬HN讨论  · 04/09 20:11  · behat
4.
We’re Ben and Jacob, cofounders of Freestyle ( https://freestyle.sh ). We’re building a cloud for Coding Agents. For the first generation of agents it looked like workflows with minimal tools. 2 years ago we published a package to let AI work in SQL, at that time GPT-4 could write simple scripts. Soon after the first AI App Builders started using AI to make whole websites; we supported that with a serverless deploy system. But the current generation is going much further, instead of minimal tools and basic serverless apps AI can utilize the full power of a computer (“sandbox”). We’re building
📄原文 ·  💬HN讨论  · 04/07 00:32  · benswerd
5.
Hi HN! We're Vincent and Jochen from sitefire ( https://sitefire.ai ). Our platform makes it easy for brands to improve their visibility in AI search. We’ve been working together for years and have backgrounds in RL/optimization at Stanford and software engineering. We came to this idea after speaking with marketing teams who were seeing declining traffic due to Google’s AI Overviews and didn’t know what to do. This space can feel esoteric. Many case studies, few actual studies. Constant battle against myths (e.g. you need a llms.txt vs. you don't need a llms.txt) and "GEO hacks". We try to be
📄原文 ·  💬HN讨论  · 03/21 01:05  · vincko
6.
Hey HN! We’re Hayden, Ronan, Avi, and Warren of Voltair ( https://voltairlabs.com/ ). We’re making weatherized, hybrid-fixed drones deployed for power utility inspections. Here’s some footage: https://vimeo.com/1173862237/ac28095cc6?share=copy&fl=sv&fe=... and a photo of our latest prototype: https://imgur.com/a/bYHnqZ4 . The U.S. has 7M miles of power lines (enough to go to the moon and back 14 times), and they're aging. Over 50% of all power flows through transformers that are at least 30 years old, which is about when they start to fail. Power line conductors are just bare metal with 4,000-
📄原文 ·  💬HN讨论  · 03/20 00:57  · wweissbluth
7.
Hey HN! We're Aakash and Viswesh, and we're building Canary ( https://www.runcanary.ai ). We build AI agents that read your codebase, figure out what a pull request actually changed, and generate and execute tests for every affected user workflow. Aakash and I previously built AI coding tools at Windsurf, Cognition, and Google. AI tools were making every team faster at shipping, but nobody was testing real user behavior before merge. PRs got bigger, reviews still happened in file diffs, and changes that looked clean broke checkout, auth, and billing in production. We saw it firsthand. We start
📄原文 ·  💬HN讨论  · 03/20 00:01  · Visweshyc
8.
Hey HN! We’re Carmel and Rhea, the founders of Kita ( https://www.usekita.com/ ). We automate credit review for lenders in emerging markets using VLMs. In many emerging markets, like the Philippines and Mexico, credit infrastructure is weak. Open finance is still nascent, and credit bureaus are unreliable. So to apply for a loan, lenders rely on borrowers submitting documentation to understand their ability to repay. A borrower can submit financial documents, such as bank statements and payslips, in any format, from pdfs, images of physical documents and screenshots. On top of that, financial
📄原文 ·  💬HN讨论  · 03/18 03:46  · rheamalhotra1
9.
Hey HN, we're Jie Shen, Charles, Andreas, and Shaocheng. We built Chamber ( https://usechamber.io ), an AI agent that manages GPU infrastructure for you. You talk to it wherever your team already works and it handles things like provisioning clusters, diagnosing failed jobs, managing workloads. Demo: https://www.youtube.com/watch?v=xdqh2C_hif4 We all worked on GPU infrastructure at Amazon. Between us we've spent years on this problem — monitoring GPU fleets, debugging failures at scale, building the tooling around it. After leaving we talked to a bunch of AI teams and kept hearing the same stu
📄原文 ·  💬HN讨论  · 03/17 01:09  · jshen96
10.
Hi HN, we’re Yarik and Vlad from VOYGR ( https://voygr.tech/ ), working on better real-world place intelligence for app developers and agents. Here’s a demo: https://www.youtube.com/watch?v=cNIpcWIE0n4 . Google Maps can tell you a restaurant is "4.2 stars, open till 10." Their API can't tell you the chef left last month, wait times doubled, and locals moved on. Maps APIs today just give you a fixed snapshot. We're building an infinite, queryable place profile that combines accurate place data with fresh web context like news, articles, and events. Vlad worked on the Google Maps APIs as well as
📄原文 ·  💬HN讨论  · 03/17 00:21  · ymarkov
11.
Hi HN, we’re Lewis and Edgar, building Captain to simplify unstructured data search ( https://runcaptain.com ). Captain automates the building and maintenance of file-based RAG pipelines. It indexes cloud storage like S3 and GCS, plus SaaS sources like Google Drive. There’s a quick walkthrough at https://youtu.be/EIQkwAsIPmc . We also put up this demo site called “Ask PG’s Essays” which lets you ask/search the corpus of pg’s essays, to get a feel for how it works: https://pg.runcaptain.com . The RAG part of this took Captain about 3 minutes to set up. Here are some sample prompts to get a feel
📄原文 ·  💬HN讨论  · 03/13 23:45  · CMLewis
12.
Hey HN! We're Ashwin and Akshay from Spine AI ( https://www.getspine.ai ). Spine Swarm is a multi-agent system that works on an infinite visual canvas to complete complex non-coding projects: competitive analysis, financial modeling, SEO audits, pitch decks, interactive prototypes, and more. Here's a video of it in action: https://www.youtube.com/watch?v=R_2-ggpZz0Q . We've been friends for over 13 years. We took our first ML course together at NTU, in a part of campus called North Spine, which is where the name comes from. We went through YC in S23 and have spent about 3 years building Spine
📄原文 ·  💬HN讨论  · 03/13 21:22  · a24venka
13.
Hey HN — I’m Veer and my cofounder is Suryaa. We're building Cumulus Labs (YC W26), and we're releasing our latest product IonRouter ( https://ionrouter.io/ ), an inference API for open-source and fine tuned models. You swap in our base URL, keep your existing OpenAI client code, and get access to any model (open source or finetuned to you) running on our own inference engine. The problem we kept running into: every inference provider is either fast-but-expensive (Together, Fireworks — you pay for always-on GPUs) or cheap-but-DIY (Modal, RunPod — you configure vLLM yourself and deal with slow
📄原文 ·  💬HN讨论  · 03/13 02:52  · vshah1016
14.
Hey HN! We're Neel and Anay, and we’re building Sentrial ( https://sentrial.com ). It’s production monitoring for AI products. We automatically detect failure patterns: loops, hallucinations, tool misuse, and user frustrations the moment they happen. When issues surface, Sentrial diagnoses the root cause by analyzing conversation patterns, model outputs, and tool interactions, then recommends specific fixes. Here's a demo if you're interested: https://www.youtube.com/watch?v=cc4DWrJF7hk . When agents fail, choose wrong tools, or blow cost budgets, there's no way to know why - usually just logs
📄原文 ·  💬HN讨论  · 03/12 00:24  · anayrshukla
15.
Hey HN — we’re Rajit, Land, and Alex. We’re building Prism ( https://www.prismvideos.com ), an AI video creation platform and API. Here’s a quick demo of how you can remix any video with Prism: https://youtu.be/0eez_2DnayI Here’s a quick demo of how you can automate UGC-style ads with Openclaw + Prism: https://www.youtube.com/watch?v=5dWaD23qnro Accompanying skill.md file: https://docs.google.com/document/d/1lIskVljW1OqbkXFyXeLHRsfM... Making an AI video today usually means stitching together a dozen tools (image generation, image-to-video, upscalers, lip-sync, voiceover, and an editor). Every
📄原文 ·  💬HN讨论  · 03/12 00:16  · aliu327
16.
Hi HN, we're Sanchit and Shubham (YC W26). We built a fast inference engine for Apple Silicon. LLMs, speech-to-text, text-to-speech – MetalRT beats llama.cpp, Apple's MLX, Ollama, and sherpa-onnx on every modality we tested. Custom Metal shaders, no framework overhead. Also, we've open-sourced RCLI, the fastest end-to-end voice AI pipeline on Apple Silicon. Mic to spoken response, entirely on-device. No cloud, no API keys. To get started: brew tap RunanywhereAI/rcli https://github.com/RunanywhereAI/RCLI.git brew install rcli rcli setup # downloads ~1 GB of models rcli # interactive mode with p
📄原文 ·  💬HN讨论  · 03/11 01:14  · sanchitmonga22
17.
Hi HN, I’m Alberto. I co-founded Didit ( https://didit.me ) with my identical twin brother Alejandro. We are building a unified identity layer—a single integration that handles KYC, AML, biometrics, authentication, and fraud prevention globally. Here’s a demo: https://www.youtube.com/watch?v=eTdcg7JCc4M&t=7s . Being identical twins, we’ve spent our whole lives dealing with identity confusion, so it is a bit of irony that we ended up building a company to solve it for the internet. Growing up in Barcelona, we spent years working on products where identity issues were a massive pain. We eventual
📄原文 ·  💬HN讨论  · 03/10 23:08  · rosasalberto
18.
Hello Hacker News! We're Filip, Stavros, and Vivek from Terminal Use ( https://www.terminaluse.com/ ). We built Terminal Use to make it easier to deploy agents that work in a sandboxed environment and need filesystems to do work. This includes coding agents, research agents, document processing agents, and internal tools that read and write files. Here's a demo: https://www.youtube.com/watch?v=ttMl96l9xPA . Our biggest pain point with hosting agents was that you'd need to stitch together multiple pieces: packaging your agent, running it in a sandbox, streaming messages back to users, persistin
📄原文 ·  💬HN讨论  · 03/10 00:53  · filipbalucha
19.
Hi HN! We’re Sam and Michael from Palus Finance ( https://palus.finance ). We’re building a treasury management platform for startups and SMBs to earn higher yields with a high-yield bond portfolio. We were funded by YC for a consumer-focused product for higher-yield savings. But when we joined YC and got our funding, we realized we needed the product for our own startup’s cash reserves, and other startups in the batch started telling us they wanted this too. We realized that traditional startup treasury products do much the same thing: open a brokerage account, sweep your cash into a money ma
📄原文 ·  💬HN讨论  · 03/07 02:26  · sam_palus
20.
Hi HN! We're Gobhanu and Saatvik (brothers), building Vela ( https://tryvela.ai ) - AI agents that handle multi-party, multi-channel scheduling. Scheduling is a constraint satisfaction problem disguised as email! It’s easy when it’s two people, one timezone, one channel. But it becomes a constraint satisfaction problem when inputs are unstructured natural language across multiple communication channels, constraints change mid-solve, and the objective function includes social dynamics that don't exist formally anywhere. What if scheduling just happened? For example: a recruiter sends one messag
📄原文 ·  💬HN讨论  · 03/06 01:43  · Gobhanu
21.
Hey HN - we're Tarush, Sidhant, and Shashij from Cekura ( https://www.cekura.ai ). We've been running voice agent simulation for 1.5 years, and recently extended the same infrastructure to chat. Teams use Cekura to simulate real user conversations, stress-test prompts and LLM behavior, and catch regressions before they hit production. The core problem: you can't manually QA an AI agent. When you ship a new prompt, swap a model, or add a tool, how do you know the agent still behaves correctly across the thousands of ways users might interact with it? Most teams resort to manual spot-checking (d
📄原文 ·  💬HN讨论  · 03/03 22:30  · atarus
22.
Hi HN! My name is Rohan and, together with Paul, I’m the co-founder of OctaPulse ( https://www.tryoctapulse.com/ ). We’re building a robotics layer for seafood production, starting with automated fish inspection. We are currently deployed at our first production site with the largest trout producer in North America. You might be wondering how the heck we got into this with no background in aquaculture or the ocean industry. We are both from coastal communities. I am from Goa, India and Paul is from Malta and Puerto Rico. Seafood is deeply tied to both our cultures and communities. We saw first
📄原文 ·  💬HN讨论  · 03/03 00:39  · rohxnsxngh
23.
Hey HN - we're Saksham and Ishan, and we’re building Cardboard ( https://www.usecardboard.com ). It lets you go from raw footage to an edited video by describing what you want in natural language. There’s a demo video at https://www.usecardboard.com/share/fUN2i9ft8B46 , and you can try the product out at https://demo.usecardboard.com (no login required!) People sit on mountains of raw assets - product walkthroughs, customer interviews, travel videos, screen recordings, changelogs, etc. - that could become testimonials, ads, vlogs, launch videos, etc. Instead they sit in cloud storage / hard dr
📄原文 ·  💬HN讨论  · 02/27 02:38  · sxmawl
24.
Hi HN, I’m Vincent, CTO of TeamOut ( https://www.teamout.com/ ). We build an AI agent that plans company events from start to finish entirely through conversation. Similar to how Lovable helps build websites through chat, we apply that approach to event planning. Our system handles venue sourcing, vendor coordination, flight cost estimation, itinerary building, and overall project management. Here’s a demo: https://www.youtube.com/watch?v=QVyc-x-isjI . The product is live at https://app.teamout.com/ai and does not require signup. We went through YC in 2022 but did not launch on HN at the time.
📄原文 ·  💬HN讨论  · 02/25 22:02  · vincentalbouy
25.
Hey HN, I am Dimittri and we’re building Sonarly ( https://sonarly.com ), an AI engineer for production. It connects to your observability tools like Sentry, Datadog, or user feedback channels, triages issues, and fixes them to cut your resolution time. Here's a demo: https://www.youtube.com/watch?v=rr3VHv0eRdw . Sonarly is really about removing the noise from production alerts by grouping duplicates and returning a root cause analysis to save time to on-call engineers and literally cut your MTTR. Before starting this company, my co-founder and I had a B2C app in edtech and had, some days, tho
📄原文 ·  💬HN讨论  · 02/18 01:03  · Dimittri
26.
Hey y’all, Kartik, Ishaan, and Christian from Omnara ( https://www.omnara.com/ ) here. We’re building a web and mobile agentic IDE for Claude Code and Codex that lets you run and interact with coding agents from anywhere. Omnara lets you run Claude Code and Codex sessions on your own machine, and exposes those sessions through a web and mobile interface so you can stay involved even when you’re away from your desk. Think of it like Claude Code Desktop or Conductor, except you can continue your sessions on your phone. Here’s a demo of the web and mobile apps - https://youtu.be/R8Wmy4FLbhQ We st
📄原文 ·  💬HN讨论  · 02/13 01:14  · kmansm27
27.
Hi HN, I'm Arsalan, founder of LiveDocs ( https://livedocs.com ). We're building an AI-native data workspace that lets teams ask questions of their real data and have the system plan, execute, and maintain the analysis end-to-end. We previously posted about LiveDocs four years ago ( https://news.ycombinator.com/item?id=30735058 ). Back then, LiveDocs was a no-code analytics tool for stitching together metrics from tools like Stripe and Google Analytics. It worked for basic reporting, but over time we ran into the same ceiling our users did. Dashboards are fine until the questions get messy, an
📄原文 ·  💬HN讨论  · 02/11 02:09  · arsalanb
28.
Hi all, Aram and Eduard here - co-founders of Modelence ( https://modelence.com ). After spending years on scaling our previous startup’s platform, we built an open-source full-stack TypeScript + MongoDB framework to stop solving the same auth / database / API / cron job implementations every time we created an app, and we didn’t like the idea of using multiple managed platforms for each of these to run our apps either. (Here’s our prior Show HN post for reference: https://news.ycombinator.com/item?id=44902227 ) At the same time, we were excited by the whole AI app builder boom and realized th
📄原文 ·  💬HN讨论  · 02/04 00:03  · eduardpi
29.
Hey HN, we're Haakam, Michael, and Adi. We're building AgentMail ( https://agentmail.to ), the email inbox API for agents. We’re not talking about AI for your email, this is email for your AI. Email is an optimal interface for long-running agents. It’s multithreaded and asynchronous with full support for rich text and files. It’s a universal protocol with identity and authentication built in. Moreover, a lot of workflow critical context already lives in email. We wanted to build email agents that you can forward your work to and get back a completed task. The agents could act entirely autonomo
📄原文 ·  💬HN讨论  · 01/30 00:42  · Haakam21
30.
Hi HN! We're Kamran, Raaid, Laith, and Omeed from Constellation Space ( https://constellation-io.com/ ). We built an AI system that predicts satellite link failures before they happen. Here's a video walkthrough: https://www.youtube.com/watch?v=069V9fADAtM . Between us, we've spent years working on satellite operations at SpaceX, Blue Origin, and NASA. At SpaceX, we managed constellation health for Starlink. At Blue, we worked on next-gen test infra for New Glenn. At NASA, we dealt with deep space communications. The same problem kept coming up: by the time you notice a link is degrading, you'
📄原文 ·  💬HN讨论  · 01/23 01:03  · kmajid
热点技术 (13)
1.
Article URL: https://reclaimthenet.org/senate-panel-backs-guard-act-ai-age-verification-bill Comments URL: https://news.ycombinator.com/item?id=48002681 Points: 34 # Comments: 4
📄原文 ·  💬HN讨论  · 05/04 07:22  · g42gregory
2.
Article URL: https://death-of-scrum.net/ Comments URL: https://news.ycombinator.com/item?id=47999880 Points: 36 # Comments: 45
📄原文 ·  💬HN讨论  · 05/04 02:28  · mantyx
3.
Article URL: https://www.americanscientist.org/article/each-blade-a-single-crystal Comments URL: https://news.ycombinator.com/item?id=47997059 Points: 58 # Comments: 23
📄原文 ·  💬HN讨论  · 05/03 22:02  · whycome
4.
Hey HN community, I built a tool that helps optimize your post for hitting the first page of Show HN. How it works: I used a Hugging Face dataset of all Hacker News posts from the past 3 years and trained a model that predicts how successful your post might be. There's still a lot of randomness on HN, so nothing is guaranteed, but the tool helps optimize your post for higher odds. A couple of interesting findings: - GitHub repo links work x3 better than regular domains - Open-source tools have a steady virality rate (13.9% - one of the highest) - "I built" outperforms "We built" - Using parent
📄原文 ·  💬HN讨论  · 05/03 20:02  · margotli
5.
Demo: https://www.youtube.com/watch?v=f5uygzEmdLw Hi HN, I built a RISC-V emulator that implements the RV32IM instruction set and a minimal syscall interface to run DOOM. A few weeks ago, I got my first output with a simple hello world assembly program. Since then I have been working tirelessly to get DOOM to run. I needed to figure out how to run C programs first, and came across newlib, which allows the underlying environment to implement the syscall stubs one by one until the programs run. I have also added ELF loading, but currently only a single `PT_LOAD` segment is supported. To port DOO
📄原文 ·  💬HN讨论  · 05/03 19:57  · Flex247A
6.
Article URL: https://blog.feld.me/posts/2026/04/open-source-does-not-imply-open-community/ Comments URL: https://news.ycombinator.com/item?id=47992772 Points: 185 # Comments: 83
📄原文 ·  💬HN讨论  · 05/03 10:36  · RohanAdwankar
7.
Article URL: https://www.clojuriststogether.org/news/q2-2026-funding-announcement/ Comments URL: https://news.ycombinator.com/item?id=47990789 Points: 135 # Comments: 16
📄原文 ·  💬HN讨论  · 05/03 05:34  · dragandj
8.
Article URL: https://mirandaheath.website/static/oss_burnout_report_mh_25.pdf Comments URL: https://news.ycombinator.com/item?id=47981669 Points: 132 # Comments: 66
📄原文 ·  💬HN讨论  · 05/02 07:24  · susam
9.
Article URL: https://courses.joshwcomeau.com/wham/open-house/00-introduction Comments URL: https://news.ycombinator.com/item?id=47979190 Points: 109 # Comments: 10
📄原文 ·  💬HN讨论  · 05/02 03:35  · SpyCoder77
10.
Article URL: https://github.com/calebwin/gitgres Comments URL: https://news.ycombinator.com/item?id=47977659 Points: 42 # Comments: 23
📄原文 ·  💬HN讨论  · 05/02 01:40  · calebhwin
11.
Article URL: https://keepthingsopen.com Comments URL: https://news.ycombinator.com/item?id=47975785 Points: 254 # Comments: 13
📄原文 ·  💬HN讨论  · 05/01 23:15  · tvararu
12.
Article URL: https://shkspr.mobi/blog/2026/05/nhs-goes-to-war-against-open-source/ Comments URL: https://news.ycombinator.com/item?id=47973710 Points: 90 # Comments: 16
📄原文 ·  💬HN讨论  · 05/01 19:53  · edent
13.
Article URL: https://matduggan.com/if-i-could-make-my-own-github/ Comments URL: https://news.ycombinator.com/item?id=47971771 Points: 73 # Comments: 2
📄原文 ·  💬HN讨论  · 05/01 14:21  · vinhnx
Hacker News RSS 聚合 · Claude AI 自动翻译 · 如需取消订阅请联系管理员