frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Code duplication is far cheaper than the wrong abstraction

https://sandimetz.com/blog/2016/1/20/the-wrong-abstraction
64•rafaepta•55m ago•33 comments

(How to Write a (Lisp) Interpreter (In Python))

https://norvig.com/lispy.html
45•tosh•1h ago•19 comments

Beyond All Reason (Free Total Annihilation Inspired RTS)

https://www.beyondallreason.info
270•mosiuerbarso•5h ago•134 comments

Who Owns Your ATProto Identity? Hint: It's Probably Not You

https://kevinak.se/blog/who-actually-owns-your-atproto-identity-hint-its-probably-not-you
98•kevinak•2h ago•88 comments

Commodore Made a Digital Detox Phone That Isn't Dumb

https://www.wired.me/story/commodore-made-a-digital-detox-phone-that-isnt-dumb
63•Audiophilip•3d ago•37 comments

Wildcard (YC W25) Is Hiring a Founding Applied ML Engineer

https://www.ycombinator.com/companies/wildcard/jobs/SEmo4di-founding-applied-ml-engineer
1•kaushikmahorker•3m ago

Google Hits 50% IPv6

https://blog.apnic.net/2026/04/28/google-hits-50-ipv6/
333•barqawiz•8h ago•315 comments

System call instrumentation on Linux/x86‑64 using memory‑indirect calls, part I

https://www.humprog.org/~stephen/blog/2026/06/15/#system-call-instrumentation-on-intel-negative-r...
12•matt_d•4d ago•3 comments

Fossil Fuels Are 40% of Freight Shipping Tonnage, but Half Its Fuel Use

https://cleantechnica.com/2026/06/16/shipping-freight-energy-fossil-cargo/
49•choult•2h ago•27 comments

AI Has Broken Hiring

https://hbr.org/2026/06/ai-has-broken-hiring-heres-how-to-fix-it
22•ChrisArchitect•49m ago•15 comments

A 3D voxel game engine written in APL

https://github.com/namgyaaal/avoxelgame
115•sph•8h ago•10 comments

Loupe – A iOS app that raises awareness about what native apps can see

https://github.com/mysk-research/loupe
441•Cider9986•1d ago•176 comments

Running MicroVMs in Proxmox VE, the Easy Way

https://taoofmac.com/space/blog/2026/06/18/1845
158•zdw•2d ago•20 comments

AI is a mass psychotic delusion [video]

https://www.youtube.com/watch?v=WNiSUGCC-gY
9•jmount•15m ago•1 comments

Two Qwen3 models on one DGX Spark: the residency math

https://www.devashish.me/p/two-qwen3-models-on-one-dgx-spark
50•devashish86•3d ago•25 comments

Slow breathing modulates brain function and risk behavior

https://www.cell.com/neuron/fulltext/S0896-6273(26)00339-9
321•croes•18h ago•93 comments

Renting a sewing machine from the library

https://www.bbc.com/future/article/20260618-the-weird-and-wonderful-libraries-of-finland
298•sohkamyung•18h ago•172 comments

Zigzag Decoding with AVX-512

https://zeux.io/2026/06/17/zigzag-decoding-avx512/
112•luu•3d ago•21 comments

Epoll vs. io_uring in Linux

https://sibexi.co/posts/epoll-vs-io_uring/
224•Sibexico•17h ago•52 comments

The case against geometric algebra (2024)

https://alexkritchevsky.com/2024/02/28/geometric-algebra.html
97•Hbruz0•5h ago•85 comments

Occupancy Math on the AMD MI355X: A From-First-Principles Guide

https://indianspeedster.github.io/blog/occupancy-math-mi355x/
7•skidrow•4d ago•0 comments

A tale of two path separators

https://alexwlchan.net/2021/slashes/
52•dbaupp•4d ago•22 comments

David Ahl's Basic Computer Games Ported to C

https://github.com/proteanthread/bcg
39•theanonymousone•4h ago•19 comments

Developers don't understand CORS (2019)

https://fosterelli.co/developers-dont-understand-cors
290•toilet•15h ago•233 comments

Unauthorized alert sent to cell phones across Brazil

https://www.cnn.com/2026/06/20/americas/brazil-hackers-unauthorized-alert-latam
178•zdw•20h ago•127 comments

15-minute at-home Lyme disease tick test

https://www.bostonglobe.com/2026/06/17/business/lyme-disease-tick-test/
178•bookofjoe•3d ago•130 comments

DOS Game "F-15 Strike Eagle II" reversing project needs DOS test pilots

https://neuviemeporte.github.io/f15-se2/2026/06/20/needyou.html
271•LowLevelMahn•1d ago•70 comments

SMPTE Makes Its Standards Freely Accessible

https://www.smpte.org/blog/smpte-makes-its-standards-freely-accessible-openingstandards-library-t...
281•zdw•1d ago•95 comments

UHF X11: X11 Built for VisionOS and Apple Vision Pro

https://www.lispm.net/apps/uhf-x11/
220•zdw•23h ago•49 comments

Rare medieval bookmark exceeds expectations at auction

https://www.thehistoryblog.com/archives/76314
33•speckx•4d ago•10 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.