frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

ASML firing 1700 people, mostly managers

https://www.ed.nl/binnenland/asml-wil-veel-managementbanen-schrappen-rekent-op-1700-ontslagen~a04...
141•dep_b•1h ago•95 comments

Make.ts

https://matklad.github.io/2026/01/27/make-ts.html
48•ingve•2h ago•27 comments

There's only one Woz, but we can all learn from him

https://www.fastcompany.com/91477114/steve-wozniak-woz-apple-the-tech-interactive-humanitarian-award
92•coloneltcb•4d ago•30 comments

SVG Path Editor

https://yqnn.github.io/svg-path-editor/
68•gurjeet•5d ago•7 comments

Prism

https://openai.com/index/introducing-prism
647•meetpateltech•15h ago•369 comments

I Stopped Following the News

https://mertbulan.com/2026/01/28/why-i-stopped-following-the-news/
68•mertbio•1h ago•41 comments

A few random notes from Claude coding quite a bit last few weeks

https://twitter.com/karpathy/status/2015883857489522876
608•bigwheels•1d ago•486 comments

Golden Ratio using an equilateral triangle inscribed in a circle

https://geometrycode.com/free/how-to-graphically-derive-the-golden-ratio-using-an-equilateral-tri...
76•peter_d_sherman•4d ago•20 comments

Thirty Years of the Square Kilometre Array

https://physicsworld.com/a/thirty-years-of-the-square-kilometre-array-heres-what-the-worlds-large...
8•mooreds•2d ago•0 comments

430k-year-old well-preserved wooden tools are the oldest ever found

https://www.nytimes.com/2026/01/26/science/archaeology-neanderthals-tools.html
422•bookofjoe•18h ago•219 comments

Rust at Scale: An Added Layer of Security for WhatsApp

https://engineering.fb.com/2026/01/27/security/rust-at-scale-security-whatsapp/
19•ubj•3h ago•2 comments

Rust’s Standard Library on the GPU

https://www.vectorware.com/blog/rust-std-on-gpu/
172•justaboutanyone•4d ago•27 comments

Parametric CAD in Rust

https://campedersen.com/vcad
164•ecto•13h ago•112 comments

Lennart Poettering, Christian Brauner founded a new company

https://amutable.com/about
298•hornedhob•14h ago•431 comments

Doing the thing is doing the thing

https://www.softwaredesign.ing/blog/doing-the-thing-is-doing-the-thing
384•prakhar897•1d ago•127 comments

Xfwl4 – The Roadmap for a Xfce Wayland Compositor

https://alexxcons.github.io/blogpost_15.html
319•pantalaimon•20h ago•239 comments

Time Station Emulator

https://github.com/kangtastic/timestation
168•FriedPickles•13h ago•42 comments

Amazon closing its Fresh and Go stores

https://finance.yahoo.com/news/amazon-closing-fresh-grocery-convenience-150437789.html
235•trenning•18h ago•440 comments

AI2: Open Coding Agents

https://allenai.org/blog/open-coding-agents
191•publicmatt•16h ago•30 comments

Show HN: One Human + One Agent = One Browser From Scratch in 20K LOC

https://emsh.cat/one-human-one-agent-one-browser/
238•embedding-shape•20h ago•113 comments

SoundCloud Data Breach Now on HaveIBeenPwned

https://haveibeenpwned.com/Breach/SoundCloud
179•gnabgib•16h ago•93 comments

FBI is investigating Minnesota Signal chats tracking ICE

https://www.nbcnews.com/tech/internet/fbi-investigating-minnesota-signal-minneapolis-group-ice-pa...
744•duxup•16h ago•1005 comments

I found the perfect yearly calendar (for me)

https://blog.notmyhostna.me/posts/i-found-the-perfect-yearly-calendar-for-me
61•dewey•4d ago•23 comments

Notes on starting to use Django

https://jvns.ca/blog/2026/01/27/some-notes-on-starting-to-use-django/
84•ingve•10h ago•36 comments

AISLE’s autonomous analyzer found all CVEs in the January OpenSSL release

https://aisle.com/blog/aisle-discovered-12-out-of-12-openssl-vulnerabilities
159•mmsc•8h ago•112 comments

Bridging the Gap Between PLECS and SPICE

https://erickschulz.dev/posts/plecs-spice/
37•eschu•2d ago•15 comments

The Texas Instruments CC-40 invades Gopherspace (plus TI-74 BASICALC)

http://oldvcr.blogspot.com/2025/12/the-texas-instruments-cc-40-invades.html
20•PaulHoule•5d ago•1 comments

Extremophile molds are invading art museums

https://www.scientificamerican.com/article/how-extremophile-molds-are-destroying-museum-artifacts/
101•sohkamyung•4d ago•51 comments

Try text scaling support in Chrome Canary

https://www.joshtumath.uk/posts/2026-01-27-try-text-scaling-support-in-chrome-canary/
101•linolevan•14h ago•34 comments

Hypercubic (YC F25) Is Hiring a Founding SWE and COBOL Engineer

https://www.ycombinator.com/companies/hypercubic/jobs
1•sai18•15h ago
Open in hackernews

The Fastest Way yet to Color Graphs

https://www.quantamagazine.org/the-fastest-way-yet-to-color-graphs-20250512/
62•GavCo•8mo ago

Comments

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