WelcomeWEFreedomWindsorEssexCounty-ActionCommunicationsRalliesResourcesSocialEventsWednesdayNightMeetings-ActivismAgoraAgorismCanadaCommonLawCommunityDataCentersDataCentresDoocracyFarmersMarketIntroductionsNaturalLawNewslettersOntarioOrganizingOutreachProjexProjexWikiRalliesResistanceAnalysisSoireesSoiréesWikiSpooksWindsorElectionsTop Subs
2
internet - - (+2|-1)
Designed to Last: A Manifesto for Preserving Content on the Web(jeffhuang.com)
2 commentsbyLarrySwinger
Add topics

Comment preview

[-]x0x71(+1|0)

I'm going to disagree with him on more than a few points.

Returning to vanilla CSS is correct. For this site in particular I finally adopted Sass/SCSS. Well the killer feature I wanted was nested CSS. That's now supported in normal CSS.

Don't minimize HTML. It probably doesn't matter in any dimension. Like he said, the deflate alg is doing it anyway and it gets undone on the client side. Same thing happens with minification. Go to inspect page and you have a DOM that isn't minified. He claims it's hard for him to debug when it's minified. Why would you touch the minified html? You still have the original non-min version, and on the front end you have inspect page.

End all forms of hotlinking: Absolutely disagree. What you want is redundant hotlinking. But everything this guy writes suggests he never touches a database and only works with static so I guess that's not an option for him. https://img.gvid.tv

Stick with native fonts: I do. In theory if a browser wants to look good they will make good fonts available. In a better world browsers would make it easier for you to pick your preferred serif, sanserif, and mono-font and pages should just render the user's preference unless you have some really niche design they are going for. I don't see how that makes a page more likely to survive though. If you get your font from a public cdn and they decide to close, the browser will still render the same font family if you give it a generic backup. While I agree it seems irrelevant to the central point.

Obsessively compress your images: No! If we are talking about preservation that is the opposite of what you want to do. Then the internet becomes a garbage pile of compressed and re-compressed images. The internet is modern. It serves 4k video multiple frames a second. It can handle a single fucking image at good quality. Again this seems to be more of his general web development preferences which optimizes for a bygone era, more so than anything that has anything to do with the central topic. Yes shinking images is still a good idea for SEO... but at the cost of contributing to a more preserved internet.

Item 7 is a good point.

parentlinkreply
[-]LarrySwinger1(+1|0)

@JasonCarswell

parentlinkreply