Lemmy Shitpost
Welcome to Lemmy Shitpost. Here you can shitpost to your hearts content.
Anything and everything goes. Memes, Jokes, Vents and Banter. Though we still have to comply with lemmy.world instance rules. So behave!
Rules:
1. Be Respectful
Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.
Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.
...
2. No Illegal Content
Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.
That means:
-No promoting violence/threats against any individuals
-No CSA content or Revenge Porn
-No sharing private/personal information (Doxxing)
...
3. No Spam
Posting the same post, no matter the intent is against the rules.
-If you have posted content, please refrain from re-posting said content within this community.
-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.
-No posting Scams/Advertisements/Phishing Links/IP Grabbers
-No Bots, Bots will be banned from the community.
...
4. No Porn/Explicit
Content
-Do not post explicit content. Lemmy.World is not the instance for NSFW content.
-Do not post Gore or Shock Content.
...
5. No Enciting Harassment,
Brigading, Doxxing or Witch Hunts
-Do not Brigade other Communities
-No calls to action against other communities/users within Lemmy or outside of Lemmy.
-No Witch Hunts against users/communities.
-No content that harasses members within or outside of the community.
...
6. NSFW should be behind NSFW tags.
-Content that is NSFW should be behind NSFW tags.
-Content that might be distressing should be kept behind NSFW tags.
...
If you see content that is a breach of the rules, please flag and report the comment and a moderator will take action where they can.
Also check out:
Partnered Communities:
1.Memes
10.LinuxMemes (Linux themed memes)
Reach out to
All communities included on the sidebar are to be made in compliance with the instance rules. Striker
view the rest of the comments
This is actually a generational thing. Millennials were taught “PEMDAS”:
But younger generations have been taught “BEDMAS” instead:
Notably, Division and Multiplication are swapped on PEMDAS and BEDMAS, to make this “both happen at the same time” more straightforward. But that only applies if the entire operation can happen at the same time.
For instance, let’s say
6/2(3)compared to6÷2(3). At first glance, they both appear to be the same operation. But in the former, the6dividend would be over the entire2(3)divisor. Which means you would need to simplify the divisor (by resolving the multiplication of2•3) before you divide. So the former would simplify to6/6=1, while the latter would divide first and become3(3)=9.Technically, if you wanted to be completely clear, you would write it using multiple parenthesis as needed. For instance, you would write it as either:
(6÷2)(3)=9or6÷(2(3))=1to avoid the ambiguity. Then it wouldn’t matter if you’re using PEMDAS or BEDMAS.I have never heard of or seen an example of anyone using / and ÷ in different ways. If you want multiple terms in your divisor, either write it as a large fraction with all relevant terms in the dividend or divisor, or use parentheses. This just seems like sloppy notation to me.
The slash was just because MarkDown doesn’t really make mathematical notation easy. The point is that with a slash, the 6 is over the entire

2(3)divisor. It’s the difference between these:You can even see that the automatic solution (in yellow) parses the two differently. In the first example, it correctly resolves the
2(3)first, because you should always simplify both the top and the bottom as much as possible before you resolve the division. But in the second, it parses the6÷2first, because it is left ambiguous. The slash is literally the horizontal bar, putting the dividend above the entire divisor. Except it’s in a single line, instead of taking up three lines of text for a single operation.