mrskitch

10 ms·

1. 31.▲
   by mrskitch 6y ago

   Wow this is almost identical to what we use at browserless.io. I’d be curious to hear how switching SSL termination went as that seems to be the hardest “reproducible” part of it, and copying over certificates is kinda scary. The only thing
2. 32.▲
   by mrskitch 6y ago

   This is how we framed it at browserless.io. Libraries generally aren't a product, and even though some of them do a lot, it's hard to charge folks for an `npm i`-style product. I tried a lot to look into this and it just didn&#x
3. 33.▲
   by mrskitch 6y ago

   Yes: often the case is that JS does some kind of data-fetching, API calls, or whatever else to render a full page (single-page apps for instance). With Github being mostly just HTML markup and not needing a JS runtime we could have definite
4. 34.▲
   by mrskitch 6y ago

   Thanks for the mention! I'm the founder of browserless.io, and agree with pretty much everything you're saying. Our infrastructure actually does procedure for some of our scraping needs: we scrape puppeteer's GH documentation
5. 35.▲
   White whale hunting: finding and fixing a slow Node.js memory leak(docs.browserless.io)

   2 points by mrskitch 6y ago|0 comments
6. 36.▲
   by mrskitch 6y ago

   Hey, I work on browserless.io, which supports both puppeteer and selenium. Selenium uses a chatty HTTP interface, whereas puppeteer/playwright use WebSockets or pipes to communicate. Under-the-hood, however, Selenium is simply using ch
7. 37.▲
   by mrskitch 6y ago

   Thanks for the mention (browserless.io)! Really enjoying this site, let me know if you'd like a guest post and I'd happily add something. We've gathered a few weird tricks and tips as well. Definitely a lot that can be shared
8. 38.▲
   by mrskitch 6y ago

   Yeah, you can definitely think of it like that
9. 39.▲
   by mrskitch 6y ago

   Hey folks, Joel here (creator of Quik + browserless.io). Quik came about as an attempt to stop spending time on IE support... but still support it when you have to. A vast amount of my "frustration" time as a developer was getting
10. 40.▲
    Show HN: Quik – Internet Explorer as a Service(quik.dev)

    36 points by mrskitch 6y ago|10 comments
11. 41.▲
    Show HN: Quik – Internet Explorer as a Service(quik.dev)

    6 points by mrskitch 6y ago|1 comments
12. 42.▲
    How Browserless.io Screencasting Works(docs.browserless.io)

    2 points by mrskitch 6y ago|0 comments
13. 43.▲
    by mrskitch 6y ago

    I pretty much stole Mike's business model, and peppered in some cloud-y saas for browserles.io. I'm almost done with year 3, and will hopefully hit 500kARR this year. Mike's story was a lot of inspiration for me, and I think
14. 44.▲
    by mrskitch 7y ago

    Thanks for that! Appreciated! I have another person help with support now, but I really enjoy the dev stuff so I jump on those. It’s what got me here in the first place :)
15. 45.▲
    by mrskitch 7y ago

    Thanks for the heads up!
16. 46.▲
    by mrskitch 7y ago

    Thanks for posting. I run browserless.io on DO, and want to keep it that way. Many have posted about about how they use DO for small projects, and I started that same way, but now it's the muscle behind a much bigger thing. Appreciate
17. 47.▲
    by mrskitch 7y ago

    Loneliness is a big issue for sure. When I started browserless, it was very much that way. In all honesty when I open sourced the project it helped quite a bit, and it’s nice to hear both good and bad feedback versus wondering if folks like
18. 48.▲
    by mrskitch 7y ago

    FWIW you can run non-headlessly: https://docs.browserless.io/docs/chrome-flags.html#setting-h...
19. 49.▲
    by mrskitch 7y ago

    Just to follow up, you can use our /scrape API to do this: curl -X POST \ https://chrome.browserless.io/scrape \ -H 'Content-Type: application/json' \ -d '{ "url": " https:&#x
20. 50.▲
    by mrskitch 7y ago

    Thanks again for the questions. Please do email me if I happen to overlook anything: joel at browserless dot io
21. 51.▲
    by mrskitch 7y ago

    ++ getting the wordage on _what_ it does and why you'd use it can be tough.
22. 52.▲
    by mrskitch 7y ago

    I felt similar, thanks for echoing the sentiment.
23. 53.▲
    by mrskitch 7y ago

    Hey! Great to see you here! We’re you with knotch?
24. 54.▲
    by mrskitch 7y ago

    The protocol is pretty easy, I think coordinating the necessary “enable” calls is a bit cumbersome. Also the legacy JSON protocol is harder to support, but I understand why. Hardest part is debugging crash issues and why they happened. You
25. 55.▲
    by mrskitch 7y ago

    Interesting, I’ll take a look and see if our markup is encoded improperly.
26. 56.▲
    by mrskitch 7y ago

    Noted ;)
27. 57.▲
    by mrskitch 7y ago

    I spent ~4 hours on my 10th wedding anniversary debugging a production issue. It's not a fun thing to talk about, and doesn't get a lot of attention, but the truth of the matter is that when things are bad _they are bad_. I can se
28. 58.▲
    by mrskitch 7y ago

    I've definitely come across your site multiple times, and I can say with absolute certainty it's helpful!
29. 59.▲
    by mrskitch 7y ago

    Wow, you said this so much better than I could, thanks for chiming in
30. 60.▲
    by mrskitch 7y ago

    Commute was nearly 3 hours for me back when I had to do it. I'd say being remote certainly can help, but has it's own drawbacks as well. For instance, if you're already programming and working 8+ hours a day in your home, the