Show HN: I rebuilt the only parts of my IDE I use, in Rust, over a weekend
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.
29 points by kyle-ssg - 20 comments
Is this something you expect other people to use?
Are you planning to maintain this?
Is this just a joke?
I guess I don't really understand the point of posts like this.
My guess is this made it to the front page solely from the Rust boost.
What's the difference?
You 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.
Just wait for the moment you need to write code for an embedded platform that doesn't have a debugging mechanism.
I've been programming for more than 30 years. Funnily, I used to use debuggers A LOT (in Borland Turbo C++ DOS "IDE" times, Visual Basic, Eclipse, Netbeans, Adobe Flash Builder, etc). But nowadays I seldomly use the debugger, if at all.
Profiling is a tool meant for processes that relate to performance, or hot spots. Debuggers when integrated well[1], are great tools but compete with print based debugging which is a much more general skill one uses and needs to learn.
Let's reserve malpraxis considerations for writing code without any true thought given for security, privacy, accessibility and human rights affected.
[1] and I don't like the interface of any of the debuggers I used. Except maybe in ghci, if I had the patience to script a Tcl/Tk frontend one day.
Debugging and profiling has always been outside of the IDE for me, except when I started out as a Java Developer.