frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Civic Hygiene – avoid building technologies that could be used by a police state (2013)

https://shkspr.mobi/blog/2013/11/civic-hygiene/
124•felineflock•39m ago•60 comments

Geolocating a random island using geometry and CUDA programming

https://yassa9.github.io/osint/gralhix-004/
235•yassa9•4h ago•47 comments

A joke domain purchase turned in geopolitical warfare

https://sprocketfox.io/xssfox/2026/08/19/sondehub-and-war/
315•kareiva•5h ago•41 comments

OpenLogi

https://openlogi.org/en
1302•amatheus•14h ago•358 comments

Microgpt in pure C hits 10M tps on Apple m5

https://github.com/vixhal-baraiya/microgpt-c
48•dhorthy•1d ago•10 comments

PostgreSQL for Everything

https://www.raphaelbauer.com:443/posts/postgresql-everything/
158•karlmush•3h ago•107 comments

Launch HN: OneCLI (YC S26) – OSS sandboxed agent harness for teams

https://github.com/onecli/onecli
5•guyb3•18m ago•0 comments

Moderna reports first positive Phase 3 for mRNA neoantigen therapy in melanoma

https://twitter.com/NoubarAfeyan/status/2090050162441752787
275•heydenberk•3h ago•111 comments

Devices with GrapheneOS support should be available in 2027

https://grapheneos.social/@GrapheneOS/117078064184215730
448•exceptione•5h ago•266 comments

Remote workers report the highest well-being in study of 7,700 employees

https://www.colorado.edu/today/2026/08/12/remote-workers-report-highest-well-being-study-7700-emp...
81•downbad_•1h ago•34 comments

Chain-of-Thought Reasoning in the Wild Is Not Always Faithful

https://arxiv.org/abs/2503.08679
7•florianherrengt•28m ago•2 comments

Ornith-1.5: From Self-Scaffolding to Self-Improvement

https://ornith.ai/ornith_1_5.html
24•CommonGuy•1h ago•2 comments

Air Theremin – a browser theremin you play by waving at your webcam

https://theremin.bizibah.com/
165•gurov•6h ago•65 comments

Taffy: A flexible, high-performance, cross-platform UI layout library

https://github.com/DioxusLabs/taffy
59•robin_reala•6d ago•23 comments

Extensible Software in the Age of LLMs

https://jeremymorrell.dev/blog/extensible-software-in-the-age-of-llms/
3•coloneltcb•21m ago•0 comments

A decades-old bug in Knuth's long division (TAOCP Vol II, Algorithm 4.3.1D)

https://kolja.rs/algorithm-d/
104•nk_kolja•6d ago•21 comments

Cerebras CS-4

https://www.cerebras.ai/cs4
407•sunils34•16h ago•247 comments

Rings forged from meteorites may have been fashionable among ancient Greek elite

https://phys.org/news/2026-08-forged-meteorites-fashionable-ancient-greek.html
86•pseudolus•5d ago•35 comments

Being ambitious and being a dad

https://nicholascharriere.com/blog/being-ambitious-and-being-a-dad/
789•nichochar•3d ago•599 comments

Supersonic Trebuchet [video]

https://www.youtube.com/watch?v=Co57SfcT-h0
209•CharlesW•4d ago•92 comments

Mathematics in the Age of AI

https://arxiv.org/abs/2608.16753
7•jonbaer•1h ago•3 comments

Activation Energy is a good model for a lot of things

https://homosabiens.substack.com/p/activation-energy-is-a-good-model
117•surprisetalk•5d ago•32 comments

Show HN: Nikon F100 Film Camera Repair Notes

https://github.com/enthdegree/f100
25•enthdegree•4d ago•12 comments

Palomar: A registry of Lean verified mathematics

https://terrytao.wordpress.com/2026/08/18/palomar-a-registry-of-lean-verified-mathematics/
155•matt_d•14h ago•37 comments

A 3D fruit fly on macOS desktop powered by the real FlyWire connectome

https://github.com/DenisSergeevitch/desktop-fly
355•phoenix120•18h ago•163 comments

New Casio F-B100W – Upgrade to the iconic F-91W after 40 years

https://www.casio.com/uk/watches/casio/product.F-B100W-1A/
75•__fst__•1h ago•62 comments

How does IKEA come up with names for its products?

https://www.ikea.com/se/en/customer-service/knowledge/articles/6f564c4d-2ccc-46de-b643-545a3948dc...
427•NaOH•22h ago•304 comments

λλ: A Programming Language for Silicon Photonics

https://dl.acm.org/doi/10.1145/3789240.3829151
74•matt_d•10h ago•16 comments

Finger: the 1971 social network that never died

https://en.andros.dev/blog/54572bc7/finger-the-1971-social-network-that-never-died/
296•andros•1d ago•99 comments

A 25-year-old video patent just expired, ending a legal headache for Linux

https://www.xda-developers.com/25-year-old-brazilian-video-patent-expired-legal-headache-linux/
288•theanonymousone•4d ago•143 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.