frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

'VPNs are lawful technical tools,' says EU Court in landmark copyright ruling

https://remysharp.com/links/2026-07-23-35890312
295•speckx•1h ago•111 comments

RFC 8890 – The Internet is for End Users (2020)

https://mnot.net/blog/2020/for_the_users
38•notarobot123•1h ago•12 comments

Why Don't People Use Formal Methods? (2019)

https://www.hillelwayne.com/post/why-dont-people-use-formal-methods/
56•Thom2503•2h ago•37 comments

Launch HN: Prized (YC S26) – Let non-engineer staff build secure internal tools

https://prized.dev
19•marinoseliades•1h ago•7 comments

Ron Gilbert started production on Thimbleweed Park 2

https://www.grumpygamer.com/twp2_announce/
139•alberto-m•6h ago•55 comments

SDL_GPU minimal, single-header, high-performance 2D graphics painting library

https://github.com/n67094/sdl_gp
5•n67094•19m ago•0 comments

Gpiozero Flow

https://bennuttall.com/blog/2026/07/gpiozero-flow/
97•benn_88•4h ago•29 comments

Hacker Public Radio

https://hackerpublicradio.org/
7•bmacho•27m ago•0 comments

How Old Is Ann?

https://quuxplusone.github.io/blog/2026/07/29/how-old-is-ann/
38•ibobev•2h ago•38 comments

Trusted URLs via Cryptographic Signatures

https://blog.certisfy.com/2026/04/trusted-urls-via-cryptographic.html
3•Edmond•25m ago•0 comments

Carolina Cloud pays SOFR on unused prepaid credits

https://docs.carolinacloud.io/organizations/prepaid-interest/
54•bojangleslover•5h ago•39 comments

Mbodi AI (YC P25) Is Hiring Robotics/Research Engineers

https://www.ycombinator.com/companies/mbodi-ai/jobs
1•chitianhao•2h ago

Go LLM SDK for streaming, tool-calling AI backends (plus frontend React lib)

https://github.com/grafana/ai-sdk
25•matryer•3h ago•8 comments

Building a native C# implementation of CEL engine

https://bsid.io/writing/building-a-cel-engine-for-net
5•jackedEngineer•2d ago•0 comments

Why Is Everyone Trying to Build a Solid-State Battery?

https://www.construction-physics.com/p/why-is-everyone-trying-to-build-a
57•crescit_eundo•2h ago•59 comments

Are We Stuck with Lean?

https://mathoverflow.net/questions/513742/are-we-stuck-with-lean
26•jjgreen•3h ago•5 comments

Why DNA damage from smoking and UV rays cause cancer in some but not others

https://www.cam.ac.uk/research/news/study-reveals-why-dna-damage-from-smoking-and-uv-rays-may-cau...
5•gmays•41m ago•1 comments

The Lost Civic Life of Movie Rental Stores

https://thereader.mitpress.mit.edu/the-lost-civic-life-of-movie-rental-stores/
5•facundo_olano•45m ago•0 comments

3D Pinball for Windows (1995)

https://98.js.org/programs/pinball/space-cadet.html
26•mushstory•3h ago•9 comments

Show HN: I audited my AI leaderboard scale – every score dropped 6-15 points

https://agiranker.com/
4•baraklaniado•52m ago•1 comments

CosmosEscape: Taking over Every Database in Azure Cosmos DB

https://www.wiz.io/blog/cosmosescape-taking-over-every-database-in-azure-cosmos-db
20•uvuv•2h ago•6 comments

The Glass Famine

https://edconway.substack.com/p/the-glass-famine
60•baud147258•3d ago•30 comments

Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode

https://github.com/YoanWai/agent-manager
66•yoanwaidev•5h ago•47 comments

Google will expand age checks on Android worldwide till the end of the year

https://android-developers.googleblog.com/2026/07/google-play-age-signals-api-safer-experiences.html
217•dmantis•4h ago•245 comments

The Alice and Bob After Dinner Speech (1984)

https://hex.ooo/library/alicebob.html
8•kamma4434•3d ago•1 comments

LLM Honeypot

https://llm2human.pages.dev/
346•8thom•16h ago•96 comments

You can't solve computer use by ignoring the interface

https://steelmanlabs.com/blog/computer-use-is-far-from-solved
29•mpavlov•3h ago•4 comments

Azulejo

https://en.wikipedia.org/wiki/Azulejo
107•Amorymeltzer•1d ago•35 comments

The first watch featuring computer functions

https://by.seiko-design.com/140th/en/topic/58.html
55•stefanv•4d ago•24 comments

Europe's fires are just the start

https://economist.com/leaders/2026/07/28/europes-fires-are-just-the-start
74•andsoitis•1h ago•104 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.