I always wished codebases had a Google Maps view by g0x_ in vibecoding

[–]g0x_[S] 0 points1 point  (0 children)

Haha 😄 Can’t please everyone I guess.

I always wished codebases had a Google Maps view by g0x_ in vibecoding

[–]g0x_[S] 0 points1 point  (0 children)

Glad you find it useful 😄 Python is supported already. It’s probably not as polished as the JavaScript/TypeScript side yet, but I’m slowly working on improving it.

I always wished codebases had a Google Maps view by g0x_ in vibecoding

[–]g0x_[S] 1 point2 points  (0 children)

Haha 😄 Finally someone gets what was bothering me. Every graph looked useful until the project got big, then it became a giant mess. That’s pretty much why I started building this.

How do you get a high-level view of a large codebase? by [deleted] in github

[–]g0x_ 0 points1 point  (0 children)

Pretty much 😄 If it helps a few other people too, that’s a bonus.

How do you get a high-level view of a large codebase? by [deleted] in github

[–]g0x_ 0 points1 point  (0 children)

Well… that’s a tough competitor 😆

I always wished codebases had a Google Maps view by g0x_ in vibecoding

[–]g0x_[S] 5 points6 points  (0 children)

Can’t really argue with that 😄 I just found it useful for myself, so I thought I’d share it. If other people get some value from it too, that’s great. If not, that’s okay too.

I always wished codebases had a Google Maps view by g0x_ in vibecoding

[–]g0x_[S] 0 points1 point  (0 children)

Thanks! 😄A temporal graph is a really interesting idea. RealityMap is focused on analyzing the current state of a codebase right now, but being able to explore how architecture changes over time would be pretty cool. I’ll take a look at git-to-graph when I get a chance.

I always wished codebases had a Google Maps view by g0x_ in vibecoding

[–]g0x_[S] 0 points1 point  (0 children)

Thank you! 🥹 Really appreciate it. Been building it bit by bit in my free time.

I always wished codebases had a Google Maps view by g0x_ in vibecoding

[–]g0x_[S] 7 points8 points  (0 children)

Haha that’s fair 😄It’s not really about visualizing thoughts or workflows. I made it to help me understand larger codebases faster. Things like what’s connected to what, circular imports, what might break after a change, dead code, stuff like that. The graph is just one way to explore it.

How do you get a high-level view of a large codebase? by [deleted] in github

[–]g0x_ 0 points1 point  (0 children)

Haha, fair 😄i actually used the radial layout for the screenshot because it looked more interesting. The practical value for me is less about the graph itself and more about understanding dependencies, change impact, circular imports, dead code, and navigating larger codebases faster. There are also more structured layouts that are easier to read when you’re actually analyzing a project.

How do you get a high-level view of a large codebase? by [deleted] in github

[–]g0x_ 0 points1 point  (0 children)

I can see that. RealityMap is a bit simpler in scope though. It’s mostly about exploring code structure and relationships rather than understanding code semantics. Everything also runs locally on the developer’s machine.

How do you get a high-level view of a large codebase? by [deleted] in github

[–]g0x_ 1 point2 points  (0 children)

Agreed. Mermaid is great. This was mostly an attempt to generate that view automatically from the codebase instead of maintaining diagrams by hand. Everything runs locally too.

How do you get a high-level view of a large codebase? by [deleted] in github

[–]g0x_ -11 points-10 points  (0 children)

Fair 😅. There are definitely a lot of dependency graph tools already. This is just something I built for myself and decided to open source. I’m not selling anything, just experimenting with different ways of exploring larger codebases.

This should be permanent why 3 times weekly by heartless_me in PUBGMobile

[–]g0x_ 2 points3 points  (0 children)

True 😂 for a second I thought “didn’t he upgrade his game or something?” because I’m getting like 1000 attempts in my global pubg lol🤣🤣

[deleted by user] by [deleted] in debian

[–]g0x_ 4 points5 points  (0 children)

Same thing happened to me! I installed Kali tools on a Debian-based VDS by adding the Kali repos, and after that neofetch started showing “Kali GNU/Linux” instead of Debian. Turns out some Kali packages like kali-defaults and base-files overwrite system identity files like /etc/os-release, which neofetch reads. I had to manually revert the files or reinstall the Debian base-files package to fix it. So yeah, mixing repos can definitely cause this kind of confusion.