[muzani]

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.

[mrskitch]

Great point. It's a hard thing to try and succinctly summarize, plus the title _has_ to be somewhat appealing or no one will ever visit it.

It's a bit "damned if you do, damned if you don't" since lots of folks won't click on click-bait-ish links but will gloss over more terse titles.

[piptastic]

Also you didn't respond to the person who did leave a comment. Tough to have a post take off that way.

[mrskitch]

Hrm, it must have slipped past me, I'll take a look!

EDIT: yeah, this is my bad. Totally missed it and it's a great comment too :(

[piptastic]

it's not all bad, you still can :)

[mrskitch]

Appears it's locked now? Can't seem to reply :(