frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

DeepSeek: DeepSeek v4.1 Flash 1017

https://openrouter.ai/deepseek/deepseek-v4.1-flash-1017
138•theanonymousone•1h ago•15 comments

"Tame" boar and deer are instinctively adapting to the wolf in the Netherlands

https://nos.nl/video/2635315-wildcamera-s-tonen-hoe-zwijnen-en-herten-zich-aanpassen-aan-de-wolf
25•felipevb•1h ago•29 comments

Ultramarine 1 Flash

https://www.paperinstruments.com/ultramarine
252•i_rush_carriers•1d ago•71 comments

Is MCP becoming the common foundation of smart, decentralised search?

https://contextetech.com/en/articles/mcp-protocol-smart-decentralised-search
11•contextetech•1h ago•7 comments

Tesla Roadster

https://www.tesla.com/roadster
1441•shekhar101•1d ago•2523 comments

Show HN: Llmspeed – feel how fast a local LLM runs before you buy the hardware

https://llmspeed.dev/
79•albinstman•5h ago•28 comments

DeepSeek-v4.1-Flash-1017

https://huggingface.co/deepseek-ai/DeepSeek-V4.1-Flash-1017
159•theykk•2h ago•64 comments

Intuitive concurrent programming in any language

https://www.lf-lang.org/
47•mpweiher•1d ago•9 comments

Llama.cpp on a jailbroken PS5: run any GGUF model natively on the console

https://github.com/cobanov/PS5LM
293•Anon84•15h ago•73 comments

Tell HN: Remember to migrate away from .name domain

44•nikanj•2d ago•23 comments

Recipes Are Moving from Maven Central to the Code Genome Project

https://docs.openrewrite.org/reference/latest-versions-of-every-openrewrite-module
9•javahippie•1d ago•2 comments

You could have invented transformers from memory

https://alexwang.ai/posts/associative-memory/
312•speckx•15h ago•72 comments

Claude reveals ECDSA curve origins

https://www.anthropic.com/research/ecdsa-curve-origins
876•ahlCVA•15h ago•326 comments

FLUX 3 Image Klein

https://bfl.ai/blog/flux-3-image-klein
167•gmays•14h ago•47 comments

0/1 Knapsack Problem in PyTorch

https://jedrzej.maczan.pl/2025_11_21_dp_knapsack_sliding_hirschberg
26•yu3zhou4•2d ago•1 comments

Apple ML Research: Muse Spark Open with MLX on Mac Studio

https://machinelearning.apple.com/research/mlx-distributed-inference
321•antipaul•20h ago•161 comments

eBay Restricts Listings of Radio Equipment, but Exempts Ham-Band-Only Gear

https://www.arrl.org/arrlletterissue?issue=2026-10-15#eBay-Restricts-Listings-of-Radio-Equipment_...
224•7402•16h ago•199 comments

Butlerian Jihad

https://dune.fandom.com/wiki/Butlerian_Jihad
234•wetwater•8h ago•126 comments

Designing more efficient quantum circuits with Claude

https://www.anthropic.com/research/designing-efficient-quantum-circuits
143•pretext•16h ago•32 comments

JPEG XL vs. AVIF for web use-cases

https://jakearchibald.com/2026/jpeg-xl-vs-avif/
264•farlight•18h ago•183 comments

I built the RealWorld app in Lean 4

https://leangineer.com/blog/realworld-in-lean/
60•saviorand•2d ago•5 comments

A story of WiFi secrets, UART lockdowns and a damaged flash memory chip

https://adepts.of0x.cc/eufy-homestation2-firmware/
47•michidk•18h ago•3 comments

Flexport Is Hiring a Biz Ops Leader in Office of CEO

https://www.flexport.com/company/careers/
1•thedogeye•9h ago

Monte-Carlo Simulations

https://eli.thegreenplace.net/2026/monte-carlo-simulations/
124•ibobev•3d ago•22 comments

90% of US working hours are spent on tasks not covered well by AI benchmarks

https://www.mercor.com/research/labor-index/benchmark-map/
508•speckx•17h ago•430 comments

Show HN: I got tired of btop not seeing my Mac's chip, so I built siltop

https://github.com/CLoaKY233/siltop
6•cloaky233•3h ago•3 comments

Nine-Inch Snails

https://www.theatlantic.com/science/2026/10/giant-african-snails-florida-invasion/688850/
69•zdw•12h ago•34 comments

How the Claude Code team does code review

https://claude.dev/blog/solving-code-review-at-anthropic/
351•pretext•15h ago•330 comments

Show HN: Gemini 4 Argon plays StarCraft

https://starskirmish.com/bench/v0-2/
224•__cayenne__•20h ago•101 comments

Wireless magnetic millirobots that deliver medicine inside the beating heart

https://hub.jhu.edu/2026/10/12/magnetic-millirobots-cardiac-treatment/
97•giuliomagnifico•3d ago•16 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.