frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Claude Opus 4.7

https://www.anthropic.com/news/claude-opus-4-7
1358•meetpateltech•9h ago•983 comments

Codex for almost everything

https://openai.com/index/codex-for-almost-everything/
612•mikeevans•6h ago•345 comments

A Better R Programming Experience Thanks to Tree-sitter

https://ropensci.org/blog/2026/04/02/tree-sitter-overview/
52•sebg•2h ago•1 comments

Guy builds AI driven hardware hacker arm from duct tape, old cam and CNC machine

https://github.com/gainsec/autoprober
49•scaredpelican•1h ago•9 comments

Official Clojure Documentary page with Video, Shownotes, and Links

https://clojure.org/about/documentary
66•adityaathalye•3h ago•16 comments

Android CLI: Build Android apps 3x faster using any agent

https://android-developers.googleblog.com/2026/04/build-android-apps-3x-faster-using-any-agent.html
79•ingve•4h ago•24 comments

Qwen3.6-35B-A3B: Agentic coding power, now open to all

https://qwen.ai/blog?id=qwen3.6-35b-a3b
846•cmitsakis•9h ago•400 comments

Show HN: Marky – A lightweight Markdown viewer for agentic coding

https://github.com/GRVYDEV/marky
23•GRVYDEV•7h ago•5 comments

Qwen3.6-35B-A3B on my laptop drew me a better pelican than Claude Opus 4.7

https://simonwillison.net/2026/Apr/16/qwen-beats-opus/
250•simonw•5h ago•59 comments

Cloudflare's AI Platform: an inference layer designed for agents

https://blog.cloudflare.com/ai-platform/
223•nikitoci•10h ago•55 comments

Join Akkari's Founding Team (YC P26) as an Engineer

1•michael_moore•2h ago

Launch HN: Kampala (YC W26) – Reverse-Engineer Apps into APIs

https://www.zatanna.ai/kampala
63•alexblackwell_•8h ago•59 comments

The future of everything is lies, I guess: Where do we go from here?

https://aphyr.com/posts/420-the-future-of-everything-is-lies-i-guess-where-do-we-go-from-here
463•aphyr•9h ago•509 comments

New unsealed records reveal Amazon's price-fixing tactics, California AG claims

https://www.theguardian.com/us-news/ng-interactive/2026/apr/16/amazon-price-fixing-california-law...
30•kmfrk•1h ago•6 comments

Artifacts: Versioned storage that speaks Git

https://blog.cloudflare.com/artifacts-git-for-agents-beta/
142•jgrahamc•10h ago•14 comments

GPT‑Rosalind for life sciences research

https://openai.com/index/introducing-gpt-rosalind/
37•babelfish•4h ago•7 comments

Python Package Compiler:Package Matlab Programs for Deployment as Python Package

https://www.mathworks.com/help/compiler_sdk/ml_code/pythonpackagecompiler-app.html
5•teleforce•3d ago•0 comments

Circuit Transformations, Loop Fusion, and Inductive Proof

https://natetyoung.github.io/carry_save_fusion/
18•matt_d•3d ago•1 comments

IBM AP-101 general-purpose computer [pdf]

https://gandalfddi.z19.web.core.windows.net/Shuttle/IBM%20AP-101S%20General%20Purpose%20Computer%...
11•__patchbit__•3d ago•2 comments

Playdate’s handheld changed how Duke University teaches game design

https://news.play.date/news/duke-playdate-education/
35•Ivoah•4h ago•13 comments

Show HN: CodeBurn – Analyze Claude Code token usage by task

https://github.com/AgentSeal/codeburn
68•agentseal•3d ago•14 comments

Show HN: MacMind – A transformer neural network in HyperCard on a 1989 Macintosh

https://github.com/SeanFDZ/macmind
107•hammer32•10h ago•31 comments

The "Passive Income" trap ate a generation of entrepreneurs

https://www.joanwestenberg.com/the-passive-income-trap-ate-a-generation-of-entrepreneurs/
89•devonnull•2h ago•78 comments

Codex Hacked a Samsung TV

https://blog.calif.io/p/codex-hacked-a-samsung-tv
195•campuscodi•12h ago•113 comments

Cloudflare Email Service

https://blog.cloudflare.com/email-for-agents/
393•jilles•10h ago•186 comments

AI cybersecurity is not proof of work

https://antirez.com/news/163
189•surprisetalk•12h ago•78 comments

European civil servants are being forced off WhatsApp

https://www.politico.eu/article/european-civil-servants-new-messaging-services/
79•aa_is_op•3h ago•48 comments

Six Characters

https://ajitem.com/blog/iron-core-part-2-six-characters/
82•Airplanepasta•3d ago•13 comments

PHP 8.6 Closure Optimizations

https://wiki.php.net/rfc/closure-optimizations
108•moebrowne•2d ago•29 comments

Japan implements language proficiency requirements for certain visa applicants

https://www.japantimes.co.jp/news/2026/04/15/japan/society/jlpt-visa-requirement/
120•mikhael•6h ago•88 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•11mo ago

Comments

tonyarkles•11mo 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•11mo ago
You can convert edge coloring problems into vertex coloring problems and vice versa through a simple O(n) procedure.
meindnoch•11mo 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•11mo ago
Indeed. Thanks, I stand corrected.
tonyarkles•11mo 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•11mo 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•11mo 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•11mo ago
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•11mo 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•11mo 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•11mo 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.
phkahler•11mo ago
Is this going to lead to faster compile times? Faster register allocation...
john-h-k•11mo ago
Very few compilers actually use vertex coloring for register allocation
isaacimagine•11mo 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•11mo ago
and this post isn't even about vertex coloring
DannyBee•11mo 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.