frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

AWS Acquires DuckDB

https://ducklabs.com/news/2026/08/26/ducklabs-to-join-aws
253•onderkalaci•55m ago•54 comments

Qwen3.8-Flash-Next: A New Architecture, Towards Ultimate Cost-Efficiency

https://qwen.ai/blog?id=qwen3.8-flash-next
128•tosh•1h ago•36 comments

RAG Is Simpler Than You Think

https://www.lighthousenewsletter.com/p/rag-is-simpler-than-you-think
224•j0selit0•5h ago•102 comments

Oldinsurancemaps.net is now a Charter Project

https://openstreetmap.us/news/2026/08/oim-charter-project/
117•altilunium•4h ago•19 comments

A curmudgeon tries a language server

https://entropicthoughts.com/curmudgeon-tries-language-server
22•crescit_eundo•1h ago•2 comments

XCancel and Nitter are receiving C&D letters from XCorp

206•mobilio•4h ago•75 comments

Meta reaches $16.68B settlement over social media harms to children

https://www.reuters.com/world/us/meta-settles-with-us-states-over-social-media-harms-2026-08-26/
41•bhouston•26m ago•14 comments

Z.ai confirms Ox Alpha is a new GLM-series model and will release its weights

https://www.bloomberg.com/news/articles/2026-08-26/china-s-z-ai-made-ox-alpha-stealth-model-that-...
260•garo-pro•3h ago•100 comments

Fake US thinktank set up and funded by Israel sought to game AI for propaganda

https://www.theguardian.com/world/2026/aug/26/fake-thinktank-israel-ai-propaganda
131•n1b0m•1h ago•14 comments

Proliferate (YC S25) Is Hiring

https://www.ycombinator.com/companies/proliferate/jobs/OgpCKYJ-founding-product-engineer
1•pablo24602•1h ago

Apple introduces M6 and M5 Ultra

https://www.apple.com/newsroom/2026/08/apple-introduces-m6-and-m5-ultra-for-a-big-leap-in-perform...
1233•interpol_p•1d ago•1180 comments

Beyond Recall and the Illusion of Competence

https://var0.xyz/posts/beyond-recall-and-the-illusion-of-competence.html
46•tuxie_•3h ago•15 comments

Stalking the Wily Hacker: 40 years later – Cliff Stoll [video]

https://www.youtube.com/watch?v=656058JxTM0
169•zoenolan•4d ago•50 comments

Value Classes Still Need Compiler Sympathy

https://johan-sjolen.github.io/post/compiler-sympathy/compiler-sympathy/
58•lichtenberger•4h ago•20 comments

FDA authorizes first wearable device that monitors ketone and blood sugar levels

https://www.fda.gov/news-events/press-announcements/fda-authorizes-first-wearable-device-continuo...
458•sunnynagra•18h ago•210 comments

OpenAI Jalapeño: Better than Nvidia Blackwell

https://newsletter.semianalysis.com/p/openai-jalapeno-better-than-nvidia
541•bmulholland•23h ago•340 comments

Queryable Executables

https://fzakaria.com/2026/08/24/actually-queryable-executables
260•rguiscard•13h ago•73 comments

New Mac Studio with M5 Max and M5 Ultra

https://www.apple.com/newsroom/2026/08/apple-introduces-new-mac-studio-with-m5-max-and-m5-ultra/
795•interpol_p•1d ago•527 comments

Harvest (IBM 7950): Supercomputer for cryptanalysis at the NSA in the Cold War

https://spectrum.ieee.org/cold-war-codebreaker-nsa-ibm
62•jnord•8h ago•16 comments

Omarchy development practices lead to predictable security issues

https://blog.happyfellow.dev/merchants-of-insecurity/
218•arn3n•1h ago•281 comments

Show HN: Buslens – where can I get to by bus? (UK)

https://rupertlinacre.com/buslens/
69•RobinL•6h ago•43 comments

Black hole singularity is a surface not a point

https://arxiv.org/abs/2608.21590
283•raattgift•20h ago•195 comments

New Mac mini, featuring M6 and M5 Pro

https://www.apple.com/newsroom/2026/08/apple-unveils-a-more-powerful-mac-mini-featuring-the-all-n...
520•runako•1d ago•324 comments

Maiao: Gerrit-style code review workflow for GitHub, GitLab, Gitea, others

https://github.com/runetes/maiao
100•zdw•15h ago•63 comments

Bill Gates: The turbulent AI era is here

https://www.gatesnotes.com/work/make-ai-work-for-everyone/reader/a-turbulent-ai-era-and-critical-...
81•ilamont•1h ago•108 comments

When str.lower() is a security vulnerability in Python

https://sethmlarson.dev/when-str-lower-is-a-security-vulnerability
156•rbanffy•17h ago•67 comments

Building a backyard office, the build and cost breakdown

https://www.imkylelambert.com/articles/building-a-backyard-office-the-build-and-cost-breakdown
386•surprisetalk•23h ago•236 comments

Nitter and XCancel receive cease and desist notices

https://github.com/zedeus/nitter/issues/1442
1053•Banditoz•20h ago•887 comments

Tooltips need a delay, and then they need to skip it

https://blog.master.dev/tooltips-need-a-delay-and-then-they-need-to-skip-it/
207•ibobev•21h ago•70 comments

Run OpenBSD on DigitalOcean for $4/month

https://nil.wallyjones.com/run-openbsd-on-digitalocean-for-4month/
187•speckx•20h ago•85 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.