frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Coffeehouses and the Rise of Science [pdf]

https://www.monirbounadi.com/Bounadi_JMP.pdf
42•Michelangelo11•1h ago•18 comments

Doing Show HN generates a ton of automated email pitches

https://petervandijck.com/post/pbrgs-ev0bc
33•petervandijck•1h ago•25 comments

How to make almost anything

https://pub.cba.mit.edu/863.26/site/
387•o4c•6h ago•73 comments

Universal XSS in uBlock Origin from website-driven element picker

https://iter.ca/post/ubo-uxss/
416•zaik•10h ago•120 comments

The Secret ThinkPad Powerbutton Code to Bring Dead Laptops Back to Life (2007)

https://masnick.com/posts/the-secret-thinkpad-powerbutton-code-to-bring-dead-laptops-back-to-life/
8•sammatilda•32m ago•0 comments

Researchers track whole body movement with just a smartwatch

https://news.cornell.edu/stories/2026/11/researchers-track-whole-body-movement-just-smartwatch
75•PaulHoule•2d ago•15 comments

Qwen4-Max

https://qwen.ai/blog?id=qwen4-max
604•ilreb•9h ago•255 comments

Old Bitly links are being hijacked

https://ransomnews.com/burger-king-tweet-bitly-link-hijack-2026/
312•hspeiser•14h ago•158 comments

What's Next for Nvidia?

https://steveblank.com/2026/11/15/whats-next-for-nvidia/
295•zdw•12h ago•373 comments

Exact Gradients Through a BRep Kernel

https://muni.works/research/vcad
15•ecto•2d ago•3 comments

I Can't Believe It Can Sort

https://yugen-tsuki.github.io/unbelievablesort.html
31•Muhammad523•2d ago•35 comments

Tor Project Issues Rapid-Response DoS-Defense Fix Amid Sustained DDoS Attack

https://forum.torproject.org/t/security-release-0-4-9-17/22454
170•aillia•11h ago•49 comments

Protomaps: Self-hosting map tiles has gotten cheap and easy

https://bruceroettgers.eu/blog/protomaps/
366•bcye•16h ago•62 comments

It's always DNS, so why are we running our own?

https://s2.dev/blog/dns-server
11•misker1•2h ago•6 comments

“…and the proof is checked in Lean”

https://xenaproject.wordpress.com/2026/11/12/and-the-proof-is-checked-in-lean/
45•matt_d•4h ago•15 comments

OOS – an open operating system for the Rigol Scopes

https://www.eevblog.com/forum/testgear/oos-an-open-operating-system-for-the-rigol-scopes/
6•qwezxcrty•2d ago•2 comments

Preserving 30 years of Salon journalism

https://blog.archive.org/2026/11/12/preserving-30-years-of-salon-journalism/
166•CharlesW•13h ago•40 comments

A short explainer on how El Niño works [video]

https://www.youtube.com/watch?v=7_JF3etiAv8
251•nharada•17h ago•129 comments

Handwriting, as a Font

https://ductus.sorenblank.com
324•coinfused•16h ago•60 comments

The Lasting Influence of John Berger

https://www.newyorker.com/magazine/2026/11/16/john-berger-a-life-tom-overton-book-review
31•prismatic•4d ago•0 comments

Do we still have to denormalize? Have your schema and search it too

https://www.paradedb.com/blog/joins
84•philippemnoel•2d ago•23 comments

Crows make decisions faster than we can

https://www.nytimes.com/2026/11/15/science/birdbrain-crows-birds-research-decision.html
252•gumby•18h ago•171 comments

Making Atuin sync 32x faster with packfiles

https://blog.atuin.sh/making-atuin-sync-32x-faster-with-packfiles/
22•ossusermivami•4d ago•8 comments

WebGL Flight Simulator with seed generated terrain

https://baron.by.dai.studio/
165•ranger_danger•15h ago•35 comments

Simple 8085 Computer

https://www.hackster.io/mit41301/simple-8085-computer-9fe156
51•AlexeyBrin•3d ago•4 comments

Winudf – DVD / BluRay driver for DOS, Windows 1.x – 3x / 95 / 98 / ME

https://github.com/ages2001/WINUDF
10•Oxodao•4h ago•0 comments

Artificial Intelligence for the Z80

https://www.dfsantos.com/en/libro-ia-z80
52•AlexeyBrin•2d ago•7 comments

A quest to create the perfect whiskey glass

https://www.nytimes.com/2026/11/13/dining/drinks/kurt-josef-zalto-whiskey-glass.html
70•Kaibeezy•2d ago•71 comments

Mini.nvim Is Now on Tangled

https://tangled.org/nvim-mini.org/mini.nvim
75•nerdypepper•12h ago•22 comments

Debian Becomes Unresponsive after 6.1.0-55 Kernel Update

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1154101
122•artooro•7h ago•45 comments
Open in hackernews

Finding a Bug in Chromium

https://bou.ke/blog/chromium-bug/
65•bouk•1y ago

Comments

rvz•1y ago
Great technical post, however:

> At Monumental we’ve building robots to automate construction, starting with masonry.

If you thought running to construction jobs was safe, well thanks to Monumental, it soon won't be.

The end goal is to achieve a 10% increase of global unemployment by the latest 2035 and 40% of employers anticipate reducing their workforce where AI can automate tasks by the 2030 deadline according to the WEF 2025 Future of Jobs report. [0]

Worse if earlier.

[0] https://www.weforum.org/publications/the-future-of-jobs-repo...

TheDong•1y ago
And according to OSHA, construction jobs account for more fatal injuries than any other job, so in a sense they're saving lives by reducing the number of dangerous jobs.

We've already managed to handle the desire to keep the sham of "jobs are a necessary part of life for everyone who isn't ultra-wealthy" going via Bullshit Jobs, we can keep inventing more Bullshit Jobs.

Heck, we probably both work Bullshit Jobs. Do we really need 20 different companies, all with thousands of employees, optimizing ad-impressions to make teenagers want to drink coke and buy nike shoes?

Do we really need 10 different "uber for pet-sitting your turtle" apps?

Each failed startup was, in reality, a large bag of bullshit jobs that transferred money from the VCs to bullshit-job workers, who's to say those people couldn't be ex construction workers?

Cthulhu_•1y ago
Given the author's name, he's Dutch which does use a lot of brick in their houses... for decoration, it's concrete blocks with prefab brick facades for at least two decades now, built by robots. See for example https://www.bouwtotaal.nl/2021/10/prefab-gevelelementen-voor...

The demand for housing and thus construction workers isn't going down any time soon; the Netherlands alone needs to build a million homes in the next decade and are running behind on that. Brick walls is just one task of many in a construction project, just like your JIRA or Github ticket is just one task of many in a software project.

bouk•1y ago
Prefab stone strips are used here and there but most brick facades are still built by hand on-site.

There's a huge shortage of workers, which is why we're working on this.

pjmlp•1y ago
Cooking and serving at tables also won't be an excape route, given that there are already kitchen and waitresses robots.

We are really going into a dystopian world, unless there is some event that disrupts the roadmap to drive everyone into unemployment, besides a few elite folks that get to profit from the robots.

The generations to come will have much more to worry about than climate, also note how all the ongoing wars, geopolitcs change back to cold war days, and AI race has made everyone forget about the planet.

Forcing us to use paper straws and wood cuttlery won't save us.

charcircuit•1y ago
My first guess would be that this early return is always happening after entering the bugged state. The one cleanup task could get stuck or not cleanup after itself properly.

    // Only one cleanup task is posted at a time.
    if (!HasDirtyJSFinalizationRegistries() || is_finalization_registry_cleanup_task_posted_) {
      return;
    }
https://source.chromium.org/chromium/chromium/src/+/main:v8/...
bouk•1y ago
Ah this makes a lot of sense, perhaps the posted flag doesn't get reset e.g. if this branch gets followed: https://source.chromium.org/chromium/chromium/src/+/main:v8/...
syg•1y ago
Yeah this is the bug. My bad, will fix.
donatj•1y ago
Hey! I too just filed my first Chromium bug[1]! They changed a behavior that broke opening new windows with tabs, and thus broke my advanced tab search extension Tabasco[2].

I was frankly impressed by the experience. They had me create a minimal extension illustrating the issue and were very quickly able automate a bisection that found its root, a security fix somewhat bluntly resolved. They've supposedly fixed the issue in an upcoming release I await with bated breath.

- [1] https://issues.chromium.org/issues/405283740

- [2] https://chromewebstore.google.com/detail/tabasco-advanced-ta...

tester756•1y ago
>FinalizationRegistry

>Avoid where possible

>Correct use of FinalizationRegistry takes careful thought, and it's best avoided if possible. It's also important to avoid relying on any specific behaviors not guaranteed by the specification. When, how, and whether garbage collection occurs is down to the implementation of any given JavaScript engine. Any behavior you observe in one engine may be different in another engine, in another version of the same engine, or even in a slightly different situation with the same version of the same engine. Garbage collection is a hard problem that JavaScript engine implementers are constantly refining and improving their solutions to.

Kinda tricky API

ketanhwr•1y ago
> A conforming JavaScript implementation, even one that does garbage collection, is not required to call cleanup callbacks.

Really looking forward to the "Explicit Resource Management" proposal[0] that sounds like a much better idea really.

[0]: https://github.com/tc39/proposal-explicit-resource-managemen...

panstromek•1y ago
Hm.. I would honestly try to avoid relying on finalization mechanism of a garbage collector like this. It sounds brittle from the start. Even without the bug, I can imagine you can get into a situation where some unused JS object holds a reference to a giant thing in wasm memory, but engine doesn't run the GC, because it technically doesn't know that, it only sees the little pointer object which seems small.

I think WASM had historically had some problem with freeing memory, so I'd probably rather rely on some pooling or arena with explicit memory size limit (for the whole allocated wasm memory).