Ask HN: If HTML supersedes Markdown fr AI, Will it be versatile enough for devs? | Hacker News Reader

Ask HN: If HTML supersedes Markdown fr AI, Will it be versatile enough for devs?

8 pointszameermfm24 comments

Isn't Markdown's hallmark its versatility while performant? I see there is an increasing call from tech community towards HTML to be adopted instead of Markdown due to its richness in the agentic communication layer. But is it versatile across any kind of interfaces? versatile with different format conversions? and performant (as the md is lightweight)?

View on HN

I believe there is no one way,it is all about context of your work.Also leak of needs provide new versions of what we use.

i do think html will become popular, both will stay relevant

depending on your tooling, editing and viewing html won't be a problem in the slightest and opens up all kinds of possibilities

personally very excited to introduce more html into my docs process

True, they fill a beautiful gap

What do you mean if? The internet is built on html. Markdown is a random flare up of an annoying annotation standard pushed by LLMs. No one used Markdown anywhere near at the scale of html before ChatGPT

Thats a complete reductive idea of MDs. MD was long spawn before LLMs as a need for light weight formatting and easy conversion to different formats. No one used at that scale doesnt mean the absence of the utility for it, as the primary adopters were tech community and that was a layer below the consumer market. Utility obviously stands, the question is, can HTML supersede on that utility side of it in all developer work components.

I said “not used at the scale of html” not “no utility”

So you write a HTML Readme? Markdown is what I write 99% of the time. Unless I am in a rich editor and HTML behind the scenes.

HTML is a communication layer. Hardly anyone is writing it directly. Using React etc. or whatever or even LLM.

No but I should.

My point is: what’s the total number of html files in existence? Billions. What’s the total number of markdown readme files.

lmao

I saw you sitting at -1 karma so I gave you an upvote.

I feel like Markdown stays the human-feindly layer,while HTML/AST becomes the machine-to-machine layer.

True, Machine to machine is interesting to think about

I think its just hype not worth it at all and you want be able to read it clearly from your editot

Yeah, Reading it clearly in the editor - Probably MD to HTML happens in the editor anyway. So what we are dealing with here are a battle between ease of writing, readability and various cost dimensions.

HTML offers more flexibility while markdown is usually easier to create

May be they should coexist for utilities they provide

HTML for human? Markdown for Agent?

Agent to human?

A) Who cares? What performance are you even talking about? Number of tokens?

B) HTML can contain data, layout, and design within a single file. Markdown isn’t comparable. There will be many situations where Markdown can’t do what HTML, so this is overall a silly comparison.

A) Enterprises for one, e.g Rendering of an HTML page vs MD in an AI IDE or even tokens (compounding costs for a communication doc may be billions in a year) B) True, its a subset, nobody is arguing against it. HTML has overheads in terms of stylings. MD in essence is just a straight arrow.

If there is a communication between two points with ultimate low latency way with readability and threshold just enough to have the idea, MD passes that mark. As tokens needs to conserved

Nobody cares about “tokens”

What do you mean by the cost of rendering an HTML page in an IDE? You know those markdown previews are almost always rendered by converting them to an HTML snippet first, right? Also HTML does not need to be styled, the tags have their own semantic meanings just like the various semantic structures of markdown. The styling “overhead”, which gets added so the document is easier to visually interpret for a human, is exactly the same. The only time when styling doesn’t come into the equation is when you directly view markdown source.

Also, latency???

If cost of showing HTML and MD are same in the CPU level for UI, but generation of them costs uneven at AI level (as it should be mathematically), shouldn't the equation be what is the lowest cost to represent something considering the token usage

> Rendering of an HTML page vs MD in an AI IDE or even tokens

MD is usually converted to HTML and then rendered by a webview, which means MD is more expensive.

> compounding costs for a communication doc may be billions in a year

Lol absolutely not. It would be surprising if the "compounding costs for a communication doc" reached $1 a year. I don't think you understand how efficient computers are and how optimized HTML rendering has become.

> As tokens needs to conserved

Not really. No large org is really optimizing for fewer tokens yet.

Reply on news.ycombinator.com