Show HN: I rebuilt the only parts of my IDE I use, in Rust, over a weekend (github.com)
I don't know Rust.
Friday after work I realised that 90% of my IDE time now is just the commit/diff view — and even good IDEs feel heavy for that.
So over the weekend I built a dedicated native tool for just that. Kyde is a macOS git commit + diff editor with one goal: be fast, do Git well.
I'm curious whether anyone else mostly opens their IDE for git operations these days.
It's open source, and there's a signed app in Releases.
22 comments
[ 3.0 ms ] story [ 43.6 ms ] threadYou seem to have one of those three. I’m not sure what your coding background is, but debuggers/profilers are incredibly useful and important, and it’s essentially malpractice for a developer never to use them.
My guess is this made it to the front page solely from the Rust boost.
Is this something you expect other people to use?
Are you planning to maintain this?
Are you making a point about ai capabilities?
Is this just a joke?
I guess I don't really understand the point of posts like this.
But the terminal already has excellent diff and commit tools.
What were your biggest challenges in making this?
Another possible useful feature would be to add "open in system" or similar in the right-click menu for a file, to open the file with whatever application the OS has bound to it.
EDIT: I see there's a plugin thing that when clicked installs the highlighting. Cool!
EDIT: Also missing is selectively staging lines of a changed file to commit. I would actually change the behaviour of the Git UI so that it matches the VSCode one, to reduce the learning curve. Most people already know how that works, no need to make them learn a new UX.
It seems the AI coding is just the software version of Temu. Lots of cheap stuff but none of it is very good and it breaks pretty easily when you try to do anything outside of a very very small list of uses.