frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

GPT 5.6 Sol is the best "vision" model OpenAI ever released

https://blog.roboflow.com/openai-gpt-5-6/
17•plurby•59m ago•15 comments

Qwen 3.8 27B is excellent, but it defaults to overthinking things

https://simonwillison.net/2026/Aug/16/qwen-38-27b/
606•bilsbie•13h ago•292 comments

How Go detects struct copies with sync.noCopy

https://func25.dev/posts/go-sync-nocopy/
15•func25•4d ago•13 comments

On A.I. regulation and messaging

https://twitter.com/DarioAmodei/status/2088758816376807762
138•jacquesm•11h ago•254 comments

Mexico Crackdown on Coastal Development Underway

https://yucatanmagazine.com/mexico-crackdown-on-coastal-development/
7•untiledsource•58m ago•0 comments

Buyer cancels showing after Deflock shows two cameras utilized by the HOA

https://twitter.com/lydiakauppi/status/2089196932413452386
52•bilsbie•50m ago•32 comments

Show HN: Desktopcolors.com – A museum for solid background colors of classic OS

https://desktopcolors.com
54•vlowrian•5h ago•23 comments

Anthropic's 'watermark' text adulteration in Claude is a perversion of writing

https://daringfireball.net/2026/08/anthropics_watermark_text_adulteration_in_claude_is_a_perversi...
422•ropbear•15h ago•403 comments

A third world engineer responds to “RISC-V: They should have known better”

https://rvembedded.com/blog_post/12/
557•Narishma•20h ago•282 comments

Reticulum – Decentralized Mesh Network

https://reticulum.network/
160•sudo_cowsay•13h ago•56 comments

Claude: System Prompts

https://platform.claude.com/docs/en/release-notes/system-prompts
695•tosh•1d ago•268 comments

The Mysterious Syndrome Destroying Endurance Athletes

https://www.outsideonline.com/health/training-performance/running-empty/
36•cwwc•2d ago•27 comments

AGI-64 Brings Sierra Adventures to the Commodore 64

https://meanhamster.com/news/agi-64-brings-sierra-adventures-to-the-commodore-64
106•erickhill•11h ago•14 comments

Linear algebra done right

https://linear.axler.net/
122•the-mitr•7h ago•51 comments

Who Owns Commodore? The Retro PC Brand Still Exists, but a Lot Has Changed

https://www.bgr.com/2233625/who-owns-commodore-retro-brand/
9•theanonymousone•1h ago•0 comments

Rhombus 1.1 is now available

https://blog.racket-lang.org/2026/08/rhombus-v1.1.html
98•spdegabrielle•12h ago•30 comments

How do I permanently disable random Google Photos popup to backup photos? (2024)

https://support.google.com/photos/thread/256212140/how-do-i-permanently-disable-google-photos-pop...
159•dt3ft•3d ago•107 comments

Build a Stratum 1 PTP Grandmaster on a Budget

https://opscode.io/posts/ptp-grandmaster-cm4-sr1723u10/
25•malcolmfrazier•3d ago•6 comments

SIMD in the 90s: Programming Intel's Pentium MMX

https://pikuma.com/blog/programming-intel-pentium-mmx-simd
131•ibobev•4d ago•54 comments

Self hosted email continues to steeply decline

https://labs.ripe.net/author/artem-berezin/two-providers-a-stubborn-plateau-and-a-very-long-tail-...
69•minusf•2h ago•90 comments

Gakutensoku

https://en.wikipedia.org/wiki/Gakutensoku
46•benbreen•3d ago•7 comments

Applying a photosynthetic process to treat “dry eye”

https://www.science.org/content/blog-post/taking-tip-plants-eyes
55•gumby•12h ago•17 comments

The AI Credit Resale Economy

https://vectoral.com/blog/who-are-the-token-brokers
307•mlenhard•22h ago•123 comments

People are worried about America's solvency

https://www.ft.com/content/e04f286c-f5ed-46d1-8e3f-0bbe4cce4d3e
62•root-parent•1h ago•60 comments

Production-ready detection and response queries for osquery

https://github.com/chainguard-dev/osquery-defense-kit
19•ankitg12•4d ago•1 comments

David Sacks on X: Some thoughts on Dario's post

https://twitter.com/DavidSacks/status/2089227290769080656
11•bilsbie•33m ago•5 comments

Tell HN: Cloudflare silently injects its analytics when you switch nameservers

561•stagas•19h ago•167 comments

Protobuf has LSP support

https://buf.build/blog/protobuf-lsp
163•theanonymousone•18h ago•115 comments

MathCode, Mathematical Coding Agent

https://math-ai-org.github.io/mathcode/
108•homarp•18h ago•29 comments

Prolly: A content-addressed ordered map built on prolly trees

https://github.com/crabbuild/prolly
48•forhappy•12h ago•5 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.