769
firefox rule
(slrpnk.net)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 Nov 2024
769 points (97.5% liked)
196
17560 readers
462 users here now
Be sure to follow the rule before you head out.
Rule: You must post before you leave.
Other rules
Behavior rules:
- No bigotry (transphobia, racism, etc…)
- No genocide denial
- No support for authoritarian behaviour (incl. Tankies)
- No namecalling
- Accounts from lemmygrad.ml, threads.net, or hexbear.net are held to higher standards
- Other things seen as cleary bad
Posting rules:
- No AI generated content (DALL-E etc…)
- No advertisements
- No gore / violence
- Mutual aid posts are not allowed
NSFW: NSFW content is permitted but it must be tagged and have content warnings. Anything that doesn't adhere to this will be removed. Content warnings should be added like: [penis], [explicit description of sex]. Non-sexualized breasts of any gender are not considered inappropriate and therefore do not need to be blurred/tagged.
If you have any questions, feel free to contact us on our matrix channel or email.
Other 196's:
founded 2 years ago
MODERATORS
I will agree with you that VANILLA JavaScript isn't to blame, but all the frameworks and packages are.
Yes, being shitty at their jobs. even the frameworks/packages are not to blame. its which you pick and how you use them.
for peoples context: just checked a few sites most range in the 30MB-150MB per page. which is pretty reasonable for the complexity of the websites involved. one included a streaming service actively playing a video.
Its just that these things add up across 100 tabs.