frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Fable wrote a .NET GC in C#, got within range of the stock GC in 2 days

https://github.com/kevingosse/ManagedDotnetGC/tree/claude/experiments
1•kookiz•58s ago•1 comments

How AI Embeddings Cut Cloud Costs by 50% While Boosting Matching by 65%

https://tech.wmg.com/breaking-the-black-box-how-ai-embeddings-cut-cloud-costs-by-50-while-boostin...
1•wmg•1m ago•0 comments

Funding open-source software without compromising it

https://yorickpeterse.com/articles/funding-open-source-software-without-compromising-it/
1•YorickPeterse•2m ago•0 comments

The $2T question: Will knowledge-work complexity scale with model capability?

https://twitter.com/__josh_harris__/status/2074824864288919945
1•jah242•4m ago•1 comments

Show HN: GhostedWatch, an extension that detects silent removals on patriots.win

https://ghostedwatch.com/
1•rhaksw•6m ago•0 comments

China warns about AI risks with Anthropic's Claude Code

https://www.cnbc.com/2026/07/08/china-anthropic-ai-claude-code-backdoor-security-threat.html
1•cramer4next•6m ago•1 comments

Robots available for rent: But what can they do?

https://www.bbc.com/news/articles/c4gymkg9lr2o
1•monkeydust•7m ago•0 comments

Show HN: I built the NAS drive comparison table I couldn't find

https://www.nasdisks.com/
2•deeddy•7m ago•0 comments

Show HN: Seqvio – a whiteboard explainer toolkit for React/TSX videos

https://github.com/makesynt/seqvio
1•markthis•9m ago•0 comments

Kasroz: An Optimal Keyboard for Swipe

https://futo.tech/blog/swipe-keyboard
1•ementally•9m ago•0 comments

The Second Derivative: Why No One Understands the AI Boom

https://www.groundbrkr.com/p/the-second-derivative-why-no-one
1•ericwaller•10m ago•0 comments

What happens inside a tennis player's brain as they try to return a 148mph serve

https://theconversation.com/what-happens-inside-a-tennis-players-brain-as-they-try-to-return-a-14...
1•0in•10m ago•0 comments

How to cheat when crossing the Channel by swimming

https://github.com/valhalla/valhalla/discussions/6190
1•nilsnolde•10m ago•0 comments

Show HN: VetoBench – benchmarking AI memory beyond retrieval

https://github.com/adelinamart/robrain/tree/main/packages/vetobench
2•mart1adelina•12m ago•0 comments

First Robot-Run Hotel Is Opening in China

https://www.gadgetreview.com/worlds-first-fully-robot-run-hotel-is-opening-in-china
1•surprisetalk•12m ago•0 comments

Show HN: DeviceShelf – a read-only LAN scanner for homelabs, no cloud back end

https://deviceshelf.app/
1•itsmueller•12m ago•0 comments

Ask HN: Can I find enthusiasts like me as a first time builder?

2•AlexSonn•13m ago•0 comments

Stop Writing Claude.md Rules. Write Linting Rules Instead

https://zernie.com/blog/stop-writing-claude-md-rules/
1•speckx•14m ago•0 comments

Reducing Android JVM allocations for less memory pressure and faster logs

https://blog.bitdrift.io/post/reducing-android-jvm-allocations
1•karinakarina3•14m ago•0 comments

Deprecated Accessor Footgun in AI SDK v7

https://www.lightningjar.com/blog/tool-history-footgun
1•kevinpeckham•16m ago•0 comments

Show HN: Argutum – an AI chat that pays you per message, scored in real time

https://argutum.com
1•ayushsanghavi•17m ago•0 comments

The Age of Reading Is Over

https://www.theatlantic.com/magazine/2026/08/reading-crisis-postliterate-age/687618/
2•0in•19m ago•0 comments

Handsum: An LQIP Image File Format

https://nigeltao.github.io/blog/2026/handsum.html
1•dmit•19m ago•0 comments

An ad-hoc replacement for multitail made with tmux and grcat

https://github.com/themadsens/tmtail/tree/main
1•themadsens•21m ago•0 comments

New EU plan to address the risks and opportunities of advanced AI for cybersec

https://commission.europa.eu/news-and-media/news/new-eu-plan-address-risks-and-opportunities-adva...
1•_____k•21m ago•0 comments

Show HN: CodeRadius, map and govern multi repo architectures

https://coderadius.ai
1•emnlmn•23m ago•0 comments

Show HN: Control YOLO Training and Datasets from Claude/Cursor via MCP

https://github.com/amanharshx/ultralytics-mcp
3•amanharshx•23m ago•0 comments

Companies Reserving AI-Training Rights in Their Terms

https://tostracker.app/analysis/ai-training-rights
1•tldrthelaw•23m ago•0 comments

Recovering a failing disk using a Raspberry Pi and a bit of AI

https://aes.id.au/blog/2026/07/08/recovering-a-failing-disk-using-a-raspberry-pi-and-a-bit-of-ai/
1•andrewescott•24m ago•0 comments

Real limits converted to API-equivalent $ value for Claude Code, Codex, Copilot

https://twitter.com/ivanborshchov/status/2074823674205458756
1•deviscool•25m ago•1 comments
Open in hackernews

Generating Mazes with Inductive Graphs (2017)

https://jelv.is/blog/Generating-Mazes-with-Inductive-Graphs/
20•todsacerdoti•1y ago

Comments

tomfly•1y ago
where is the entrance and exit?
Jaxan•1y ago
Doesn’t matter, because all positions are reachable. So just pick any two positions at the border and remove a wall.
kazinator•1y ago
Here is a maze that was generated recursively starting at the upper left cell.

  +    +----+----+----+----+----+----+----+----+----+
  |    |                        |                   |
  |    |                        |                   |
  +    +----+----+    +----+    +----+    +----+    +
  |              |         |                   |    |
  |              |         |                   |    |
  +----+----+    +    +----+----+----+----+----+    +
  |              |    |                        |    |
  |              |    |                        |    |
  +    +----+----+    +    +----+----+----+    +    +
  |         |              |              |    |    |
  |         |              |              |    |    |
  +    +----+    +    +----+----+----+    +    +----+
  |              |    |                   |    |    |
  |              |    |                   |    |    |
  +----+----+----+    +    +----+----+----+    +    +
  |                        |                   |    |
  |                        |                   |    |
  +    +----+----+----+    +    +----+----+----+    +
  |    |    |              |    |              |    |
  |    |    |              |    |              |    |
  +    +    +    +    +----+    +    +----+    +    +
  |    |    |    |    |         |    |         |    |
  |    |    |    |    |         |    |         |    |
  +    +    +    +    +----+----+----+    +    +    +
  |    |    |    |    |                   |         |
  |    |    |    |    |                   |         |
  +    +    +----+    +    +----+----+    +----+----+
  |              |         |                        |
  |              |         |                        |
  +----+----+----+----+----+----+----+----+----+    +

It matters to start there because it will be easier if you go backwards.

The maze has 100 cells. For each cell, we can calculate which exit goes back toward the entrance, assigning the letters U, D, L, R:

  U R R D L L R D L L
  U L L D L U L L L U
  R R U D D L L L L U
  U L D L L R R D U U
  U L L U D L L L U D
  R R R U L R R R U D
  U D R R U U R R D D
  U D U U R U U D L D
  U D U U D L L L U L
  U L L U L R R U L L
Stats:

  L - 33
  U - 29
  R - 20
  D - 18
Left and Up are more frequent back-to-entrance escapes than Right or Down. This is because of the way the maze was generated.

To check the hypothesis, we should analyze it in the other direction. For each cell, determine the exit which heads in the direction of the exit:

  D R R D L L R D L L
  D R D D L U L L L U
  D L L D D L L L L U
  D L R D L R R D D U
  R R U D D L L L U D
  R R R R D R R R U D
  U D R D L U R R D D
  U D U D R U U D L D
  U D U D R R R D U L
  U L L R U R R R R D
Stats:

  D - 30
  R - 28
  L - 24
  U - 18
There is a weaker bias for the D-R axis toward the exit, compared to the L-U axis toward the entrance. I suspect if we study larger numbers of larger mazes, we will find similar findings.

So that is to say, it is easier to navigate the maze in the reverse direction: the heuristic to try left/up exits will work more often than the right/down in the proper direction.

smartmic•1y ago
From the book "Mazes for Programmers" by Jamis Buck, 2015, The Pragmatic Programmers (a must-read for any maze/programming enthusiast!):

> Aren't mazes supposed to have starting points and end points? […] honestly, […] it's entirely up to you. […] The maze […] is a perfect maze, and one of the attributes of a perfect maze is that there exists exactly one path between any two cells in it. […] You pick them, and there's guaranteed to be a path between them.

You do not need to choose an entrance or exit only on the sides, but you can also choose "Pacman-style" where the goal is to reach points inside the maze.

"Perfect" refers to the mathematical/logical properties of a maze (i.e. no loops), not the aesthetical aspect. I have not checked though if the mazes in the source here are all perfect.

kazinator•1y ago
While you can put the entrance and exit wherever you want, if you know that the maze was generated by a recursive branching process which had a starting point somewhere, it probably behooves you to put the start at that point corresponding to the root of the tree, so that the maze wanderer faces the most branching choices.

Laying out the abstract maze tree into the rectilinear grid of cells obfuscates the tree somewhat, but not entirely. A process that generates from upper left to lower right, for instance, will tend to generate cells whose parent-headed exits going left and up more often than not, making the reverse direction a bit easier.

(Again, it depends on the maze generation process.)

kazinator•1y ago
Making random mazes in a rectilinear grid is a good exercise for one big reason: mazes are not all the same. Mazes have style can be very knotty and twisty, or have long passages. You can add hacks into a given algorithm to vary the style, but there are certain things it won't necessarily do.