new | show | ask | jobs Github

personjerry a day ago

If you have the raw HTML why would you need to do this at all?

▲

manlymuppet a day ago | parent [-]

I should've been more precise with my words.

What I meant is doing inspect element on the Space Jam website, and doing select all + copy.

▲

futuraperdita a day ago | parent [-]

I think you're assuming a pattern existed in 1996 that didn't actually exist until the 2010s.

In 1996 JavaScript was extremely limited; even server side processing was often limited to CGI scripts. There was nothing like React that was in common use at the time. The Space Jam website was almost certainly not dynamically compiled as HTML - it existed and was served as a static set of files.

Even a decade later, React and the frontend-framework sort of thinking wasn't really a big thing. People had started to make lots of things with "DHTML" in the early 2000s where JavaScript was used to make things spicier (pretty animations, some server side loading with AJAX) and still often worked without JS enabled in a pattern called graceful degradation.

What you'd get from "View Source", or "Inspect Element", and what was literally saved on disk of spacejam.com, was almost certainly the same content.

▲

manlymuppet 20 hours ago | parent [-]

I'm not trying to dispute this though. Although I appreciate the clarity, I am aware of the web's past.

The only point I was trying to make was that this project could be better achieved by an LLM if spacejam.com's HTML is supplied.

For why you'd want to do this rather than simply use the original code is up to the developer, but I'd expect a common reason to be the ease of modern frameworks. Some justifications for making Claude create the same code again in a different framework include:

- Using <script> tags is bad practice in a lot of modern frameworks, and it's better to just translate to React and run your logic directly within components.

- Perhaps you're using TailwindCSS, in which case it's a good idea to port over all the original CSS so you can have unified codebase.

- Hosting on modern frameworks is often conveinent.

- Sometimes (although maybe not for a website this small) the source code with a framework is less verbose.

You probably misunderstood me because I paraphrased "raw" HTML several times throughout my comments in this thread before I actually read the page source and realized it was the original source code.

	▲	garretraziel 10 hours ago \| parent [-]
		I think that the reason why everyone is acting surprised about your suggestion is that the target wasn’t to obtain the page in some higher level framework or anything. The HTML of the page was what the author wanted Claude to output. Would he used source HTML as an input, there would be nothing for Claude to do. Different exercise.