frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Open Social Web Alliance

https://osw-alliance.net/en/
83•doener•1h ago•64 comments

Show HN: I built a game where you are an LLM's subagent

https://github.com/gulivan/worker755
116•ivantgam•3h ago•28 comments

Toyota, Nissan, and Honda to standardize parts to lower costs

https://www.caranddriver.com/news/a74490092/toyota-nissan-honda-standardize-parts-lower-costs/
937•zdw•13h ago•551 comments

Pill to treat pancreatic cancer hailed as 'biggest breakthrough in decades'

https://www.theguardian.com/society/2026/nov/20/pill-pancreatic-cancer-breakthrough-daraxonrasib
1240•rafaelc•1d ago•267 comments

A Better Vocabulary for Testing

https://alperenkeles.com/posts/vocab-for-testing/
32•alpaylan•18h ago•7 comments

Europe weakens chemical rules as science links them to 'lifestyle diseases'

https://www.lemonde.fr/en/opinion/article/2026/11/22/as-science-increasingly-shows-the-role-chemi...
54•atmosx•1h ago•15 comments

Lean verification of the Riemann Hypothesis

https://leanprover-community.github.io/blog/posts/riemann-hypothesis/
1156•g-b-r•1d ago•959 comments

Ask HN: Tips for transitioning from web development to embedded/firmware?

32•llmblockchain•3d ago•24 comments

Self-hosted library branch over public web OPDS

https://joinmayberry.com/
84•philips•2d ago•24 comments

Sandwich Simulator

https://stulle.app/
446•subdomain•17h ago•153 comments

What Makes UltraSMR Different?

https://blog.westerndigital.com/what-is-ultrasmr-technology/
8•bluedino•2d ago•3 comments

The Where's Waldo of the 1500s

https://blog.alexbeals.com/posts/il-civetta
23•speckx•3d ago•5 comments

Muru – AI-assisted Rust server for Python apps by mod_WSGI's creator

https://simonwillison.net/2026/Nov/21/muru/
47•joshcsimmons•7h ago•8 comments

Inkling-2-Mini in 5.4 GB Memory

https://github.com/ShinMegamiBoson/lookatmyquant
533•k__•23h ago•128 comments

Detonating a pile of lead azide

https://www.science.org/content/blog-post/detonating-huge-pile-lead-azide-really
672•beginning_end•1d ago•409 comments

87% of the Anthropic power will come from gas and 11% from coal in 2028

https://betterdatacenterproject.com/2026/11/16/how-ai-is-powered-a-breakdown-of-byop-and-grid-power/
485•happosai•8h ago•577 comments

Backblaze customers worried of personal data sale/sharing after policy update

https://www.neowin.net/news/backblaze-customers-worried-of-personal-data-salesharing-after-policy...
30•cube00•1h ago•10 comments

I joined the NTP Pool, but not with my Stratum 1 Pi

https://www.jeffgeerling.com/blog/2026/i-joined-the-ntp-pool/
5•fortran77•1h ago•0 comments

Data Processing Incidents on Inference Providers

https://openrouter.ai/blog/announcements/data-processing-incidents-on-inference-providers/
246•sdko•14h ago•85 comments

Fast-Anything: Don't rewrite it in Rust. Rewrite the 5% that's slow

https://github.com/EL4CTEO/fast-anything
122•BaselAshraf81•12h ago•92 comments

Notes on the discrete Fourier transform (DFT)

https://eli.thegreenplace.net/2026/notes-on-the-discrete-fourier-transform-dft/
72•kouosi•10h ago•9 comments

Getting the mind to steer the body to steer you

https://notnottalmud.substack.com/p/getting-the-mind-to-steer-the-body
363•jger15•1d ago•132 comments

My monitor was cutting my download speed by 75%

https://blog.tymscar.com/posts/studiodisplayethernet/
657•soheilpro•1d ago•303 comments

Field Mice on Drugs

https://ambrook.com/offrange/livestock/field-mice-on-drugs
21•surprisetalk•2d ago•3 comments

PcapAnalyzer – self-hosted pcap analyzer with 27 problem detectors

https://github.com/sebaandrada-cell/PcapAnalyzer
148•sebaandrada•18h ago•19 comments

The Mythology of Conscious AI

https://www.noemamag.com/the-mythology-of-conscious-ai/
128•Anon84•14h ago•338 comments

Ask HN: Are the trades a safe career transition?

9•Rd6n6•1h ago•4 comments

Advice for the next 100 Rust GUIs

https://linebender.org/blog/next-100-guis/
235•raphlinus•19h ago•123 comments

Pandex – Official European Law for AI Agents, over MCP

https://www.pandex.io
129•vasie•20h ago•31 comments

LLMs can read and write executables byte by byte from a hex dump

https://sgiannopoulos.github.io/blog/machine-code-programming/
301•fortran77•4d ago•172 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.