this post was submitted on 02 Apr 2025
193 points (95.7% liked)

196

2892 readers
2798 users here now

Community Rules

You must post before you leave

Be nice. Assume others have good intent (within reason).

Block or ignore posts, comments, and users that irritate you in some way rather than engaging. Report if they are actually breaking community rules.

Use content warnings and/or mark as NSFW when appropriate. Most posts with content warnings likely need to be marked NSFW.

Most 196 posts are memes, shitposts, cute images, or even just recent things that happened, etc. There is no real theme, but try to avoid posts that are very inflammatory, offensive, very low quality, or very "off topic".

Bigotry is not allowed, this includes (but is not limited to): Homophobia, Transphobia, Racism, Sexism, Abelism, Classism, or discrimination based on things like Ethnicity, Nationality, Language, or Religion.

Avoid shilling for corporations, posting advertisements, or promoting exploitation of workers.

Proselytization, support, or defense of authoritarianism is not welcome. This includes but is not limited to: imperialism, nationalism, genocide denial, ethnic or racial supremacy, fascism, Nazism, Marxism-Leninism, Maoism, etc.

Avoid AI generated content.

Avoid misinformation.

Avoid incomprehensible posts.

No threats or personal attacks.

No spam.

Moderator Guidelines

Moderator Guidelines

  • Don’t be mean to users. Be gentle or neutral.
  • Most moderator actions which have a modlog message should include your username.
  • When in doubt about whether or not a user is problematic, send them a DM.
  • Don’t waste time debating/arguing with problematic users.
  • Assume the best, but don’t tolerate sealioning/just asking questions/concern trolling.
  • Ask another mod to take over cases you struggle with, if you get tired, or when things get personal.
  • Ask the other mods for advice when things get complicated.
  • Share everything you do in the mod matrix, both so several mods aren't unknowingly handling the same issues, but also so you can receive feedback on what you intend to do.
  • Don't rush mod actions. If a case doesn't need to be handled right away, consider taking a short break before getting to it. This is to say, cool down and make room for feedback.
  • Don’t perform too much moderation in the comments, except if you want a verdict to be public or to ask people to dial a convo down/stop. Single comment warnings are okay.
  • Send users concise DMs about verdicts about them, such as bans etc, except in cases where it is clear we don’t want them at all, such as obvious transphobes. No need to notify someone they haven’t been banned of course.
  • Explain to a user why their behavior is problematic and how it is distressing others rather than engage with whatever they are saying. Ask them to avoid this in the future and send them packing if they do not comply.
  • First warn users, then temp ban them, then finally perma ban them when they break the rules or act inappropriately. Skip steps if necessary.
  • Use neutral statements like “this statement can be considered transphobic” rather than “you are being transphobic”.
  • No large decisions or actions without community input (polls or meta posts f.ex.).
  • Large internal decisions (such as ousting a mod) might require a vote, needing more than 50% of the votes to pass. Also consider asking the community for feedback.
  • Remember you are a voluntary moderator. You don’t get paid. Take a break when you need one. Perhaps ask another moderator to step in if necessary.

founded 2 months ago
MODERATORS
 
top 23 comments
sorted by: hot top controversial new old
[–] [email protected] 8 points 1 day ago

How close are we to RISCV chips having comparable performance to consumer proprietary chips?

[–] [email protected] 12 points 1 day ago* (last edited 21 hours ago) (3 children)

It's beyond my mind that x86(-64) survived to this day. It's so inefficient

Edit: to clarify: I know nearly nothing about processors, so maybe the architecture isn't really that inefficient. All I know is that after Apple switched to its own ARM-based chips, the programs could run faster using the same or less energy. Even with the compatibility later

[–] [email protected] 13 points 1 day ago (1 children)

Well, legacy compatibility.

[–] [email protected] 4 points 21 hours ago (1 children)

This is one that way too many people forget about, to switch to something else, you'd need to emulate x86 for the software that hasn't or do without. Emulation causes overhead and performance reduction, and doing without seems fine on paper until you encounter software you want or more crucially need and can't use it because it hasn't been ported, isn't open-source, or can't be ported due to heavy use of x86 assembly.

[–] [email protected] 2 points 19 hours ago

On the other hand, nobody ever will fix, update, or port many pieces of software if backwards compatibility is expected to be kept up indefinitely.

I'm frankly not sure which is better. Do it the apple way, force projects to make their software work on modern platforms, and just accept that some people will really be fucked over for the sake of progress. Doesn't sit right with me, but on the other hand things can't keep being compatible forever.

[–] [email protected] 6 points 1 day ago

It's efficient on a macro scale. Imagine if every piece of software on the planet had to be recompiled and tested for each flavor of the month risc processor?

[–] [email protected] 1 points 1 day ago

Eh, the backend's pretty decoupled from the ISA, it's the frontend of these chips that's needlessly complicated.

[–] [email protected] 17 points 1 day ago* (last edited 1 day ago) (1 children)

I’m all for open ISAs, but one of these can be licensed at reasonable rates and the other sued AMD for making the 64-but instruction set architecture that Intel should have made.

[–] [email protected] 3 points 1 day ago (1 children)

help who's who? there's three mamufacturers in the meme and I'm woefully uninformed

[–] [email protected] 7 points 1 day ago (1 children)

Arm licenses ISAs and designs. It doesn’t manufacture anything.

[–] [email protected] 2 points 1 day ago (1 children)

sorry, right. I still don't know who sued AMD, I assume intel?

[–] [email protected] 2 points 21 hours ago

It was Intel. Stagnating CPU monopoly they are.

[–] [email protected] 33 points 1 day ago (4 children)

I'm fully ready to switch to RISCV when compatibility and performance match x86_64 and ARM

[–] [email protected] 13 points 1 day ago

Don't forget about also having a matching open-source GPU unless you want shit performance for graphics too.

[–] [email protected] 14 points 1 day ago* (last edited 1 day ago)

Match? That's unlikely to happen anytime soon (or at all)

[–] [email protected] 19 points 1 day ago* (last edited 1 day ago)

Ah, so in about 20 years then sad lol

[–] [email protected] 15 points 1 day ago

I dont even need it to match, just be usable.

[–] [email protected] 22 points 2 days ago (1 children)
[–] [email protected] 31 points 1 day ago (1 children)

AMD has done a bit of open source driver and software stuff, but their chips aren't any more open AFAIK.

[–] [email protected] 5 points 1 day ago

Yeah thats what my understanding was as well.

[–] [email protected] 3 points 1 day ago (1 children)
[–] [email protected] 5 points 1 day ago (1 children)
[–] [email protected] 1 points 18 hours ago

I liked him in the 2/sqrt(2) = sqrt(2) meme.