view the rest of the comments
196
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.
Why not lix?
honestly, because nix the language is bad and unnecessary. nix the community/nix the system is one thing, and lix adresses that, but my basic gripe is that they decided to make a new language when so many already exist, then make it the most weird, inconsistent mess since c++.
what's inconsistent about nix?
Have a look at Guile Scheme like Guix uses and see what consistency can look like.
consistency is in the eyes of beholder i guess. i personally don't think scheme is much better consistency-wise. maybe except the consistent use of parentheses...
well, for a declarative language it has taken on a lot of procedural constructs. then there's the right-associativity on some structures, currying that looks like nesting, and oddities like recursive definitions. it uses a lot of different building blocks, is what i'm getting at.
i see that as nix being inconsistent with the tradition of functional languages, which is fair. but i don't think there are many internal self inconsistencies?
of course it's all based on opinion when it comes down to it, but the recursive vs regular dicts feel inconsistent. the conditionals all seem to have slightly different syntax as well.
i think it comes down to them not being able to decide if they wanted a dsl or a generalist language, and landing somewhere inbetween. they could just have hooked up a lua interpreter, or gone config-only, but instead we got yaml anchors with logic in them.
i always assumed they wanted something that's lazy-by-default and relatively simple, because that's what nix feel like to me. and using a language they control probably makes things like evaluation caching simpler? also nix is turing-complete so i wouldn't consider it a dsl.
if you hate recursive attrs you can always use
lib.fix (self: { ... })i think it started out as one, right? it just feels like a classic case of greenspun's tenth to me.
My thought as well, Lix is amazing if only for its governance