Show HN: Gitdot – A better GitHub. Open-source, written in Rust
31–40 of 322 posts
Re: Show HN: Gitdot – A better GitHub. Open-source, written in Rust
#32Re: Show HN: Gitdot – A better GitHub. Open-source, written in Rust
#33I like the terminal aesthetics but please, for accessibility's sake, make input boxes look more like input boxes and buttons look like buttons.
thank you for the feedback, yeah i've been going and trimming a few places where i think my own tendencies have gone a bit too far. i will also say on accessibility, i recognize the site is a bit too small font in general — and will fix it soon.
Re: Show HN: Gitdot – A better GitHub. Open-source, written in Rust
#34It is ... problematic ... to lead with "anti-AI" and then bury terms like "judicious in our use of it" in the fine print. IMO a team like yours can either: * Use LLMs, in which case you aren't "anti-AI". * Not use LLMs currently, but the non-use is not due to following a principle, in which case you aren't "anti-AI". * Not use LLMs and promise never to do so. I'm happy you are trying something new. But you hurt yours…
hope our sentiment is clearer in the comments that i've made, i think i've made the mistake of phrasing here with the "anti", i'll revisit it.
edit: dang has removed it, apologies for the confusion i caused, that was my mistake.
Re: Show HN: Gitdot – A better GitHub. Open-source, written in Rust
#35> 5. What features will gitdot not have? > AI. > We view AI as an implementation detail — and do not think that using it is necessarily good. > In fact, we think it makes many products worse by acting as a bandaid for poor design. > That isn’t to say we are blind to it, but that we will be judicious in our use of it instead. Not sure I follow. What feature are the developers referring to? I understand that AI will po…
That's not really anti-AI. Anti-AI would mean avoiding it as a value regardless of practicality. That sounds more like anti-enshittification.
Re: Show HN: Gitdot – A better GitHub. Open-source, written in Rust
#36Earlier quoted context omitted.
thank you for the feedback, yeah i've been going and trimming a few places where i think my own tendencies have gone a bit too far. i will also say on accessibility, i recognize the site is a bit too small font in general — and will fix it soon.
Generally probably shouldn’t try to innovate in too many places at once
Re: Show HN: Gitdot – A better GitHub. Open-source, written in Rust
#37I absolutely love the minimalist UI. I see code reviews is in the roadmap, I can't wait to try it.
Re: Show HN: Gitdot – A better GitHub. Open-source, written in Rust
#38Seems interesting an I'll take more of a peek after work, but one thing that stood out to me is the only way back to the home page after navigating to a repo is the back button. Going back to the home page via the back button also doesn't retain that "new" was selected. But I agree with others, I do like the simplicity of the site.
this hn thread is interesting as it feels like i'm getting to revisit a lot of decisions i've made in the design haha. i debated this for a while too, some of my thinking for how it is is that i wanted the focus of a repository page to be _the repository_. so as much as we can, trim things that might detract. it was also done with the intention that it's actually pretty rare for a user to find or explore repositories…
If anything since the keyboard shortcut already exists, you could always put it in little cursor menu at the bottom of the screen. But yeah up to you, I look forward to your progress.
Re: Show HN: Gitdot – A better GitHub. Open-source, written in Rust
#39Seems interesting an I'll take more of a peek after work, but one thing that stood out to me is the only way back to the home page after navigating to a repo is the back button. Going back to the home page via the back button also doesn't retain that "new" was selected. But I agree with others, I do like the simplicity of the site.
this hn thread is interesting as it feels like i'm getting to revisit a lot of decisions i've made in the design haha. i debated this for a while too, some of my thinking for how it is is that i wanted the focus of a repository page to be _the repository_. so as much as we can, trim things that might detract. it was also done with the intention that it's actually pretty rare for a user to find or explore repositories…
But, I wanted to say thanks for posting this and being really open in the comments. It’s hard to get so much feedback so quickly. It’s a firehouse of criticism that’s hard to deal with.
You’re handling it well.