One of the main issues with the 'foo is large threads loading slowly. The page will show instantly but you can't interact for a few seconds. This is because of the javascript iterating each post and doing heavy work. On small threads it's not noticeable until the post count reaches ~500. This happens regardless if you enable a setting or not for example: filters dates, embeds, and media settings. On every page load it could hypothetically iterate 1000 posts, run heavy regexes, add a bunch of events to many buttons (each post could have (5-10), do the same for images. It quickly adds up when you have a large amount of posts, and this is actually fine but not good enough for large threads.
After a few features I have planned, I'm going to look into optimizing the javascript. For anyone curious: Instead of rendering all posts at once I will only process them as they come into view. For any buttons, instead of individual handlers on each button I will have a single top level listener to intercept all events and this could be the greatest improvement dropping a potential ~5000+ listeners to just one! A single page on the 'foo could eat 100MB but with these changes it will improve a LOT. I'll do this incrementally so first I'll do the latter fix as it's the simplest in theory, and I'll do my best to accurately measure and profile the changes in loading time and memory requirements.
I was told to post more and share a devlog or something
Love you all anons.
