frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

US FAA says it will phase out floppy disks from air traffic control by 2028

https://www.reuters.com/world/us/us-faa-says-it-will-phase-out-floppy-disks-air-traffic-control-b...
34•ChrisArchitect•13h ago•61 comments

Tesla to wind down Cybertruck production

https://www.nbcnews.com/tech/tech-news/tesla-wind-cybertruck-production-years-poor-sales-markets-...
283•PLenz•5h ago•480 comments

Gemini Omni 1.2 Flash

https://blog.google/innovation-and-ai/technology/developers-tools/introducing-gemini-omni-1-2-flash/
209•thisisauserid•4h ago•164 comments

Blender's UI and Runtime: Much Faster Than GPUI

https://github.com/ppmpreetham/BUI
544•ppmpreetham•10h ago•216 comments

Deus Ex

https://www.filfre.net/2026/11/deus-ex/
202•cybersoyuz•2h ago•92 comments

First steps in bare-metal programming using UEFI

https://kevinboone.me/efitest_index.html
29•LaSombra•1h ago•1 comments

Claude Code sends your email address to websites

https://github.com/anthropics/claude-code/issues/107757
1492•motoroco•19h ago•467 comments

UpCodes (YC S17) is hiring SDR's to sell AI compliance software

https://up.codes/careers?utm_source=HN
1•Old_Thrashbarg•49m ago

Rune: A native GPU-rendered Rust UI framework for macOS, Windows, Linux and web

https://github.com/anomalyco/rune
23•mik3y•1h ago•8 comments

Lippitt-Knoster in Practice (Field Notes for Managing Complex Projects)

https://sharedphysics.com/lippitt-knoster-in-practice-field-notes-for-managing-complex-projects/
28•goopthink•2h ago•1 comments

Zero Hour: Telling time was a matter of survival and strategy during WWI (2014)

https://www.laphamsquarterly.org/roundtable/zero-hour
51•NaOH•22h ago•1 comments

Scriptable GeoDNS: Leaving AWS for Bunny

https://vincent.bernat.ch/en/blog/2026-bunny-geodns
14•sshah03•1h ago•7 comments

Living beyond the limits of survival: wood ants trapped in a gigantic pitfall (2016)

https://jhr.pensoft.net/articles.php?id=9096
129•hitekker•7h ago•42 comments

MTG-I2 First Images

https://www.eumetsat.int/mtg-i2-first-images
32•N19PEDL2•3h ago•6 comments

Dutch 'idealist' bank ASN blocks non-Google Android, including GrapheneOS

https://github.com/PrivSec-dev/banking-apps-compat-report/issues/105
552•microtonal•8h ago•345 comments

Kugelblitz – Mac-Native Google Earth Alternative

https://apps.metaebene.me/en/kugelblitz
213•luoc•10h ago•54 comments

MS Paint Remote Code Execution Vulnerability

https://www.cve.org/CVERecord?id=CVE-2026-83844
683•kuberwastaken•21h ago•254 comments

From Linux to Wikipedia: How Volunteers Build the Internet

https://thereader.mitpress.mit.edu/from-linux-to-wikipedia-how-volunteers-build-the-internet/
246•jonbaer•13h ago•82 comments

Anthropic IPO valuation talks drop to $1.3T

https://epyhia.com/anthropic-ipo-valuation-talks-drop-to-1-3-trillion-as-major-investors
21•arbuge•31m ago•6 comments

We've built an open-source feature flag server for 11 years

https://github.com/Unleash/unleash
107•ivarconr•6h ago•67 comments

Ask HN: What in the world is taking Ubuntu so long?

116•linsomniac•2h ago•59 comments

University libraries are being swarmed by AI bots, putting public access at risk

https://www.cbc.ca/news/world/university-libraries-ai-data-scraping-bots-9.7408287
93•blakesterz•3h ago•46 comments

AI for scientific discovery: How researchers use Claude

https://www.anthropic.com/research/how-researchers-use-claude
62•ersinesen•8h ago•25 comments

Show HN: Agentic Identity Broker, OAuth Delegation for AI Agents

https://github.com/zalando-incubator/agentic-identity-broker
13•jbspeakr•2h ago•3 comments

Pwn.college

https://pwn.college/
271•tripdout•14h ago•43 comments

sshole

https://sshhole.com
2886•josemrb•1d ago•706 comments

Multiplayer tanks that demolish real buildings from OpenStreetMap

https://worldstrike.fun/
148•n4ze3m•9h ago•98 comments

The Hackintosh Reborn

https://www.naut.ca/blog/2026/11/05/the-hackintosh-reborn-with-ai/
385•rubatuga•22h ago•222 comments

Chomsky and the Two Cultures of Statistical Learning (2011)

https://www.norvig.com/chomsky.html
63•andsoitis•9h ago•39 comments

Window Sweaters

https://github.com/saragordic/window-sweaters
439•nickswalker•1d ago•127 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.