frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Doomsday: Friday, 13 November, A.D. 2026 (1960)

https://www.science.org/doi/10.1126/science.132.3436.1291
84•voxleone•57m ago•28 comments

Jensen Huang resigns

https://apnews.com/article/nvidia-megaspeed-china-singapore-huang-5403f152a601cf82ce939f1d24fffa0f
3687•lldb•23h ago•3218 comments

Elevated errors on claude.ai, Claude Code, and platform.claude.com

https://status.claude.com/incidents/nn11wk485zfn
287•__vivek•2h ago•234 comments

IceWM

https://ice-wm.org/
245•inatreecrown2•8h ago•117 comments

Rust 1.100

https://blog.rust-lang.org/2026/11/12/Rust-1.100.0/
743•mbStavola•18h ago•277 comments

Brave Search API now accepts agentic payments via the x402 protocol

https://brave.com/blog/search-api-agentic-payments/
161•sjdh76•9h ago•88 comments

Show HN: My $300 embroidery machine needed a subscription, so I built my own app

https://github.com/simpsoka/zigzag
586•simpsoka•20h ago•198 comments

Gemini 4 Hydrogen and Orchestrator

https://antigravity.google/blog/gemini-4-hydrogen-in-google-antigravity/
441•jonbaer•18h ago•130 comments

Former Nvidia CEO Huang had a relationship with a second employee, sources say

https://www.reuters.com/technology/former-nvidia-ceo-huang-had-relationship-with-second-employee-...
328•jbredeche•17h ago•364 comments

Dwarf planet candidate appears which takes roughly 280 years to orbit our sun

https://www.smithsonianmag.com/smart-news/astronomers-found-a-mysterious-object-orbiting-far-beyo...
332•cybermango•18h ago•140 comments

Edge0-145B: Frontier AI Capabilities on Your Own Computer

https://edge0.ai/blog/introducing-edge0-145b-frontier-ai-capabilities-on-your-own-computer
283•sroussey•14h ago•83 comments

The Dawn of the Data Intelligence Engineer

https://motherduck.com/blog/the-data-intelligence-engineer/
70•jonbaer•3h ago•49 comments

Is there a 'right amount' of AI?

https://coyotetracks.org/blog/right-amount-of-ai/
16•milali•3h ago•18 comments

Service degradation on Microsoft 365

https://status.cloud.microsoft/
1007•dkpk•18h ago•848 comments

I'm making LLMs work on small and old devices

https://github.com/hyperionaidev/smolmaxxing/
402•mrashad74•21h ago•148 comments

Foundation Models framework

https://developer.apple.com/foundation-models-framework/
226•kermatt•15h ago•32 comments

Claude Is Down

https://status.claude.com/history
146•cornfieldlabs•2h ago•125 comments

Switcher (2004)

https://folklore.org/Switcher.html
109•sammatilda•9h ago•34 comments

Turning a 22-year-old Postgres type-confusion primitive into RCE

https://mehmetince.net/part-3-6-how-i-ended-up-turning-a-22-year-old-postgresql-type-confusion-pr...
211•ozirus•18h ago•39 comments

Abandoned Quake 4 expansion finished by modders and now playable

https://www.moddb.com/mods/openq4/downloads/openq4-0141-windows-x64
282•klaussilveira•22h ago•105 comments

Global Microsoft Outage

https://www.cnn.com/2026/11/12/business/live-news/microsoft-global-outage-intl-hnk
194•TechTechTech•6h ago•110 comments

Anthropic IPO

https://ipo.anthropic.com/us/
960•josephljohnston•1d ago•874 comments

Show HN: AgentRun – open-source, Self-improving Managed Agents

https://github.com/Parcha-ai/agentrun/blob/main/README.md
119•miguelrios•18h ago•29 comments

Relax: JIT compiler for Rust to reduce build times

https://makepad.github.io/relax/
169•adamnemecek•1d ago•87 comments

Microsoft Outlook/365 still down after 12 hours

https://twitter.com/MSFT365Status/status/2121079061774491735
385•player85•7h ago•268 comments

Sift: LSP, Lint, Format Lisp, Scheme and Emacs Lisp

https://github.com/jjba23/sift
69•jjba23•1d ago•9 comments

Talking Zen 6 with Mike Clark at AMD In-Depth

https://chipsandcheese.com/p/talking-zen-6-with-mike-clark-at
225•dverlaeckt80•22h ago•7 comments

Nvidia employees petition to bring back Jensen Huang

https://www.wired.com/story/nvidia-employees-petition-for-jensen-huangs-return/
675•lavendermon•10h ago•515 comments

Gemini 4 Hydrogen

https://blog.google/innovation-and-ai/models-and-research/gemini-models/introducing-gemini-4-hydr...
541•dvaplima•19h ago•339 comments

Show HN: Kapso – Iterative learning from enterprise data

49•alirezamshi•19h ago•11 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.