kus

u/colorado@programming.dev
0 posts · 21 comments

Recent posts

No posts.

Recent comments

on Git 2.48 released · c/linux · 1 pts · 1y

The big change in my opinion is we don't need to tell newcomers about git checkout at all. Git switch --create is much better.

on Forgejo Release v8.0.0 · c/forgejo · 4 pts · 2y

I love that reading the PR comments teaches me something about git itself as opposed to idiosyncrasies of some proprietary git forge.

Removing sql server support is ok. I doubt anyone is spending money on awl server with a free and open source git forge. PostgreSQL is fine.

That's the really nice thing about a subscription model the way jetbrains puts it you don't have to keep moving the chairs on the deck or keep shuffling the UI elements around to get a steady revenue. I am sure moving to rust will help Microsoft cut its cloud / azure cost I mean at some point it costs Microsoft money even though it owns azure.

as always, the answer is it depends. I've worked on B2B websites where you can't even see the real pricing until you sign in so it is impossible for that application to add a guest checkout. it really depends on your requirements.

I create a new branch locally with git switch --create, pull everything from main, sacrifice a small squirrel, and run the project to make sure everything still works.

If something doesn't work or I can't figure out how to resolve conflicts, I quietly switch back to my previous branch like nothing happened. That problem is for future me.

I wish the premium paid features were available for free on public repos. I mean my public repos are not real free and open source projects. I'm just learning and playing around but if you let me use premium features maybe some day I can pester my boss to get them at work