Earlier quoted context omitted.
[flagged]
That incredibly condescending phrase should be banned from HN.
It doesn't need to be explicitly imo, it falls short of many of the commenting guidelines.
Using Claude Code: The unreasonable effectiveness of HTML
161–170 of 308 posts
Re: Using Claude Code: The unreasonable effectiveness of HTML
#162I use obsidian MD editor to save important chats I made on Claude or Gemini.
It's the best markdown editor.
So when I need to check any past reference I just open my folder or files.
Html it's so ugly.
I wish IA products add a save al chat button, to avoid copy and paste every response.
Re: Using Claude Code: The unreasonable effectiveness of HTML
#163Web technologies got so many things right. People complain about it so much but it's amazing. I worked with a vibe coded app at my last job (and since quit due to it) and because it was a nextjs SPA frontend with a separate API backend, the user facing urls didn't match the backend endpoints. Because AI uses react hooks for everything, state is in-memory, url-based routing isn't a thing unless you design for it. So l…
[flagged]
Re: Using Claude Code: The unreasonable effectiveness of HTML
#164I built a Markdown viewer https://markant.md to go with the flow rather than against it. I also cooked up a mew format, which basically bundles markdown and images into “Markbooks” https://markbooks.org. LLMs don’t even need an Agent Skill to understand the format, as it is just a zip with and index.md plus assets.
I’d love for people here to consider the idea.
Re: Using Claude Code: The unreasonable effectiveness of HTML
#165I notice this trend where presentations are being made with html. Even I have some prompts that create quick html + JavaScript for data viz. may be it will become our new ppts
Re: Using Claude Code: The unreasonable effectiveness of HTML
#166Earlier quoted context omitted.
Most front end devs can’t get HTML right either.
Modern JS/TS devs probably not, but I wouldn't even call someone a "frontend dev" if you don't know HTML, kind of being a infrastructure engineer and not knowing how any OSes work.
It’s not just knowing HTML as in writing a bunch div tags and patting yourself on the back. If you aren’t able to achieve at least 80% WCAG AA compliance you can’t write HTML.
Most frontend devs have no idea what any of that means. But then it seems everyone who can write 3 lines of code professionally refers to themselves as an ”engineer”.
Re: Using Claude Code: The unreasonable effectiveness of HTML
#167My concern here is that by gravitating to HTML you lose the ability for a human (you!) to easily co-author the document with the LLM. If it’s just an explainer for your consumption, that’s not a concern - but if it’s a spec sheet for something more complex, I deeply value being able to dive in and edit what is produced for me. With a HTML doc it is much harder to do that than with MD. Now of course you could just rep…
I actually think there is a second level to this. Yes HTML will get you most anywhere, but I found that letting the LLM define its own language is also unreasonably effective. Currently working on a dumb little mobile game with isometric view and sound: - told codex to write a tool that lets its place blocks in a prepared three.js document and have chromium dev tools take a screenshot. It made up a little JSON struct…
[flagged]
Re: Using Claude Code: The unreasonable effectiveness of HTML
#168My concern here is that by gravitating to HTML you lose the ability for a human (you!) to easily co-author the document with the LLM. If it’s just an explainer for your consumption, that’s not a concern - but if it’s a spec sheet for something more complex, I deeply value being able to dive in and edit what is produced for me. With a HTML doc it is much harder to do that than with MD. Now of course you could just rep…
Markdown supports inline HTML for interactive elements, I think an interesting potential alternative would be an md doc with a known HTML template and simple build (e.g. single line pandoc command).
Re: Using Claude Code: The unreasonable effectiveness of HTML
#169Aren’t HTML blocks valid Markdown? Why not just put the stuff you need in HTML and keep the rest simple?
Re: Using Claude Code: The unreasonable effectiveness of HTML
#170My concern here is that by gravitating to HTML you lose the ability for a human (you!) to easily co-author the document with the LLM. If it’s just an explainer for your consumption, that’s not a concern - but if it’s a spec sheet for something more complex, I deeply value being able to dive in and edit what is produced for me. With a HTML doc it is much harder to do that than with MD. Now of course you could just rep…
We have been authoring HTML by hand for decades with ease. Text editors are very good at it, and many have commands to auto-wrap, auto-close etc. Reading and writing is simple.
I can code up a complex HTML table by hand faster than I create a basic MD table, but other than that, I find it difficult to achieve a good writing flow with pure HTML, even with all the automation. I author a lot of API docs, READMEs, and how-to guides, and find MD to provide the perfect mix of decently powerful markup and flexibility with supporting raw HTML when needed. The only constraint is that some markup renderers don’t support or severely restrict HTML passthrough (I ran into this with GitHub recently).