Tell HN: ChatGPT has 13B revenue but can't make a working website

4 points by 0xbadcafebee ↗ HN
People talk a lot about AI being really great. But can OpenAI use it to make their own website work?

The ChatGPT performance is terrible, and has been for months. I use ChatGPT on both a Mac M3 w/32GB RAM, and a AMD Ryzen 7 PRO 7840U (w/ Radeon 780M) & 32GB RAM. After I have been using a single ChatGPT page/thread/whatever to do research for a day or two, it becomes insanely slow, locking up the browser for minutes at a time. The only recourse is to stop the page, kill the tab, and re-open the page, and hope ChatGPT is done doing whatever is locking things up. So I end up literally "exporting to JSON" whatever i've done, and opening a new thread, pasting the JSON there, just so I can continue my research/planning.

Example screenshot (where it's locking up even while trying to file a bug report): https://imgur.com/a/JfEXocr

I have reported this same bug for months. There is no indication anyone has seen these reports or is working on it, no customer service or feedback. It's like putting a letter in a bottle and tossing it out to sea.

Forget the potential impact to the environment, the economy, to jobs, the world, etc. The thing that pisses me off the most about AI is how hard is it to make a website that doesn't lock up the browser?! Like what exactly is their web page even doing that it has to suck up this many resources? I'm not doing 3d rendering here! I just need it to show me text for god's sake! This is the opposite of rocket science, and yet these bozos can't get this right? Why would anyone trust them with anything important?

2 comments

[ 2.6 ms ] story [ 12.4 ms ] thread
It's well-known that ChatGPT sucks on Firefox. They don't care.
The problem is that instead of using widely documented and implemented web languages that are built into the browser and can run natively without a translator, unskilled web devs opt to use random web modules provided by adware vendors to simplify the implementation of complex animations, fonts, and UI/UX and "vibe" coding functions. This modules are not often built for memory management and garbage collection (the opposite actually)

But I mean, you're part of the problem by heavily utilizing the same LLMs responsible for suggesting the use of ridiculously heavy modules ran at every page load and bloated front ends instead of fostering skilled programmers who write things from scratch, improve them over time, optimize them because they actually care about resource management, etc...