Wait, but if you have, for example an HTTP API and you listen on a unix socket in for incoming requests, this is quite a lot of overhead in parsing HTTP headers. It is not much, but also cannot be the recommended solution on how to do network applications.
Oh shit, the persona guy was right! We should all be adding license to our comments, so could not legally train model that are then used for commercial purposes.
Lol, something felt off, but I just wasn’t sure if I mistyped something until I saw this comment.
This is the real big-endian way. So your things line-up when you have all of these:
file_dialogue_open
file_dialogue_close
file_dropdown_open
file_rename
directory_remove
If I were designing a natural language, I’d put adjectives after the nouns, so you start with the important things first:
car big red
instead of
big red car
Aaah, AI training data. That makes sense now
But whats the point of giving out a license along the comment? Are you giving permission to use your comment?
why do you provide a link to creative commons license? Ive seen such links few times on lemmy.
Ah, makes sense. Have you tried library genesis?
VN? Virtual network?
You are not alone. This is the work git was built for.
There is a bit of benefit if you have code reviewed so separate commits are easier to review instaed of one -900 +1278 commit.