Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
juped
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
22 ms
·
271.
▲
by
juped
3y ago
more to the point, it's useful to be able to do it via soft pressure on private banks rather than hard power
272.
▲
by
juped
3y ago
Tell me more about the spectre of the nonsense world where everyone sits around starving to death because they're too wealthy and food is too cheap. Or don't, I've heard it hundreds of times, and it's still nonsensical,
273.
▲
by
juped
3y ago
No, because it's a boogeyman. The world should get richer, and things should get cheaper. Creating wealth is good.
274.
▲
by
juped
3y ago
but my rocketship emoji
275.
▲
by
juped
3y ago
This was a concrete example. I didn't know what "vanity URL" meant here, I read the concrete example, and now I do.
276.
▲
by
juped
3y ago
You've caught me in a dastardly logic trap! Now I can never present anyone evidence for the beliefs of the FSF/GPL-user social cluster. You should try arguing in court for FSF legal theories on linking!
277.
▲
by
juped
3y ago
Really bizarre to bring out the snarl word "entitled" over... the persistence of false legal theories?
278.
▲
by
juped
3y ago
I don't agree with you but I appreciate you providing me with comments like this to cite when I try to convince people "yes, FSF are really that maximalist; no, that's not a 90s relic they moved on from".
279.
▲
by
juped
3y ago
it doesn't, full stop, but the FSF has been pushing its maximalist theories which would not survive a second in court for decades now. what may be more relevant is that the use of the GPL is evidence that the author (possibly) believes
280.
▲
by
juped
3y ago
Calling C functions like open() requires unsafe code.
281.
▲
by
juped
3y ago
in fact way safer, since it doesn't rely on the unsafe-riddled std::fs!
282.
▲
by
juped
3y ago
it's not even super weak evidence, just the prior against turnip-abducting aliens is so strong
283.
▲
by
juped
3y ago
lots; the tongue-in-cheek name is "evil merge" but it's honestly pretty common precisely because, as you say, the mere textual merge could be a broken result. "conflict" is a bad name because it sounds like some kin
284.
▲
by
juped
3y ago
diff(old, new) is sort of a degenerate case of diff3(left, base, right) where left = base; if your patch came _from_ git in some capacity it can identify base and doesn't need to fall back
285.
▲
by
juped
3y ago
It's _a_ way that an algorithm found out of the infinitely many edit scripts representing the same change; the underlying nitpick in this thread is that an algorithm found it and maybe it's not a great choice (we've likely al
286.
▲
by
juped
3y ago
It's the reality, it's just applying diffs. The OP's blog actually has an earlier post about how applying diffs uses a 3-way merge; before ort and its more versatile API which can handle just applying diffs, rebase literally
287.
▲
by
juped
3y ago
> It gets a little weird with merge commits, but maybe you just say it’s stored as a diff from the first parent of the merge. Depending on the specific operation it can act like a diff from any of the parents (though the first is special
288.
▲
by
juped
3y ago
How does this "run up against reality", it is the reality, full stop, not even eliding tricky details. Whatever made you say that is the part of you that's confused here.
289.
▲
by
juped
3y ago
i used to think cgi-bin was a "bin" to put your cgi scripts in (i mean, they were perl, not binary)
290.
▲
by
juped
3y ago
And yet plenty of people repost the same unfunny xkcds over and over to an endlessly delighted audience.
291.
▲
by
juped
3y ago
This is a tragic, wrongheaded move, and I say that as a big Git enthusiast (but a Github hater, to be fair...) I don't think PyPy gains anything from this, not even a reduction in the annoying messages that have been psychologically to
292.
▲
by
juped
3y ago
Note that when (other people's, surely, not yours) bad git history with unrelatedly-broken commits everywhere means you can't bisect, you can use bisect --first-parent to travel down only the first-parent history (which should be
293.
▲
by
juped
3y ago
The experience of splitting in git could be made nicer in a few ways, but yeah.
294.
▲
by
juped
3y ago
> interrupt flow sorta. this really varies strongly from person to person and i wouldn't generalize. but you can construct small commits after you're done with your work. > contain intermediary trains of thought that aren&#x
295.
▲
by
juped
3y ago
You're not curious; you're trying to wage an editor flamewar and are confused that I'm not. I'd jokingly say "ed" or "windows notepad" except you'd earnestly try to explain to me that vi or emacs
296.
▲
by
juped
3y ago
Misattribution or failure to attribute is a species of fraud , it has no relation to copyright.
297.
▲
by
juped
3y ago
Extensive binary packages would have been nice back in the years when Gentoo was a meme OS; CPUs were a lot slower and not multicore. I don't have a use for them now. Anyway, the best OS is the one you already know how to use.
298.
▲
by
juped
3y ago
No, see, I don't accept the moral rights of authors as legitimate. See my original comment. Because I don't accept these rights, I don't think "compensating" someone by putting restraints on others would be at all l
299.
▲
by
juped
3y ago
The financial rights are the good part. People should be paid for their work; this is how to get the incentives aligned and promote the progress of science and the arts. Making them into incredibly long-lived rent fiefdoms is bad, and the t
300.
▲
by
juped
3y ago
The problem is the clash between the American concept of copyright (copyright is economic; it's a method of paying authors for their contributions to the public domain) and the European (copyright is the enforcement of an author's
More ›