It could be the way it's presented too. What does "headless Chrome as a service" even mean?
When I look at the Github link, I actually understand what it does: "Severless Chrome on your own infrastructure. Each session gets its own clean Chrome context for total isolation. After the session is complete Chrome is shutdown. You can also think of it like a database connection where your app connects to browserless, runs some work, and gets results back."
But it's fair. Titles are hard and HN shuns clickbait.
When I look at the Github link, I actually understand what it does: "Severless Chrome on your own infrastructure. Each session gets its own clean Chrome context for total isolation. After the session is complete Chrome is shutdown. You can also think of it like a database connection where your app connects to browserless, runs some work, and gets results back."
But it's fair. Titles are hard and HN shuns clickbait.