u/BlockOfDiamond

"Oh, Schist!"

This post contains content not supported on old Reddit. Click here to view the full post

This post contains content not supported on old Reddit. Click here to view the full post

This post contains content not supported on old Reddit. Click here to view the full post

This post contains content not supported on old Reddit. Click here to view the full post

This post contains content not supported on old Reddit. Click here to view the full post

I am not well versed in traditional gender roles, but unless having a death wish is somehow considered manly, there is absolutely no reason for wearing a helmet to be seen as "cowardly" or "unmanly." If your head comes into contact with pavement at speed, no matter how tough you think you are, the pavement is going to win that interaction. Wear your helmet. The number of videos of people I see crashing their bikes or skateboards attempting silly stunts, and they are not even wearing helmets, is astounding. Wearing a helmet is not "showing weakness" but acknowledging physics. Physics always wins.

I am not sure what exactly these people mean by "manly" but if they mean confident and resilient, then wearing the helmet proves you are secure and self-confident and smart enough to not risk your life for the sake of social validation or "appearing tough."

This terrible voting system is responsible for our "number two" party system that everyone hates. Accordingly, there is no "red" and "blue" in this system, just brown, because "number two" of course.

This post contains content not supported on old Reddit. Click here to view the full post

This post contains content not supported on old Reddit. Click here to view the full post

So I made a greedy-ish voxel mesher that does unfortunately emit quads with T-junctions like every greedy mesher does. However, I have yet to notice any horrible cracks between the T junctions. Does this mean I got away with that? Or are they just going to appear if someone runs my game on an earlier GPU. In case this matters:

• I am using camera-relative rendering for good precision.
• Vertex-in-chunk coordinates are exactly representable values in FP.

If someone wrote, say, 1.234e5 instead of 1.234 x 10^5 on an exam, would you dock points, or is the abbreviated scientific notation fine in your opinion? What are the pros and cons of "e" notation acceptance?

https://preview.redd.it/7edzzzuijpbh1.png?width=1024&format=png&auto=webp&s=76a948371ac8253b32a7bc9132846fb6a40dac05

Why do people say you should not use dpps or _mm_dp_ps? Seems like a great way to take dot products.

Republicans/right-wing people, even if most of your beliefs are aligned with the right, are there any particular issues that you agree with the left on?
Democrats/left-wing people, even if most of your beliefs are aligned with the left, are there any particular issues that you agree with the right on?

While there is a case to be made about not compressing too much logic into cryptic one-liners, a lot of people seem to go too far in the opposite direction, and act as though "longer" means "more readable" no matter what. Their code is still not readable if theirs is overly explicit, verbose, and redundant code that buries meaning in unnecessary ceremony. Good readable code is concise and clear without wasting my time wading through obvious ceremony to extract meaning. Some of the worst offenders I see are things like:

if (x > 10) {
    return true;
} else {
    return false;
}

Instead of just:

return x > 10;

Like, seriously, just stop. The short version communicates the actual intent of "return whether x > 10" directly. That is straightforward and not "clever." Turning one crystal clear line into five for no reason is absolutely not helpful. The longer form indicates that the programmer does not understand how conditional expressions work. Go learn, instead of infantilizing the codebase.

The short form is literally quicker to understand once you already internalize that conditions like x > 10 already produce values of true/false even for beginners. The expanded version is not helpful and can actually reinforce the misconception that conditions are somehow tied to if or somehow different from literal true/false values themselves.

This is just one of the more egregious examples, but yeah, stop assuming longer is automatically more readable, or that shorter is automatically less readable.

What if someone moved to a an exoplanet planet hotter than the eutectoid temperature, and then built their house out of austenite?

Why do some people write:

if (x > 10) {
    return true;
} else {
    return false;
}

Instead of:

return x > 10;

Performance aside, I think the shorter version is actually more readable due to not having as much visual clutter to parse, and is the most direct way to express the intent of "return the result of the comparison."

However, some people write the first version. Why is that?

I have noticed a large portion of posts, particularly from new users, are reposts from months or years ago. Sometimes they comment on their own posts, but the comments themselves are plagiarized top comments from the original post they stole.

Another pattern I often see is crossposts from newly created subreddits, often "shopping" related, whose stated purpose has nothing to do with "oops" related posts.

The purpose of r/oops is NOT to drive fake engagement with low-effort recycled content.

To help keep posts original and authentic, I am considering a few things:

• Instituting account age/karma requirements. Normally I am opposed to this sort of thing, but a LOT of the new-user posts are karma farming bots. New user posts would be held up for review.
• Banning crossposts, or writing an automod script to only allow crossposts from whitelisted communities.

But what are your thoughts on these? Is there anything else we could try?

P.S. Thanks to everyone who reports inauthentic posts. Keep them coming.