Right, but here's the trick: I can't do the same thing twice. So if I write it ugly the first time, that's the best that's ever going to be. What a waste of its potential! π
psycotica0
I don't think it's the tickling thing. It's a fair hypothesis, but it doesn't feel right to me. To me I think it's the emotional connection of doing something with another person, and the physical connection of two (or more) people working together. Like, I'd say that throwing a ball up into the air and catching it again just isn't as fun as throwing a ball back and forth between people is, and there's no biological imperative there. There isn't a lust for tossing the ball with the boys. But it's a group activity, and group activities fill a different need than solo activities, which is a different biological imperative.
So I think joinking it fulfills only part of the craving, but leaves other parts unfulfilled, which is why as soon as that part recovers the body is like "okay, let's try again"
Even if they don't change laws, and even if they don't resort to anything outright immoral, a large player can pay an up-and-coming competitor $100k for their thing, and then bury it. A $100k windfall might be a big deal to a new entrant, a difficult offer to pass up, while simultaneously being nothing for the existing incumbent. Or less morally you could outbid them for a critical resource they require just to prevent them from having it, when you don't even need it.
There's a lot of power that comes from being able to sustain a loss larger than the other party's entire operating budget.
A classic I needed to send to a friend:

Water fans explain that it is wet.
It feels like "we have 12 months to cash in on the marketing of Open Source, but then 12 months to weasel out of providing the first shred of source"
For an honest answer, from an Open Source perspective, it's mostly auth, profiles, and discoverability.
Presuming I have a GitHub account, when I encounter a library or tool or something that's hosted on GitHub that means I can fork it, make issues, comment on issues, make pull requests from my fork to upstream tied to issues, and generally have seamless interaction with any and all software on GitHub.
Or, if I have my account added to a project, then I can also merge PRs and push to master and be a maintainer of that software without any friction.
When I see that software is hosted on KDE's thing it's like "Ugh". I have to login to that, and create a profile for that, and then figure out how tickets work there, and how do I contribute to that. It's enough to just not, most of the time. And maybe I do that for kdenlive. Then I have a bug for Gimp. Okay, what the heck do they use? Is that another login? How do I contribute over there? Is registration even open? Okay guix, oh boy a mailing list. Do I want to subscribe to a dev mailing list just to submit a 2 line patch? I think I'll just not... I'm sure someone else will fix it eventually......
So besides all that, some people like their GitHub profile, and like that people can see all the things they've contributed to from one spot. That's why it's often linked on resumes, but beyond that there's also a kind of cultural cachet to having a diverse and positive profile, should someone look. If someone is a maintainer of a repo with a lot of stars, that might tell you they're "important" even if you don't know why. Because maybe you're a JS programmer, but this person seems to be big in the Java community, because they seem to maintain a few high profile java libraries.
And then lastly, it's sometimes useful as a shortcut in searching. "Source code" is kind of a useless term for searching, so if I search "ruby Ledger file library" I'm more likely to get some docs or a rubygems page, but if I search "ruby Ledger file GitHub" I'm probably going to get what I actually want, which is a readme and a git uri I can clone and play around with. Or a web view of the source I can search through to debug something without cloning. At least assuming that is what I want, it depends on what my goals are, but it's useful often enough that I do it sometimes as a way of jumping to the source part.
I'm typically anti-centralization, and anti-microsoft, and if we all move away from GitHub I'm sure I'll live, but this is why I like it despite its problems. And sometimes I want a webview of file contents, with search, without cloning, so sue me π
Since you seem like a good person to ask, which version of the movie do you watch when you're craving a watch?
I don't know the original author's opinions on AI, but I think it's still fair to say that it was clearly Copilot's goal to steal all the code and be good, and they had all the code, and so ethics aside one would expect them to have succeeded with flying colour at whatever their goals were, even if those were bad goals.
But they failed instead, which is impressive.
You could check out "FAR: Lone Sails". It's a pretty chill game where you have a machine that you're sailing/driving through platforming actions to the right. It has cinematic feel and a kind of environmental plot, but I don't think there's any way to lose or anything...
And if you like it, there's a sequel "FAR: Changing Tides" that is very similar, but longer and with a more complicated machine to manage.
I could see people being bored with it, there are "puzzles" but they're super light, but maintaining the machine scratches something within me.
I think you're looking for the word "cue" my friend!




Hmm. I've been in math, computer science, and computer programming for 20 years in English (Canada) and I've never heard "denary". It's cute, but never once heard anyone say it. So they're not interchangeable to me π