frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Hybrid Reasoning Agents: LLM agents that think in latent space, act through text

https://arxiv.org/abs/2610.18861
202•allinonai•4h ago•125 comments

William Gibson and the trademarking of cyberspace

https://colo.to/cyberspace.html
55•Eric_Gullichsen•1h ago•3 comments

Someone behind the software

https://karrisaarinen.com/posts/someone-behind-the-software/
311•tosh•9h ago•134 comments

If you don't run your own LLM proxy, how do you know whats going on?

https://jrdsgl.com/if-you-dont-run-your-own-llm-proxy-how-the-fuck-do-you-even-know-whats-going-on/
20•amrrs•4h ago•12 comments

Free Pascal compiler now supports dynamic packages

https://www.getlazarus.org/dynamic/
113•sysrpl•6h ago•22 comments

Laptop Based on 6502 CPU

https://www.maddox.pro/?p=448
25•nanochess•3d ago•6 comments

RepRapMicron

https://github.com/VikOlliver/RepRapMicron/wiki
329•RobotToaster•11h ago•54 comments

Show HN: WhatsApp MCP running free on Cloudflare

https://github.com/finereli/whatsapp-mcp
38•zoozla•3h ago•23 comments

Dogs seem to agree with humans that 'bouba' is round and 'kiki' is spiky

https://www.sciencealert.com/dogs-seem-to-agree-with-humans-that-bouba-is-round-and-kiki-is-spiky
125•gmays•23h ago•75 comments

There's never been a better time to go into math (by: 3blue1brown) [video]

https://www.youtube.com/watch?v=LKrwhjOI8Nc
160•mdp2021•1d ago•112 comments

DeepSeek search and fetch – $0.75 per 1000 successful requests

https://api-docs.deepseek.com/guides/search/
546•fagnerbrack•18h ago•257 comments

PalmOS Lemmings

https://github.com/ardiri/palmos-lemmings
89•memalign•7h ago•23 comments

"Traditional, but Puzzling"

https://unsung.aresluna.org/traditional-but-puzzling/
19•colinprince•2d ago•2 comments

One parser, two bugs, many routers: Exploiting Broadcom WiFi across eCos, Linux

https://quentinkaiser.be/security/2026/10/16/one-parser-two-bugs/
46•zoobab•2d ago•9 comments

16-bit fully functional DIY magnetic core memory

https://www.youtube.com/watch?v=OJ1WYyO2jdY
36•oliculipolicula•3d ago•16 comments

The First Candid

https://www.newyorker.com/magazine/2026/10/19/the-first-candid
46•Thevet•2d ago•10 comments

What the heck is /pkg?

https://anderegg.ca/2026/10/18/what-the-heck-is-pkg
15•GavinAnderegg•8h ago•5 comments

Java sealed classes and exhaustive pattern matching

https://neilmadden.blog/2026/04/24/java-sealed-classes-and-exhaustive-pattern-matching/
136•hnisjafx40•10h ago•102 comments

I built a programming language that LLMs can't use

https://blog.picheta.me/post/killswitch-lang/
74•dom96•1d ago•66 comments

"I'm on a war footing": Terry Tao and the crisis in math

https://www.nytimes.com/2026/10/16/us/math-ai-terence-tao.html
83•vinipolicena•2d ago•116 comments

The Intel 8087 chip: floating-point addition and subtraction

https://www.righto.com/2026/10/8087-addition-subtraction-microcode.html
88•pwg•9h ago•33 comments

Namecheap just seized and disabled all my domains

https://www.reddit.com/r/sysadmin/comments/1x8cycd/namecheap_just_seized_and_disabled_all_my_doma...
432•sashk•8h ago•202 comments

SIGSALY: Churchill's top secret hotline to the president

https://www.iwm.org.uk/history/iwm/cwr/telephone
111•stmw•4d ago•39 comments

Open MicroManipulator – A sub-micrometer 3D motion control plattform

https://github.com/0x23/MicroManipulatorStepper
174•_Microft•14h ago•13 comments

Developing for Debugging (2025)

https://www.davepacheco.net/blog/2025/developing-for-debugging-dns-propagation/
28•mpweiher•1d ago•0 comments

A new way to think about borrow checking (in reverse)

https://verdagon.dev/blog/reverse-borrow-checking
19•verdagon•13h ago•4 comments

The Elizabeth Holmes documentary “You Can See Everything” is deceiving

https://www.readtheprofile.com/p/elizabeth-holmes-documentary-you-can-see-everything
364•MaysonL•22h ago•514 comments

I electrified my push scooter with a power drill

https://eddieabbondanz.io/post/shop/drill-powered-scooter/
131•speckx•4d ago•50 comments

Show HN: The Zelda timeline to catch up before the Ocarina of Time remake

https://legendofhyrule.com/
161•jsomau•12h ago•99 comments

Types of types: Haskell's Kind system

https://thunk.blog/posts/types-of-types-haskell-kind-system/
103•Thom2503•4d ago•73 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.