Technology
Which posts fit here?
Anything that is at least tangentially connected to the technology, social media platforms, informational technologies and tech policy.
Rules
1. English only
Title and associated content has to be in English.
2. Use original link
Post URL should be the original link to the article (even if paywalled) and archived copies left in the body. It allows avoiding duplicate posts when cross-posting.
3. Respectful communication
All communication has to be respectful of differing opinions, viewpoints, and experiences.
4. Inclusivity
Everyone is welcome here regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
5. Ad hominem attacks
Any kind of personal attacks are expressly forbidden. If you can't argue your position without attacking a person's character, you already lost the argument.
6. Off-topic tangents
Stay on topic. Keep it relevant.
7. Instance rules may apply
If something is not covered by community rules, but are against lemmy.zip instance rules, they will be enforced.
Companion communities
!globalnews@lemmy.zip
!interestingshare@lemmy.zip
Icon attribution | Banner attribution
If someone is interested in moderating this community, message @brikox@lemmy.zip.
view the rest of the comments
And just backwards comparability. Web developers aren't going to fix their old site for your new browser, so you'd need to use the ancient convoluted code base to access them.
Unless you're okay with only using the big new websites. Is it most people only use 4 websites regularly?
Weird take. Web browsers are document display systems that got a bunch built on top of them. Old websites are just documents. Web browsers are meant to render them. New websites are a single html entry point that hands all website construction to JavaScript which then creates a fake document in memory for the web browser to render.
Which one is the convoluted, hard to implement and support one?
Example: NYTimes website is literally a giant document. It could be pure html and lose nothing by being rendered on the server side....except capitalism. So it can't be a document because the NYTimes needs to extract a reliable and consistent money stream from people, which means it needs to be enforced (according to them) and thus JavaScript.
I have a feeling that the "ancient convoluted code base" that exists for backwards compatibility isn't convoluted or hard to maintain at all; rather the new features are, because they include everything and the kitchen sink, as necessary for the big new websites.
Plus it's only backwards compatibility due to the feature creep of modern days. Otherwise it would be simply the support of current features.