20 comments

  • Jeremy1026 4 months ago

    > Screensaver — Ambient coding display for your workspace

    A coworker years ago screen recorded themselves coding something, then made it their screensaver. Then would just let the screensaver make it look like they were working when they wanted to goof off. This would be prefect for them.

    • throwawaymobule 4 months ago

      Would work nicely as one of the tools called by the hollywood program.

  • aunderscored 4 months ago

    This looks really cute. I wonder if it'd help with reviews when people have strange PR's

    • fastasucan 4 months ago

      Oh, this is a good use case.

    • beezlewax 4 months ago

      Exactly my thought on this.

  • mannanj 4 months ago

    is it able to actually discern the order in which the code was written? would be cool if not to augment it or create a parallel to to actually track this in the manner the code author actually did to write the code - I wonder which functions he/she went to, how he/she wrote code, how long they paused to think, and even what they were thinking!

    • arach 4 months ago

      that's a nice idea. i wonder if applying a bit of ai summarization / grouping logic could help present changes in logical sequences regardless of time or file proximity

      would probably also make sense to add quick review actions in place - like ask a question to the gitlogue tool or the author during the playback

      • mannanj 4 months ago

        maybe we could just record the screen and work backwards from there. I don't even know why we still use git when we have near unlimited data at our exposure for things like this to create newer better tools.

  • jquaint 4 months ago

    This is cool! It feels fresh and new.

    Suggestion for the related projects section: https://gource.io/ Tree view visualization of git history over time.

  • NiloCK 4 months ago

    Finally some external tooling to justify my microcommit habit. (They will play in order here, presumably, instead of the top-to-bottom per-file playback of large commits).

    Really nice - thanks for sharing.

  • alwi4 4 months ago

    I like it! It's a neat idea :)

  • surmoi 4 months ago

    I thought about such a solution for teaching recently, so I'll try it for the next class :D

    I don't mind live coding for students, but it often diverges a bit, I'd rather stick to what's on the repo I prepared with atomic commits.

  • hresvelgr 4 months ago

    This could genuinely be a very useful tool for digesting pull requests. A tiny language model could probably do a decent job of ranking hunks by importance to enable replaying back in a more coherent order.

  • iJohnDoe 4 months ago

    Actually, looks really cool! Creative idea.

  • ripped_britches 4 months ago

    Weird but fun

  • rglover 4 months ago

    This is insanely helpful for debugging other people's code or code you've long since forgotten.

    • throwaway127482 4 months ago

      How is it more helpful for debugging compared to just looking at the git patch? As far as I can tell, this is meant to be more of a cool presentation type thing, rather than something to assist with development

      • eichin 4 months ago

        Yeah, sounds like something I'd use along with Gource for presentations - gource is great for "show off our progress in the last year" in a Very Visual way (without actually being all that useful, but sometimes you need some non-technical visualizations.)

      • fragmede 4 months ago

        Pretty graphics and visualizations help people understand things because humans aren't LLMs. The web didn't have to evolve past having one font, black, on a white screen, but it did, because people aren't robots.

      • fastasucan 4 months ago

        Because looking at a lot of code at once can be overwhelming, also gokng commit for commit can make it hard to track the flow of everything.