• 0 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle



  • which will suppress this warning

    “I’m going to be annoying you until you do something about it” It is recommending that you take some sort of action, that choice is up to you as the user. In fact, the older way of disabling the warning was called advice.defaultBranchName

    AFAIK git is still Linus Trovalds’ project and one thing he is known for is “you dont fuckin break user space”. That is acknowledged in the pull request https://github.com/git/git/pull/921

    “will minimize disruption for Git’s users and will include appropriate deprecation periods”.

    Linus is also a fuck-your-feelings kind of guy so deprecation_period == linus_date_of_death. No, I’m not implying Linus is racist/bigot, just that he feels that strongly about breaking user experience.

    Git in of itself doesn’t give a shit about.

    You’re right…and that’s why its unbelievable to me how some people are still (it has been nearly 4 years since that PR above) resistant to change this one little thing. This is just the initial branch that we’re talking about here. Git doesn’t care if you:

    ﬌ git init
    Initialized empty Git repository in /home/xxxxxx/tmp/.git/
    
    ﬌ touch foo && git add foo && git commit -am "foo"
    [main (root-commit) 9c74dd1] foo
     1 file changed, 0 insertions(+), 0 deletions(-)
     create mode 100644 foo
    
    ﬌ git branch -a            
    * main
    
    ﬌ git checkout -b bar
    Switched to a new branch 'bar'
    
    ﬌ git branch -d main
    Deleted branch main (was 9c74dd1).
    
    ﬌ git branch -a
    * bar
    
    ﬌ git log      
    commit 9c74dd18d493fec727e6ce9e4ba71ed356dd970d (HEAD -> bar)
    Author: Butters
    Date:   Thu Aug 22 00:14:44 2024 -0400
    
        foo
    




  • …which you get a multiline message telling you to change your ways (Linus doesn’t break UX)…every time you init…weird.

    $ git init
    hint: Using 'master' as the name for the initial branch. This default branch name
    hint: is subject to change. To configure the initial branch name to use in all
    hint: of your new repositories, which will suppress this warning, call:
    hint:
    hint: 	git config --global init.defaultBranch <name>
    hint:
    hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
    hint: 'development'. The just-created branch can be renamed via this command:
    hint:
    hint: 	git branch -m <name>
    


  • unfair treatment.

    We’re talking about slavery here.

    sick of having to relabel

    It’s not that hard…to be accommodating.

    divorced from the social issues

    from your point of view

    the code doesn’t care

    You’re right. Call it a controller and agent. I know naming is hard, but we’re smart enough to apply our lexicon.

    never use the words master or slave ever again? What’s next??

    Ah, the slippery slope fallacy.

    We still use master over main

    The default for new repositories on GitHub has been main for awhile now. You would have had to put in effort to change it to something else. You’re a stick in the mud.


  • unfair treatment.

    We’re talking about slavery here.

    sick of having to relabel

    It’s not that hard…to be accommodating.

    divorced from the social issues

    from your point of view

    the code doesn’t care

    You’re right. Call it a controller and agent. I know naming is hard, but we’re smart enough to apply our lexicon.

    never use the words master or slave ever again? What’s next??

    Ah, the slippery slope fallacy.

    We still use master over main

    The default for repositories on GitHub has been main. You would have had to put in effort to change it to something else. You’re a stick in the mud.



  • I definitely appreciate your words and completely understand what you’re saying. I finished reading your blog and like your “raw” perspective. You should update it with an “where I’ve been, where I am and where I’m going” post. It feels like a short story, over the span of several years, but you have a bit of a cliff hanger there 😉

    I had a bunch of other stuff written but I removed it because it was scatter-brained and all over the place. I may in fact reach out to you for conversation. While our bearings might not be the same, I think there’s a lot to learn and I like your style.


  • After 25 years in tech I’m starting to look for my “out”. I have a ton of experience with electrical (signals/rf too), plumbing, mechanical, woodworking, finishing, engines, etc There isn’t much I can’t fix. As far as nautical experience goes, I’m a novice but I recently went through a small boat certification course and planning on being a “trailer sailor” for a couple years or more to build up experience. I grew up near Charleston SC harbor, and I think the ocean is calling me back.

    A couple of questions; how do you find work or how does work find you? Do you have a home base where your tools are located or are you doing these jobs in “random” ports you travel to? (You can message me if you don’t want to share your industry secrets publicly 😉 )

    /edit Found your blog so I got some reading to do.




  • /edit I realized that what I was saying before didnt make sense

    Supreme Court appointments are for life (or you quit) and it is generally very hard to replace you. The effect that a replacement on the court has, is upwards of 20 years so the impact is lasting. FTC Chair can be replaced by the President as long as Senate approves. Usually FTC picks are closely tied to the same industry the FTC governs. Its the so called “revolving door” where the CEO of say, Verizon becomes FTC Head or vice versa.