frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Why have papers by one of history's most famous physicists been retracted?

https://www.science.org/content/article/why-have-papers-one-history-s-most-famous-physicists-been...
47•adharmad•33m ago•12 comments

Incident CVE-2026-LGTM

https://nesbitt.io/2026/06/26/incident-report-cve-2026-lgtm.html
91•mooreds•1h ago•24 comments

Om Malik has died

https://om.co/2026/06/24/1966-2026/
1097•minimaxir•18h ago•130 comments

An entire Herculaneum scroll has been read for the first time

https://scrollprize.org/firstscroll
1470•verditelabs•22h ago•316 comments

The AI backlash is only getting started

https://www.economist.com/leaders/2026/06/25/the-ai-backlash-is-only-getting-started
43•andsoitis•1h ago•42 comments

Bipartite Matching Is in NC

https://scottaaronson.blog/?p=9851
62•amichail•3d ago•2 comments

Libre Barcode Project

https://graphicore.github.io/librebarcode/
224•luu•11h ago•36 comments

Ultrasound Imaging of the Brain

https://alephneuro.com/blog/ultrasound-brain
25•rossant•2h ago•7 comments

What happened after 2k people tried to hack my AI assistant

https://www.fernandoi.cl/posts/hackmyclaw/
265•cuchoi•12h ago•110 comments

Framework's 10G Ethernet module exposes USB-C's complexity

https://www.jeffgeerling.com/blog/2026/framework-10g-ethernet-module-usb-c-complexity/
247•Alupis•13h ago•135 comments

Show HN: WebBase-III – dBASE III rebuilt in the browser with its own interpreter

https://github.com/DDecoene/WebBaseIII
31•ddecoene•2d ago•8 comments

22-year-old Mozart's handwritten notebook unearthed in 'major discovery'

https://www.classicfm.com/composers/mozart/handwritten-notebook-discovered-major-paris/
142•thunderbong•5d ago•35 comments

FEXPRs vs. vtable: how LispE interpreter works

https://github.com/naver/lispe/wiki/2.7-FEXPR-vs.-vtable
15•birdculture•2d ago•4 comments

The 'papers, please' era of the internet will decimate your privacy

https://expression.fire.org/p/the-papers-please-era-of-the-internet
896•bilsbie•16h ago•440 comments

We all depend on open source. We will defend it together

https://akrites.org/letter/
355•dhruv3006•9h ago•168 comments

A game where you're an OS and have to manage processes, memory and I/O events

https://github.com/plbrault/youre-the-os
291•exploraz•3d ago•54 comments

The Garbage Collection Handbook: The Art of Automatic Memory Management (2nd Ed) (2023)

https://gchandbook.org/
192•teleforce•15h ago•39 comments

Oxide computer 3D rack guided tour

https://explorer.oxide.computer/
421•darthcloud•3d ago•173 comments

IBM debuts sub-1 nanometer chip technology

https://newsroom.ibm.com/2026-06-25-ibm-debuts-worlds-first-sub-1-nanometer-chip-technology
354•porridgeraisin•23h ago•191 comments

Hey Nico, you didn't vibe code your data room but stole it from Papermark

https://twitter.com/mfts0/status/2070080422482977095
476•mmunj•1d ago•192 comments

Show HN: OpenKnowledge – open source AI-first alternative to Obsidian/Notion

https://github.com/inkeep/open-knowledge
320•engomez•22h ago•155 comments

Show HN: Chess-Inspired Roguelike

https://princechazz.com
368•cowboy_henk•5d ago•120 comments

The best thing that has ever happened for multiplayer games

https://mas-bandwidth.com/the-best-thing-that-has-ever-happened-for-multiplayer-games/
22•gafferongames•4d ago•6 comments

Microbubbles in Medicine

https://worksinprogress.co/issue/microbubbles/
19•Jimmc414•4d ago•3 comments

Un-0: Generating Images with Coupled Oscillators

https://unconv.ai/blog/introducing-un-0-generating-images-with-coupled-oscillators/
171•babelfish•17h ago•41 comments

An oral history of Bank Python (2021)

https://calpaterson.com/bank-python.html
148•tosh•18h ago•57 comments

Apple raises prices of MacBooks, iPads

https://www.reuters.com/world/asia-pacific/apple-raises-prices-macbooks-ipads-memory-costs-skyroc...
777•virgildotcodes•1d ago•1139 comments

The Doorman's Fallacy in action

https://rozumem.xyz/posts/17
168•rozumem•18h ago•222 comments

OS9Map

https://yllan.org/software/OS9Map/
249•LaSombra•23h ago•49 comments

Zig's new bitCast semantics and LLVM back end improvements

https://ziglang.org/devlog/2026/#2026-06-25
259•kouosi•1d ago•128 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.