Creating an open-source solution to the headaches of headless browsers

Re:Creating an open-source solution to the headaches of head... by maxaf on Monday November 25, 2019 @05:46PM (#21633651)

I dove into the comments to ask the same question. I just did something similar to this with a few lines in my docker-compose.yml, which eventually turned into a few lines in a Helm chart. Why would I pay someone money for something as trivial as this?

Now, I won’t write another rant on the subject of Eternal September, and how our field is increasingly populated by charlatans who can’t do simple things on their own. But yes: that’s exactly how I feel.

[ Parent | on HN ]

Re:Creating an open-source solution to the headaches of head... by avip on Monday November 25, 2019 @05:57PM (#21633767)

Disclaimer: Neither I nor my colleagues or anyone I'm aware of are, were, or ever will, use said service.

Did you divide (time that took you to complete this trivial task + time to document it, version it, explain it to coworkers, maintain it next time chrome decides to break something) * (your $/h cost) / 0.00008 before doing that?

[ Parent | on HN ]

Re:Creating an open-source solution to the headaches of head... by rozenmd on Monday November 25, 2019 @06:00PM (#21633802)

Here's a build vs buy calculator to save you from doing the maths: https://baremetrics.com/startup-calculator

[ Parent | on HN ]

Re:Creating an open-source solution to the headaches of head... by viraptor on Monday November 25, 2019 @10:36PM (#21635465)

This is a dangerous calculator. It misses the cost of deployment, integration, internal support, etc.

(This can be significantly larger for the purchased solution then an internal one as well)

[ Parent | on HN ]