frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Goldman Sachs Is Pulling Claude Code from Its Bankers and Traders

https://www.thestateofai.com/news/goldman-sachs-claude-code-traders-bankers
104•TheWiggles•53m ago•43 comments

Llama-modchip: 284B DeepSeek on 64GB RAM, no GPU

https://github.com/synchopate/llama-modchip
265•joshcsimmons•8h ago•85 comments

A Little Snitch for Windows

https://packethound.app/
28•BadBoyBubby•1h ago•12 comments

The Reconstruction of Torn Documents

https://www.bundesarchiv.de/en/stasi-records-archive/the-reconstruction-of-torn-documents/
56•jacquesm•2d ago•35 comments

Writing as a thinking tool

http://muratbuffalo.blogspot.com/2026/11/writing-as-thinking-tool.html
166•jruohonen•8h ago•52 comments

I'm not a fan of Deno's security model (2024)

https://goldstein.lol/posts/deno-security/
41•maxloh•4h ago•20 comments

Porting Android 16 to my blind mother's keypad phone

https://z1x.us/blog/four-hundred-bucks-of-e-waste
110•z1xus•4d ago•36 comments

Goodbye Claude, hello Pi

https://caleb.software/posts/claude-to-pi.html
589•karagenit•15h ago•383 comments

Show HN: Vegetable Gardening for Engineers

https://jrcpl.us/contrib/2020/gardening-for-engineers/
55•jrcplus•4d ago•14 comments

UK House of Lords to propose mandatory CSAM detection software on smartphones

https://observer.co.uk/news/national/article/fight-to-block-child-sexual-abuse-images-unites-peer...
27•iamnothere•3h ago•7 comments

JIT bitmap text rendering for microcontrollers

https://linebender.org/blog/jit-bitmap-text/
79•dmit•8h ago•14 comments

How to prove equations using diagrams, part 1

https://www.epatters.org/post/e-graphs-1/
33•frostbyte7•6h ago•3 comments

What I run on my $10 USD OpenStick homelab

https://blog.bosscher.ch/posts/openstick/
720•LaurensBER•1d ago•128 comments

A field guide to CAPTCHA types and how they break

https://github.com/vsmutok/FuckCaptcha
23•vasylsmutok•2h ago•5 comments

Claude Code's "Don't Ask Again" exposes passwords in 1,122 public GitHub files

https://apiiro.com/blog/coding-agents-leaking-secrets-github-dont-ask-again
516•shmulc•22h ago•378 comments

Clj.rs – a Clojure dialect implemented in Rust

https://clj.rs/
133•simonpure•4d ago•49 comments

Silicon Valley Promises AI Will Cure Disease. Drugmaker CEOs Aren't Buying It

https://www.wsj.com/tech/ai/silicon-valley-promises-ai-will-cure-disease-drugmaker-ceos-arent-buy...
9•zzzeek•26m ago•6 comments

Agent memory needs its OpenTelemetry moment

https://www.lorekit.io/blog/open-agent-memory-format
141•mthines•10h ago•97 comments

Ads in Popular Apps Give Police a Powerful Tool to Spy on Users

https://www.bloomberg.com/features/2026-police-phone-tracking-advertising-tech/
31•mgh2•1h ago•1 comments

Petered

https://aworkinglibrary.com/writing/petered
134•adrianhoward•8h ago•83 comments

Declarative Dragging

https://declarative-dragging.github.io/
7•smusamashah•4d ago•0 comments

The Gordon Gekko effect: The role of culture in the financial industry (2016) [pdf]

https://www.newyorkfed.org/medialibrary/media/research/epr/2016/epr_2016_gordon-gekko-effect_lo.pdf
73•tylerdane•1d ago•48 comments

Person of Interest

https://krthr.co/person-of-interest/
252•krthr•7h ago•168 comments

Tasfer: a text editor drawn on a 2D canvas

https://www.hamza.se/blog/tasfer
75•hamza512b•4d ago•49 comments

Finding Xanadu: Inside a JRPG classic translation 15 years in the making

https://readonlymemo.com/legend-of-xanadu-pc-engine-fan-translation-interview-making-of/
62•speckx•3d ago•13 comments

Uranium cubes reveal why the German nuclear project failed

https://arstechnica.com/science/2026/11/uranium-cubes-reveal-why-the-german-nuclear-project-failed/
198•rbanffy•3d ago•136 comments

Every Mac comes with an (undocumented) family member classifier

https://8rank.ai/game/apple-intelligence-personal-knowledge-graph
821•infwhispers•1d ago•436 comments

Every Windows 11 app should kill Electron, and Discord just showed why

https://www.windowslatest.com/2026/11/06/every-windows-11-app-should-kill-electron-and-discord-ju...
426•thunderbong•1d ago•436 comments

Making any integer with four 2s (2025)

https://eli.thegreenplace.net/2025/making-any-integer-with-four-2s/
190•germanrabbit•20h ago•51 comments

MaxxBench – "Nice DeepSWE score. But is it true?"

https://maxxbench.unlap.ai/research/why-maxxbench/
372•antiuniverse•1d ago•101 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.