• 5 Posts
  • 357 Comments
Joined 3 years ago
cake
Cake day: January 13th, 2022

help-circle
  • Well, to reference Julia Evans another time:

    head and HEAD are specifically the third meaning of ‘branch’, i.e. the newest commit on a branch, but can also refer to a commit not on a branch, when in that detached head state.

    And while I’m not enamored with these names either, I can’t think of a word that I like better for this meaning.









  • They do have a history of such things happening, yes, which is why my comment exists in the first place. Normally, I would assume this to just be the result of regular shitty management practices paired with regular shitty profit motives.

    The history makes it look like they might genuinely have a higher motive here, and I’m saying I still don’t think so, because it would be far too petty and I don’t see them benefitting that much from it.






  • The thing is, I really don’t think, Google would care about Firefox. Firefox is sitting at negligible percentages of usage share. The only real competitor to Chrome is Safari and that’s because of iOS.
    I guess, they might impact Safari on macOS with this, but someone would have to try this out to actually see, and ultimately, this could still just be a dumb mistake.

    Having said that, Google holds a near-monopoly in both video content and web browsers. They have a special duty to not disadvantage competitors and even if this was an honest mistake, I do think, it deserves a slap on the wrist.



  • I have my repos on Codeberg and one of the ‘disadvantages’ is that, well, it’s a non-profit, so I genuinely don’t want to waste their resources.
    They ask you to only host open-source repos there, meaning that using it for backups of shitty personal projects, even if I would throw in an open-source license, is just out of the question for me.

    And that has weirdly been a blessing in disguise. Like, if it’s not useful for humanity to see, do I really care to keep it around forever?

    And I’ve had three projects now where I felt an obligation to push them over the finish line of actually making them a useful open-source project. Which had me iron out some of the usability shortcuts I took, made me learn a good amount of code quality stuff and of course, just feels good to complete.


  • It looks similar in structure to JSON:

    {
        "attr": {
            "size": "62091",
            "filename": "qBuUP9-OTfuzibt6PQX4-g.jpg",
            ...
        };
        "key": "Wa4AJWFldqRZjBozponbSLRZ",
         ...
    }
    

    So, it might be some JSON meta language. I just find it weird that it seems to contain all data, so you wouldn’t use this for validating or templating JSON.

    But ultimately, it also means with a handful of regex replacements, you could turn this particular file into JSON. Might make building your own parser almost trivial…