HN user

barneygale

206 karma
Posts4
Comments187
View on HN

$100k buy in at the hedgefund I know. Its a big figure for most but starting salaries, friends & family, and personal loans will get you there.

Surely this is a HN culture bubble? Very few people can borrow tens of thousands of dollars from family and friends to lend to a hedge fund. Not only would I be refused, I'd damage friendships by exposing the moral vacuum at my core.

So if I pushed back on the notion that my identity is a "malignant, parasitic-like condition to which 'white' people have a particular susceptibility" [1], by e.g. stating it is merely "okay", that would be racist?

If you push back on it /using far right slogans/ of course it's racist.

When they see we're not resisting, they'll tone down the rhetoric until we all get along. Because that's what has been happening so far - as we get closer to equality, the rhetoric is becoming milder and milder, right?

The problems that you think you have - that you're not allowed to express yourself in terms of far right slogans - are fucking pathetic and you should be ashamed of yourself for pursuing them. You have been clearly been given a life of privilege, because people who experience poverty or racism don't pick such cringeworthy fights, divorced from the suffering and problems of the real world.

You're leaning 100% into prescriptivism, taking the literal meaning of "It's Okay To be White". The vast majority of far-right slogans are innocuous on a surface reading. The most famous of all - the 14 words - are completely inoffensive if you ignore how they're used.

This is quite basic knowledge for how the far right operates, and so you're either deliberately concern trolling, or you're genuinely ignorant (in which case why are you so sure of your opinions?)

There's nothing at all dehumanising about the phrase "The Poor" (if you think there is, compare to eg “the rich”. Are we dehumanizing the rich every time we call them that?)

Yes. That's why anti-capitalist protests will criticise "the rich" and not "rich people".

I avoid it where I can, but some folks only post videos on youtube. It's much harder for a video-sharing alternative to get off the ground because google (and others in big tech) completely distort the playing field.

If a structural engineer points out that a bridge is unsafe, you don't call them "engineerbrained" and gesture at all the motorists still using the bridge. Why do we accept this bollocks in software engineering? Meta are not trustworthy and it's reasonable to want nothing to do with them.

If people are so upset, why didn't they migrate to something like Debian or SuSE when CentOS got axed?

Many people did. The remainder were too tied up in the RHEL ecosystem (including CentOS) to make the move, but red hat's recent shitcanery will push many more away.

They can both be private methods in a single module, the example still applies fine?

It does, but you're now looking at an edge case that rarely arises in practice in a well-maintained codebase, and certainly not one to design your entire branching/merging/CI strategy around.

If your codebase is a spaghettified nonsense then the problem arises much more often, and so I can understand the use of merge trains/whatnot.

For example, say A is a patch that renames the function foo() to foobar()

Why are you allowing commits to land that break interfaces?

If this is a public function it should go through a deprecation cycle.

If this is a private function then it shouldn't be accessed from outside its module/class/whatever in the first place. If it is, then you've got the "messy codebase" I referred to in my original comment.

You've misread my comment. Whether you rebase on the target, or merge in from the target, the effect is the same. My point is that you only need to do that if you encounter git conflicts that must be solved manually.

If conflicting changes have been merged in, GitLab/Hub will tell you that your branch has conflicts and prompt you to update/rebase on the target branch. That doesn't happen simply because your branch is out-of-date with the target.

Merge queues/merge trains solve a problem that only exists if you require all PRs/MRs to be based on the tip of the target branch. And there's little reason to do that unless your codebase is a total mess.