frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

OpenAI Submits S-1 Draft to SEC

https://openai.com/index/openai-submits-confidential-s-1/
224•hackerBanana•2h ago•135 comments

Surveillance Is Not Safety: A statement on the UK's latest threat to privacy [pdf]

https://signal.org/blog/pdfs/2026-06-08-uk-surveillance-is-not-safety.pdf
332•g0xA52A2A•4h ago•102 comments

Siri AI

https://www.apple.com/apple-intelligence/
356•0xedb•5h ago•292 comments

Show HN: Performative-UI – A react component library of design tropes

https://vorpus.github.io/performativeUI/
728•lizhang•9h ago•147 comments

MiMo-v2.5-Pro-UltraSpeed: 1T model with 1000 tokens per second

https://mimo.xiaomi.com/blog/mimo-tilert-1000tps
474•gainsurier•8h ago•324 comments

Apple Core AI Framework

https://developer.apple.com/documentation/coreai/
155•hmokiguess•5h ago•22 comments

Looking Forward to Postgres 19: Query Hints

https://www.pgedge.com/blog/looking-forward-to-postgres-19-query-hints
26•jjgreen•3d ago•2 comments

EU-banned pesticides found in rice, tea and spices

https://www.foodwatch.org/en/eu-banned-pesticides-found-in-rice-tea-and-spices
211•john-titor•8h ago•79 comments

Anti-social: It's fads, not friends, which now dominate social media feeds

https://www.bbc.com/worklife/article/20260520-how-social-media-ceased-to-be-social
526•1vuio0pswjnm7•12h ago•394 comments

Show HN: Gitdot – a better GitHub. Open-source, written in Rust

https://gitdot.io/
114•baepaul•7h ago•108 comments

Why are cells small?

https://burrito.bio/essays/what-limits-a-cells-size
100•mailyk•4h ago•44 comments

xAI is looking more like a datacentre REIT than a frontier lab

https://martinalderson.com/posts/xais-new-rental-business/
365•martinald•8h ago•289 comments

Apple reveals new AI architecture built around Google Gemini models

https://www.macrumors.com/2026/06/08/apple-reveals-new-ai-architecture/
308•unclefuzzy•4h ago•292 comments

FrontierCode

https://cognition.ai/blog/frontier-code
73•streamer45•3h ago•16 comments

Ask HN: What are tools you have made for yourself since the advent of AI?

121•aryamaan•5h ago•221 comments

Doing Something That's Never Been Done Before

https://talglobus.com/p/doing-something-thats-never-been-done-before/
21•surprisetalk•3d ago•9 comments

Launch HN: Intuned (YC S22) – Build and run reliable browser automations as code

https://intunedhq.com
97•fkilaiwi•10h ago•44 comments

AI is slowing down

https://www.wheresyoured.at/ai-is-slowing-down/
353•crescit_eundo•8h ago•374 comments

Switzerland wil have a referendum to cap population at 10M

https://www.admin.ch/en/sustainability-initiative
222•napolux•4h ago•437 comments

Fooling Go's X.509 Certificate Verification

https://danielmangum.com/posts/fooling-go-x509-certificate-verification/
34•hasheddan•2d ago•17 comments

OCaml Onboarding: Introduction to the Dune build system

https://ocamlpro.com/blog/2025_07_29_ocaml_onboarding_introduction_to_dune/
139•andrewstetsenko•4d ago•17 comments

1worldflag: A blue dot on a transparent background

https://1worldflag.com/
163•davidbarker•22h ago•138 comments

Stop the Apple Music app from launching

https://lowtechguys.com/musicdecoy/
559•bobbiechen•7h ago•222 comments

The Cypherpunk Library

https://www.cypherpunkbooks.com
352•yu3zhou4•15h ago•94 comments

Show HN: Mach – A compiled systems language looking for contributions

https://github.com/octalide/mach
6•octalide•59m ago•1 comments

How much of Thermo Fisher's antibody data has been manipulated?

https://reeserichardson.blog/2026/05/28/how-much-of-thermo-fishers-antibody-data-has-been-manipul...
396•mhrmsn•17h ago•87 comments

Massachusetts bans sale of precise location data in new privacy rights bill

https://techcrunch.com/2026/06/08/massachusetts-votes-to-pass-new-privacy-rights-bill-that-bans-s...
236•01-_-•6h ago•37 comments

Using XDG-Compliant Config Files (2024)

https://wxwidgets.org/blog/2024/01/using-xdg-compliant-config-files/
34•ankitg12•4d ago•7 comments

Are you expected to run five Python type-checkers now?

https://pyrefly.org/blog/too-many-type-checkers/
132•ocamoss•11h ago•147 comments

Apple bets cheaper AI will woo small developers

https://techcrunch.com/2026/06/08/apple-bets-cheaper-ai-will-woo-small-developers/
7•jbernardo95•3h ago•2 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.