BarraCUDA Open-source CUDA compiler targeting AMD GPUs

Re:BarraCUDA Open-source CUDA compiler targeting AMD GPUs by viraptor on Wednesday February 18, 2026 @06:33AM (#47059941)

I do that because there's no point in anyone seeing the pre-release versions of my projects. They're a random mess that changed the architecture 3 times. Looking at that would not give anyone useful information about the actual app. It doesn't even give me any information. It's just useless noise, do it's less confusing if it's not public.

[ Parent | on HN ]

Re:BarraCUDA Open-source CUDA compiler targeting AMD GPUs by panzi on Wednesday February 18, 2026 @07:39AM (#47060361)

I don't care about anyone seeing or not seeing my unfinished hobby projects, I just immediately push to GitHub as another form of backup.

[ Parent | on HN ]

Re:BarraCUDA Open-source CUDA compiler targeting AMD GPUs by butvacuum on Wednesday February 18, 2026 @08:47AM (#47060868)

you should push to a private working branch- and freqently. But, when merging your changes to a central branch you should squash all the intermediate commits and just provide one commit with the asked for change.

Enshrining "end of day commits", "oh, that didn't work" mistakes, etc is not only demoralizing for the developer(s), but it makes tracing changes all but impossible.

[ Parent | on HN ]

Re:BarraCUDA Open-source CUDA compiler targeting AMD GPUs by panzi on Friday February 20, 2026 @09:00AM (#47088152)

Yeah, I don't care about that for my tiny hobby projects which are used by no one. XD

[ Parent | on HN ]

Re:BarraCUDA Open-source CUDA compiler targeting AMD GPUs by bravetraveler on Wednesday February 18, 2026 @11:17AM (#47062631)

I don't care about backing up unfinished hobby projects, I just write/test until arbitrarily sharing, or if I'm completely honest, potentially abandoning it. I may not 'git init' for months, let alone make any commits or push to any remotes.

Reasoning: skip SCM 'cost' by not making commits I'd squash and ignore, anyway. The project lifetime and iteration loop are both short enough that I don't need history, bisection, or redundancy. Yet.

Point being... priorities vary. Not to make a judgement here, I just don't think the number of commits makes for a very good LLM purity test.

[ Parent | on HN ]

Re:BarraCUDA Open-source CUDA compiler targeting AMD GPUs by freakynit on Wednesday February 18, 2026 @11:41PM (#47070001)

I literally keep this in my bash history so i can press up once and hit enter to commit: `git add *; git commit -m "changes"; git push origin main;`

I use git as backup and commit like every half an hour... but make sure to give proper commit message once a certain milestone have been reached.

Im also with the author on this on squashing all these commits into a new commit and then pushing it in one go as init commit before going public.

[ Parent | on HN ]