4 ms·
The post that claimed they blog with "raw HTML" was sending markdown to the front-end with a bunch of javascript for an entire markdown engine that then convert
by culi 2y ago
The post that claimed they blog with "raw HTML" was sending markdown to the front-end with a bunch of javascript for an entire markdown engine that then converted it to HTML
This post claims they blog with raw txt files but it's just really bare HTML with a <pre> tag for the text.
But browser can display .txt files. Both of these posts claim they do something that's simple to do and then don't do it.
Also I'm gonna call it here before it happens. The next post is gonna be "I blog with raw pdfs" and they're gonna ship a whole React SPA with some library that lets you embed a pdf display. It's probably gonna use a metaframework like Next.js for absolutely no reason. Instead of you know... just serving the f'n pdf file
- seangrogg 2y agoThe HTML and <pre> tag is your browser's doing; most browsers are configured to make raw data files easier to digest (FireFox does similar prettification for raw JSON files, for example). The actual data being sent over the networking tab is a "text/plain" document that has no such HTML.
- lgas 2y agoTo elaborate a little more, the commenter above must've done an Inspect Element or otherwise navigated to the live DOM view which is what has the html and pre nodes. If you view source (or look in the network tab) instead, you'll see the plain text.
- culi 2y agoWow you're right. Thanks for the correction!
- Natfan 2y ago> view-source:https://misc.l3m.in/txt/raw_txt.txt https://misc.l3m.in/txt/raw_txt.txt I see no HTML tags, <pre> or otherwise.