frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Mistral Large 4

https://mistral.ai/news/mistral-large-4/\
1003•Philpax•4h ago•668 comments

Nobel Prize in Physics goes to Francis Halzen

https://www.nobelprize.org/prizes/physics/2026/
375•solarist•8h ago•114 comments

Release of Polars 2.0

https://pola.rs/posts/release-polars-2/
293•simicd•5h ago•53 comments

AI is now capable of developing its own inference hardware

https://github.com/FeSens/openTPU
102•fsbonetto•1h ago•70 comments

The Early History of Smalltalk (1993)

https://worrydream.com/EarlyHistoryOfSmalltalk/
56•_reza•2h ago•12 comments

Tapo (Rust/Python library) now speaks TP-Link's TPAP protocol

https://mihai.dinculescu.dev/posts/tapo-speaks-tpap/
89•faithraven•3h ago•31 comments

JetBrains reported a net financial loss first time in its tracked history

https://www.helgilibrary.com/companies/jetbrains
498•thw_9a83c•6h ago•467 comments

Benchmark in Milliseconds

https://matklad.github.io/2026/10/05/benchmark-milliseconds.html
74•surprisetalk•1d ago•16 comments

Meta's Muse Is an Adorable Privacy and Security Dumpster Fire

https://www.techdirt.com/2026/10/06/metas-muse-is-an-adorable-privacy-and-security-dumpster-fire/
284•beardyw•5h ago•182 comments

Gleam doesn't compile to Erlang source anymore

https://gleam.run/news/gleam-doesnt-compile-to-erlang-source-anymore/
214•ingve•9h ago•94 comments

Adobe Creative Suite Cleanroom Ported to Rust

https://github.com/storytold/photocraft
4•bigwheels•34m ago•1 comments

Mathematics of Geothermal Energy

https://www.ebsco.com/research-starters/power-and-energy/mathematics-geothermal-energy/
45•srameshc•4h ago•16 comments

Show HN: I turned my iPhone and a $20 smart plug into an f-stop timer

https://peterszentkiralyi.eu/darkplug/
17•pentakkusu•3h ago•1 comments

Subquadratic 3SUM and Subcubic APSP

https://arxiv.org/abs/2610.06783
34•mauriziocalo•5h ago•14 comments

Nature's capacity to 'bounce back' when species are lost is vastly overestimated

https://phys.org/news/2026-10-nature-capacity-species-lost-vastly.html
220•pseudolus•6h ago•103 comments

Beam: Reflection's 501B open-weight model

https://reflection.ai/blog/introducing-beam
515•Philpax•22h ago•164 comments

Show HN: Parseable, an open observability datalake, handles 100M time-series/min

https://www.parseable.com
44•yashdotrv•4h ago•9 comments

Find the flattest route between any two points in SF

https://flattensf.com/
273•ishan0102•20h ago•95 comments

Dust: Pretraining Transformers Without Backpropagation

https://qlabs.sh/research/dust
253•E-Reverance•20h ago•68 comments

World's First enhanced geothermal power plant completed in just 23 months

https://techcrunch.com/2026/10/01/worlds-first-enhanced-geothermal-power-plant-completed-in-just-...
118•hochmartinez•6h ago•47 comments

I'm the AGI that's wiping out humanity

https://ajmoon.com/posts/im-the-agi-thats-wiping-out-humanity-heres-how
27•alex-moon•6h ago•5 comments

Direct retinal projection display for smart glasses using a meta-optic mirror

https://www.tdk.com/en/news_center/press/20261002_01.html
96•bookofjoe•3d ago•42 comments

Friendship ended with Deno, now Node is my best friend

https://dbushell.com/2026/10/03/deno-to-node/
277•ibobev•19h ago•187 comments

Opus 5.5 agents discover two room-temperature magnetic semiconductor candidates

https://www.vals.ai/blogs/room-temperature-magnetic-semiconductors
446•outlier99•20h ago•304 comments

Testing 12 different Zigbee temperature/humidity sensors

https://smarthomescene.com/reviews/best-selling-zigbee-temperature-sensors-tested/
186•walrus01•2d ago•105 comments

Competitive Programmer's Handbook (2018) [pdf]

https://cses.fi/book/book.pdf
269•vinhnx•3d ago•66 comments

Two ARM64-specific compiler optimization bugs, in GCC 15/16 and Rust, hit curl

https://mastodon.social/@bagder/117392573268225646
39•torutofu•4h ago•5 comments

The complement of true is true, except when it's false

https://dryperspective.github.io/posts/complement-of-true/
54•aw1621107•2d ago•18 comments

Example.com just launched the biggest redesign in decades

https://www.debugbear.com/blog/example-dot-com-redesign-history
305•jgx0•18h ago•208 comments

The lamps in my house

https://arslan.io/2026/10/05/the-lamps-in-my-house/
296•farslan•1d ago•112 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.