Re:Show HN: Chromda – Serverless Website Screenshots
by cjr on Monday December 30, 2019 @05:05AM
(#21912273)
I hear you. I run Urlbox (https://urlbox.io) and accuracy is one of the hardest parts, as well as scaling hundreds or thousands of instances of chrome since it’s a real memory hog.
I also managed to get a version of the urlbox renderer working on lambda but it fails on some websites due to the /tmp space limits, for example trying to do a full page screenshot of a heavy page like dailymail would use up all of the available disk space in the lambda environment with chrome’s media cache.
Re:Show HN: Chromda – Serverless Website Screenshots
by whoisjuan on Monday December 30, 2019 @11:39AM
(#21914553)
Love what you have done with URLBOX dude! That's my goal standard when it comes to improving accuracy for GetScreenshot. I have tested with your website preview and I think both of our solutions nail accuracy, but you have been longer in this game so you probably have way more edge cases covered. I still find myself trying to address new edge cases every certain time.
Re:Show HN: Chromda – Serverless Website Screenshots
by artur_makly on Monday December 30, 2019 @04:15PM
(#21916789)
We managed to screenshot DailyMail.co.uk very well ..no coding required: https://app.visualsitemaps.com/share/6a79e25354f16408731b860...
I would be curious to see how accurate it is when it comes to rendering. I have a Screenshot as a Service side project (https://getscreenshot.rasterwise.com) that is also build with Puppeteer, but accuracy is a completely different animal.
Out of the box Puppeteer is really not that accurate so you need fine tune it to address a huge amount of rendering edge cases.
This is the area where most services come short imo. I have put a lot of effort into optimizing my service accuracy but it’s a never-ending task. There always seems to be one website that doesn’t render the way it’s supposed to be rendered.
I really don’t understand why headless browsers seem to be developed with UI rendering as a low priority. Simulating a viewport is not equal to simulating an actual screen.