frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

5k Restaurant Menus, Years 1880-1920

https://pudding.cool/2026/06/menu-collection/
221•xbryanx•4h ago•56 comments

I used Claude Code to get a second opinion on my MRI

https://antoine.fi/mri-analysis-using-claude-code-opus
119•engmarketer•2h ago•167 comments

Working around dragons with the Lemote Yeeloong laptop and OpenBSD

http://oldvcr.blogspot.com/2026/06/working-around-dragons-with-lemote.html
41•zdw•1h ago•4 comments

The Cost Yagni Was Never About – By Kent Beck

https://newsletter.kentbeck.com/p/the-cost-yagni-was-never-about
6•kiyanwang•15m ago•0 comments

Reflections on Software Engineering in the Age of AI

https://adiamond.me/2026/06/software-engineering-in-the-age-of-ai/
56•diamondap•2h ago•18 comments

Daisugi, the Japanese technique of growing trees out of other trees (2020)

https://www.openculture.com/2020/10/daisugi.html
51•MaysonL•2h ago•18 comments

Show HN: Zanagrams

https://zanagrams.com/
65•pompomsheep•3h ago•19 comments

The Boeing 747 Begins Its Final Descent

https://www.theatlantic.com/magazine/2026/07/boeing-747-retirement/687304/
40•dbl000•3d ago•31 comments

Examining circuit boards from the Space Shuttle's I/O Processor

https://www.righto.com/2026/06/space-shuttle-io-processor-boards.html
47•pwg•2h ago•8 comments

A way to exclude sensitive files issue still open for OpenAI Codex

https://github.com/openai/codex/issues/2847
142•pikseladam•6h ago•95 comments

The curious case of the disappearing Polish S (2015)

https://aresluna.org/the-curious-case-of-the-disappearing-polish-s/
176•colinprince•6h ago•44 comments

Show HN: DRM-Free Books

https://frequal.com/Perspectives/DrmFreeAuthors.html
15•TeaVMFan•1h ago•4 comments

Michigan bill would bar employers from requiring after-hours coms with workers

https://www.cbsnews.com/detroit/news/workplace-boundaries-act-employees-after-hours/
158•cebert•4h ago•96 comments

EU to legislate about Chat Control behind closed doors

https://www.patrick-breyer.de/en/double-threat-to-private-communications-undemocratic-chat-contro...
374•NeutralForest•4h ago•219 comments

Flock cameras track more than your license plate, and they're spreading fast

https://www.engadget.com/2203000/flock-cameras-recording-license-plate/
280•SanjayMehta•4h ago•190 comments

Marfa Public Radio Puts You to Sleep

https://www.marfapublicradio.org/podcast/marfa-public-radio-puts-you-to-sleep
363•reaperducer•16h ago•111 comments

Programmable Probabilistic Computer with 1M p-bits

https://arxiv.org/abs/2606.25313
15•rbanffy•2h ago•0 comments

California legislature agrees to upload driver's licenses to national database

https://papersplease.org/wp/2026/06/27/california-legislature-agrees-to-upload-drivers-licenses-t...
76•iamnothere•3h ago•28 comments

Do Babies Dream of Baby Sheep?

https://devz.cl/posts/do-babies-dream-of-electric-sheep/
87•DanielVZ•3d ago•26 comments

Build Yourself Flowers

https://vickiboykis.com/2026/04/20/build-yourself-flowers/
106•surprisetalk•3d ago•0 comments

DLL that was not present in memory despite not being formally unloaded

https://devblogs.microsoft.com/oldnewthing/20260625-00/?p=112467
103•ibobev•8h ago•37 comments

The MUMPS 76 Primer – anniversary edition

https://github.com/rochus-keller/MUMPS/blob/main/docs/MUMPS_Primer.adoc
49•Rochus•6h ago•23 comments

Google limits Meta's use of its Gemini AI models

https://www.cnbc.com/2026/06/28/google-limits-metas-use-of-its-gemini-ai-models-ft-reports.html
122•root-parent•5h ago•57 comments

Bringing Swift to the Apple ][

https://yeokhengmeng.com/2026/06/swift-on-apple-ii/
49•LucidLynx•3d ago•2 comments

Anonymous GitHub account mass-dropping undisclosed 0-days

https://github.com/bikini/exploitarium
914•binyu•1d ago•360 comments

Designing a Personal Pebble Watchface

https://www.jonashietala.se/blog/2026/06/26/designing_a_personal_pebble_watchface/
26•lawn•1d ago•5 comments

AMD Strix Halo RDMA Cluster Setup Guide

https://github.com/kyuz0/amd-strix-halo-vllm-toolboxes/blob/main/rdma_cluster/setup_guide.md
213•jakogut•18h ago•66 comments

Choosing a Public DNS Resolver

https://evilbit.de/dns-resolver-guide.html
259•pawal•20h ago•110 comments

Bashblog – a single bash script to create blogs

https://github.com/cfenollosa/bashblog
101•ludicrousdispla•13h ago•74 comments

The origins of the school system aimed to produce independent, critical thinkers (2024)

https://www.cbc.ca/radio/ideas/humboldt-education-system-bildung-1.7172093
88•pseudolus•5h ago•45 comments
Open in hackernews

The Fastest Way yet to Color Graphs

https://www.quantamagazine.org/the-fastest-way-yet-to-color-graphs-20250512/
62•GavCo•1y ago

Comments

tonyarkles•1y ago
In case you haven't looked at the article, this is looking specifically at the Edge Coloring problem and not the more commonly known Vertex Coloring problem. Vertex Coloring is NP-complete unfortunately.
erikvanoosten•1y ago
You can convert edge coloring problems into vertex coloring problems and vice versa through a simple O(n) procedure.
meindnoch•1y ago
Wrong. You can convert edge-coloring problems into vertex-coloring problems of the so-called line graph: https://en.m.wikipedia.org/wiki/Line_graph

But the opposite is not true, because not every graph is a line graph of some other graph.

erikvanoosten•1y ago
Indeed. Thanks, I stand corrected.
tonyarkles•1y ago
Hrm... right. It's been a while. And it looks like both Vertex Coloring and Edge Coloring are both NP-complete (because of the O(n) procedure you're talking about and the ability to reduce both problems down to 3-SAT). I've started looking closer at the actual paper to try to figure out what's going on here. Thanks for the reminder, I miss getting to regularly work on this stuff.

Edit: thanks sibling reply for pointing out that it's not a bidirectional transform.

mauricioc•1y ago
For the edge-coloring problem, the optimal number of colors needed to properly color the edges of G is always either Delta(G) (the maximum degree of G) or Delta(G) + 1, but deciding which one is the true optimum is an NP-complete problem.

Nevertheless, you can always properly edge-color a graph with Delta(G) + 1 colors. Finding such a coloring could in principle be slow, though: the original proof that Delta(G) + 1 colors is always doable amounted to a O(e(G) * v(G)) algorithm, where e(G) and v(G) denote the number of edges and vertices of G, respectively. This is polynomial, but nowhere near linear. What the paper in question shows is how, given any graph G, to find an edge coloring using Delta(G) + 1 colors in O(e(G) * log(Delta(G))) time, which is linear time if the maximum degree is a constant.

Syzygies•1y ago
Yes. The article ran through this point as follows:

"In 1964, a mathematician named Vadim Vizing proved a shocking result: No matter how large a graph is, it’s easy to figure out how many colors you’ll need to color it. Simply look for the maximum number of lines (or edges) connected to a single point (or vertex), and add 1."

I keep wondering why I ever read Quanta Magazine. It takes a pretty generous reading of "need" to make this a correct statement.

JohnKemeny•1y ago
phkahler•1y ago
Is this going to lead to faster compile times? Faster register allocation...
john-h-k•1y ago
Very few compilers actually use vertex coloring for register allocation
isaacimagine•1y ago
Totally. The hard part isn't coloring (you can use simple heuristics to get a decent register assignment), rather, it's figuring out which registers to spill (don't spill registers in hot loops! and a million other things!).
NooneAtAll3•1y ago
and this post isn't even about vertex coloring
DannyBee•1y ago
No.

In SSA, the graphs are chordal, so were already easily colorable (relatively).

Outside of SSA, this is not true, but the coloring is still not the hard part, it's the easy part.

Not really. Coloring a graph is almost always talking about proper coloring, meaning that things that objects that are related receive different colors.

If you read the introduction, you'll also read that the goal is to "color each of your lines and require that for every point, no two lines connected to it have the same color."

Ps. "How many colors a graph needs" is a very well established term in computer science and graph theory.

mockerell•1y ago
I think the comment referred to the phrase „a graph needs X (colors or whatever)“. For me, this can be read two ways: 1. „a graph always needs at least X colors“ or 2. „a graph always needs at most X colors“.

Personally, I would interpret this as option 1 (and so did the comment above I assume). In that case, the statement is wrong. But I’d prefer to specify „at most/ at least“ anyways.

Or even better, use actual vocabulary. „For every graph there exists a coloring with X colors.“ or „any graph can be coloured using X colors“.

PS: I also agree with the sentiment about quanta magazine. It’s hard to get some actual information from their articles if you know the topic.

JohnKemeny•1y ago
What about this statement:

No matter how large a car is, it is easy to figure out how much money you'll need to buy it. Simply look at the price tag.

(From: No matter how large a graph is, it’s easy to figure out how many colors you’ll need to color it. Simply look for the maximum ...)

mauricioc•1y ago
Parent's point is that sometimes (but not always) the store is perfectly fine selling you a car for $1 less than what the "price tag" of Delta(G)+1 dollars asks for, so "need" is a bit inaccurate.