Readit Newsjesseduffield commented on The Future of Redwood Launches Today community.redwoodjs.com/t... · Posted by u/jesseduffield
It appears that RedwoodJS as we know it is being wound down. I've never used Redwood JS but I've watched it from a distance as it was (to my knowledge) striving to be a proper fullstack JS framework akin to rails, which is a noble pursuit. Seems like they had some challenges getting traction and supporting React Server Components and now they're pivoting to a new project which revolves around cloudflare workers.
jesseduffield commented on 1M Lazygit downloads, one embarrassment at a time jesseduffield.com/Embarra... · Posted by u/jesseduffield
I didn't know about Lazygit and this blog post offers no context nor link to a presentation of the project.
For those like me: Lazygit is a "simple terminal UI for git commands" and is located at https://github.com/jesseduffield/lazygit
Good point. I've updated the post to provide context + link
jesseduffield commented on Git-absorb: Git commit –fixup, but automatic github.com/tummychow/git-... · Posted by u/striking
I tried using this tool after seeing recommendations for it, but IME it got the parent commit wrong enough times that the work to undo the damage was more than if I had looked up the commit myself and used `--fixup` instead. So I moved back to this manual workflow pretty quickly.
I prefer having full control over my commit history, and this tool is too much magic for my taste. I'm sure that it could be improved so that mistakes are rare, but I'm not sure I would trust it enough to not have to review its work anyway.
Lazygit has its own built-in approach to this problem which is much more strict than what git-absorb does (it explicitly asks for confirmation if there's any ambiguity). There's an extensive writeup about it here: https://github.com/jesseduffield/lazygit/blob/master/docs/de...