frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Next-Concept Modeling: Fast, Parallel Coarse-to-Fine Text Generation

https://arxiv.org/abs/2610.14162
10•theanonymousone•45m ago•0 comments

KetchUp – Open-source SketchUp alternative built with Rust and WebGPU

https://ketchup3d.github.io/app/
428•dcoulmbe•9h ago•119 comments

Unlocking any car from X brand in most of the world

https://shubs.io/unlocking-any-car-from-x-brand-in-most-of-the-world/
279•infosecau•7h ago•96 comments

I'm not convinced the AI bubble exists

https://matteoraso.github.io/im-not-convinced-the-ai-bubble-exists.html#im-not-convinced-the-ai-b...
219•matteoraso•8h ago•310 comments

Chimera Vocal Synth

https://chimera-vocal-synth.vercel.app/
183•nmstoker•9h ago•25 comments

Declarative Dragging

https://declarative-dragging.github.io/
499•smusamashah•4d ago•63 comments

Outlook.com is rejecting email from domains without DMARC

https://mailroute.net/blog/outlook-rejecting-email-without-dmarc
374•xmddmx•12h ago•264 comments

Dux: Free, open-source Wayland desktop shell with file manager and theming

https://duxlabs.dev/
265•indigodaddy•12h ago•86 comments

Ask HN: What are you working on? (November 2026)

198•david927•10h ago•665 comments

Nvidia CEO Jensen Huang's letter to staff about affair

https://nvidianews.nvidia.com/news/a-message-to-our-company
587•karimf•9h ago•607 comments

Ur-Nammu Founder of the Sumerian Renaissance

https://www.worldhistory.org/Ur-Nammu/
16•Bluestein•1d ago•0 comments

A Critique of GPUI

https://blog.zortax.de/posts/a-critique-of-gpui
79•ByteAtATime•4h ago•46 comments

Show HN: Flide: Make Jev-like decision models up to 9.5x faster

https://github.com/OmniJev/Flide
15•unikcc•3h ago•1 comments

RIP, Harvest

https://aphyr.com/posts/427-rip-harvest
315•zdw•6h ago•91 comments

Quasi-Logarithmic Kitchen Timer

https://blog.coredump.cx/p/quasi-logarithmic-kitchen-timer
9•surprisetalk•4d ago•2 comments

The Qlobe: Rotating Quine (2010)

http://mamememo.blogspot.com/2010/09/qlobe.html
22•niceguitars•4h ago•0 comments

Branching Beyond Leonardo: The Evolution of Tree Architecture Theory

https://blue-continuum.com/branching-beyond-leonardo
16•dnetesn•2d ago•0 comments

SultanC – an Arabic-first systems programming language

https://github.com/sultan-language/sultanc
7•supax•2d ago•0 comments

Llama-modchip: 284B DeepSeek on 64GB RAM, no GPU

https://github.com/synchopate/llama-modchip
412•joshcsimmons•21h ago•185 comments

Goldman Sachs is pulling Claude Code from its bankers and traders

https://www.thestateofai.com/news/goldman-sachs-claude-code-traders-bankers
738•TheWiggles•13h ago•399 comments

When a language's creator and its owners strongly disagree [pdf]

https://isocpp.org/files/papers/P4454R0.pdf
116•acossta•8h ago•110 comments

The Web Is More Than Enough, by Paul Ford

https://ftrain.com/aboard-the-web-is-more-than-enough
127•edward•12h ago•74 comments

Writing as a thinking tool

http://muratbuffalo.blogspot.com/2026/11/writing-as-thinking-tool.html
343•jruohonen•21h ago•87 comments

Show HN: JavaScript web apps with WASM layout and GPU rendering in 280 KB

https://github.com/rkaehn/uniform
26•rkaehn•2d ago•11 comments

Show HN: My compact, bio inspired distributed edge detection algorithm

https://github.com/RenderBear/haci
12•RenderBear•4d ago•0 comments

Is Opus 5.5 nerfed? Thinking patterns changed on November 3

https://twitter.com/shanemelaugh/status/2119192075505893695
15•rzk•1h ago•7 comments

How I Fight AI Brain Fry

https://sergeykuhne.com/blog/fighting-ai-brain-fry
228•kyunez•12h ago•164 comments

Goodbye Claude, hello Pi

https://caleb.software/posts/claude-to-pi.html
754•karagenit•1d ago•459 comments

Air holes turn silicon wafers into flat UV focusing mirrors for compact optics

https://phys.org/news/2026-11-air-holes-silicon-wafers-flat.html
50•bookofjoe•1d ago•6 comments

Playing with the STM32MP2

https://serd.es/2026/11/08/playing-with-stm32mp2.html
59•dverlaeckt80•13h ago•33 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.