frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Claude is just Mr. Meeseeks

https://github.com/thephw/claude-meseeks
85•patrickwiseman•1h ago•26 comments

‘Asia's cleanest village’ bans tourists on Sundays

https://www.bbc.com/travel/article/20260625-why-asias-cleanest-village-bans-tourists-on-sundays
42•gmays•1h ago•20 comments

Building and shipping Mac and iOS apps without ever opening Xcode

https://scottwillsey.com/building-and-shipping-mac-and-ios-apps-without-ever-opening-xcode/
254•speckx•5h ago•116 comments

Apple's new SpeechAnalyzer API, benchmarked against Whisper and its predecessor

https://get-inscribe.com/blog/apple-speech-api-benchmark.html
411•get-inscribe•7h ago•172 comments

An Englishwoman who sketched India before photography took hold

https://www.bbc.com/news/articles/cm2drrv6q54o
9•1659447091•46m ago•0 comments

Linux on the Sega 32X. Who needs hardware synchronization primitives anyway?

https://cakehonolulu.github.io/linux-on-32x/
88•cakehonolulu•5h ago•20 comments

The art and engineering of Sega CD Silpheed

https://fabiensanglard.net/silpheed/index.html
207•ibobev•9h ago•40 comments

Show HN: YouTube Guitar Tab Parser

https://github.com/marcelpanse/youtube-guitar-tab-parser
54•neogenix•3h ago•40 comments

The infinite scroll may become endangered if controversial Calif. law passes

https://www.sfgate.com/politics/article/meta-social-media-teenagers-22337724.php
51•Stratoscope•5h ago•62 comments

Telegram's t.me domain has been suspended

https://www.whois.com/whois/t.me
227•Tiberium•4h ago•156 comments

TFTP Honey Pot Results

https://bruceediger.com/posts/tftp-honeypot-results/
48•speckx•4h ago•20 comments

SalesPatriot (YC W25) Is Hiring Full Stack Engineers (SF)

https://jobs.ashbyhq.com/SalesPatriot/df223727-5781-433e-bc75-2aa5bf8dc8d7
1•maciejSz•2h ago

Samsung Health app threatens data deletion if users opt out AI training

https://neow.in/cWsyMTV3
224•bundie•3h ago•62 comments

Climate.gov was destroyed. Open data saved it

https://werd.io/climate-gov-was-destroyed-open-data-saved-it/
384•benwerd•4h ago•154 comments

MIT's New Method Flags AI Models Trained on CASM Without Generating It

https://insideai.news/news/ai-safety/mits-new-method-flags-ai-models-trained-on-child-abuse-image...
11•sdoering•2h ago•5 comments

Show HN: Jacquard, a programming language for AI-written, human-reviewed code

https://github.com/jbwinters/jacquard-lang
37•jbwinters•8h ago•13 comments

Show HN: Hackney – Compare Uber, Lyft, Waymo, and Robotaxi Prices

https://hackney.app/
8•griffinli•9h ago•8 comments

Show HN: I implemented a neural network in SQL

https://github.com/xqlsystems/xarray-sql/blob/claude/xarray-sql-mnist-demo/benchmarks/nn.py
46•alxmrs•3h ago•12 comments

Ancient Roman Board Game

https://ludus-coriovalli.web.app/
81•nobody9999•4d ago•35 comments

Linux 0.11 rewritten in idiomatic Rust, boots in QEMU

https://github.com/Poseidon-fan/linux-0.11-rs
80•arto•3h ago•65 comments

The Origins of Heikki's Garden of Flowers

https://garden-of-flowers.heikkilotvonen.com/?essay
25•panic•2d ago•2 comments

Collaboration Networks in Brazilian Computer Science

https://blog.ptidej.net/collaboration-networks-in-brazilian-computer-science/
6•aliiiimaher•3d ago•1 comments

A Study of Microsoft's Early 2026 Rollout of Claude Code and GitHub Copilot CLI

https://arxiv.org/abs/2607.01418
10•softwaredoug•2h ago•2 comments

A voxel Tokyo in real Japan time – ride the Yamanote line and study Japanese

https://jivx.com/densha
329•momentmaker•12h ago•66 comments

Show HN: Nobie – an Excel-compatible runtime for agents and humans

https://nobie.com
68•matthewgapp•5h ago•35 comments

Show HN: Sigwire – a live TUI switchboard for every signal on your Linux box

https://github.com/yeet-src/sigwire
21•zasc•3h ago•8 comments

Show HN: BillAI Bass, an AI-Powered Big Mouth Billy Bass Using Strands Agents

https://github.com/morganwilliscloud/billai-bass
52•mtw14•5h ago•25 comments

The 4-Bitter Lesson: Balancing Stability and Performance in NVFP4 RL

https://humansand.ai/blog/nvfp4-rl
21•Areibman•3d ago•3 comments

Benchmarking 15 "E-Waste" GPUs with Modern Workloads

https://esologic.com/benchmarking-tesla-gpus/
108•eso_logic•10h ago•46 comments

Manifest Man

https://www.thenewcritic.com/p/manifest-man
7•ekluger•1h ago•3 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.