frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

I love the work of the ArchWiki maintainers

https://k7r.eu/i-love-the-work-of-the-archwiki-maintainers/
247•panic•6h ago•39 comments

Flashpoint Archive – Over 200k web games and animations preserved

https://flashpointarchive.org
20•helloplanets•1h ago•4 comments

My smart sleep mask broadcasts users' brainwaves to an open MQTT broker

https://aimilios.bearblog.dev/reverse-engineering-sleep-mask/
404•minimalthinker•15h ago•192 comments

Zvec: A lightweight, fast, in-process vector database

https://github.com/alibaba/zvec
124•dvrp•1d ago•21 comments

Instagram's URL Blackhole

https://medium.com/@shredlife/instagrams-url-blackhole-c1733e081664
153•tkp-415•1d ago•24 comments

I'm building a clarity-first language (compiles to C++)

https://github.com/taman-islam/rox
21•hedayet•4d ago•18 comments

5,300-year-old 'bow drill' rewrites story of ancient Egyptian tools

https://www.ncl.ac.uk/press/articles/latest/2026/02/ancientegyptiandrillbit/
99•geox•4d ago•22 comments

uBlock filter list to hide all YouTube Shorts

https://github.com/i5heu/ublock-hide-yt-shorts/
787•i5heu•13h ago•257 comments

News publishers limit Internet Archive access due to AI scraping concerns

https://www.niemanlab.org/2026/01/news-publishers-limit-internet-archive-access-due-to-ai-scrapin...
471•ninjagoo•12h ago•298 comments

How often do full-body MRIs find cancer?

https://www.usatoday.com/story/life/health-wellness/2026/02/11/full-body-mris-cancer-aneurysm/883...
92•brandonb•1d ago•99 comments

The consequences of task switching in supervisory programming

https://martinfowler.com/fragments/2026-02-13.html
70•bigwheels•1d ago•32 comments

Amsterdam Compiler Kit

https://github.com/davidgiven/ack
117•andsoitis•14h ago•32 comments

OpenAI should build Slack

https://www.latent.space/p/ainews-why-openai-should-build-slack
143•swyx•23h ago•144 comments

MDST Engine: run GGUF models in the browser with WebGPU/WASM

https://mdst.app/blog/mdst_engine_run_gguf_models_in_your_browser
10•vmirnv•3d ago•2 comments

Can my SPARC server host a website?

https://rup12.net/posts/can-my-sparc-server-host-my-website/
50•e145bc455f1•4d ago•38 comments

Guitars of the USSR and the Jolana Special in Azerbaijani Music

https://caucascapades.wordpress.com/2012/06/14/guitars-of-the-ussr-and-the-jolana-special-in-azer...
19•bpierre•3h ago•2 comments

Breaking the spell of vibe coding

https://www.fast.ai/posts/2026-01-28-dark-flow/
204•arjunbanker•1d ago•152 comments

NewPipe: YouTube client without vertical videos and algorithmic feed

https://newpipe.net/
209•nvader•6h ago•55 comments

Flood Fill vs. The Magic Circle

https://www.robinsloan.com/winter-garden/magic-circle/
61•tobr•3d ago•19 comments

Connes Embedding Problem

https://en.wikipedia.org/wiki/Connes_embedding_problem
16•jerlendds•2d ago•1 comments

Show HN: Off Grid – Run AI text, image gen, vision offline on your phone

https://github.com/alichherawalla/off-grid-mobile
86•ali_chherawalla•8h ago•35 comments

Ooh.directory: a place to find good blogs that interest you

https://ooh.directory/
487•hisamafahri•17h ago•124 comments

Show HN: MOL – A programming language where pipelines trace themselves

https://github.com/crux-ecosystem/mol-lang
31•MouneshK•3d ago•9 comments

A review of M Disc archival capability with long term testing results (2016)

http://www.microscopy-uk.org.uk/mag/artsep16/mol-mdisc-review.html
76•1970-01-01•15h ago•95 comments

Windows NT/OS2 Design Workbook

https://computernewb.com/~lily/files/Documents/NTDesignWorkbook/
102•markus_zhang•4d ago•37 comments

Linear Representations and Superposition

http://ternarysearch.blogspot.com/2026/02/linear-representations-and-superposition.html
11•paladin314159•2h ago•0 comments

Descent, ported to the web

https://mrdoob.github.io/three-descent/
209•memalign•11h ago•43 comments

Interference Pattern Formed in a Finger Gap Is Not Single Slit Diffraction

https://note.com/hydraenids/n/nbe89030deaba
3•uolmir•2d ago•1 comments

Colored Petri Nets, LLMs, and distributed applications

https://blog.sao.dev/cpns-llms-distributed-apps/
37•stuartaxelowen•10h ago•5 comments

A header-only C vector database library

https://github.com/abdimoallim/vdb
75•abdimoalim•13h ago•31 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•9mo ago

Comments

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