←back to thread

549 points thecr0w | 1 comments | | HN request time: 0s | source
Show context
manlymuppet ◴[] No.46186353[source]
Couldn’t you just feed Claude all the raw, inspect element HTML from the website and have it “decrypt” that?

The entire website is fairly small so this seems feasible.

Usually there’s a big difference between a website’s final code and its source code because of post processing but that seems like a totally solvable Claude problem.

Sure LLMs aren’t great with images, but it’s not like the person who originally wrote the Space Jam website was meticulously messing around with positioning from a reference image to create a circular orbit — they just used the tools they had to create an acceptable result. Claude can do the same.

Perhaps the best method is to re-create, rather than replicate the design.

replies(4): >>46186464 #>>46186518 #>>46186769 #>>46186982 #
blks ◴[] No.46186518[source]
What do you mean? Raw html is the original website source code.

Modern web development completely poisoned young generation

replies(1): >>46186910 #
manlymuppet ◴[] No.46186910[source]
I'm using source code like it's used when referring to source code vs executables. React doesn't simply spit out HTML, nor the JSX used to write said React code, it outputs a mixture of things that's the optimized HTML/CSS/JS version of the React you wrote. This is akin to source code and the optimized binaries we actually use.

Perhaps the wrong usage of "source code". I probably should've been more precise. Forgive my lack of vocabulary to describe the difference I was referring to.

replies(2): >>46187021 #>>46187653 #
1. pastel8739 ◴[] No.46187021{3}[source]
For a website from 1996 though, there’s a very good chance that the page source is the source code