mrskitch

21 ms·

151.
by mrskitch 8y ago
Hey Tim! Nice to see you here! I agree with your points overall, especially the disposable containers as they’re super hard to keep up. The CPU and Memory notes are accurate as well — except for canvas intense sites (which makes sense). Tha
152.
by mrskitch 8y ago
Ouch, thanks for the heads up!
153.
by mrskitch 8y ago
You’d actually be surprised by the applications, I definitely was. Some I’ve seen: - Screenshots - PDF generation - Functional tests - Regression tests - Scraping SPAs - Crazy stuff like printing user-generated content for personalization p
154.
by mrskitch 8y ago
Right - probably repeating some stuff already out there. The main issue I’ve been seeing on puppeteers slack channel is folks who are totally new, and don’t read the docs, so trying to help all devs effectively
155.
by mrskitch 8y ago
Hey folks! I'm Joel, entrepreveloper behind this browserless.io service, happy to answer questions or chat!
156.
by mrskitch 8y ago
Very nice! It's amazing to me how many developers just run headless wo any sort of service-layer. You're gonna have a bad time :(
157.
Observations running 2M headless sessions(docs.browserless.io)
315 points by mrskitch 8y ago|84 comments
158.
Browserless pay-per-use and functions are coming soon(docs.browserless.io)
1 points by mrskitch 8y ago|0 comments
159.
by mrskitch 8y ago
Definitely: https://docs.browserless.io/docs/chrome.html#launching-with-... . I still need to write some form of docs on how to handle the auth window properly in puppeteer, but it's definitely possible
160.
by mrskitch 8y ago
I agree with what @codegeek has said, and would like to outline a few more pointers: - It's important to solve a problem you've either deeply experienced or passionate about. Having a deep passion will help you build something tha
161.
by mrskitch 8y ago
I was wondering the same as it’s a common use-case for the project I run (browserless.io). Seems to be a big demand for sane PDF rendering and generation. Been pretty interesting seeing webtech handle these kinds of problems
162.
by mrskitch 9y ago
My sentiment here is that modern JavaScript is _much_ better than its predecessors. The real issue, as it pertains to the web browser, is supporting legacy functionality that's causing drag on the web as a whole. I'm curious: what
163.
by mrskitch 9y ago
I’ve literally just helped someone do similar in their own product. If you run into issues with puppeteer’s blank or missing pages of a screenshot (for high-res images), just forgo that for canvases base64 export. It’ll save you a world of
164.
by mrskitch 9y ago
Version 1.0 was a very very simple hosted headless image running on a few VM's. At that point there wasn't any debugger or notifications about your sessions. Pretty much just a submission form that provisioned machines to support
165.
by mrskitch 9y ago
I started https://www.browserless.io/ when I found out that there wasn't a good hosted solution for headless-browser work. There's a ton of other higher-level services that do things like screenshots and pdfs, but
166.
by mrskitch 9y ago
Apologies on not replying, I seemed to have missed your comment. Money comes in two ways: hosted plans on browserless.io and via commercial licensing. Happy to answer any more questions you have
167.
by mrskitch 9y ago
Have you seen _my_ startup ( https://browserless.io/ ). The stability part is something I’m trying to solve once and for all with this project.
168.
by mrskitch 9y ago
I maintain a puppeteer-as-a-service repo here: https://github.com/joelgriffith/browserless . It’s pretty feature rich at this point, allowing you to specify concurrency, sessions timeouts, and comes with a robust IDE (w
169.
by mrskitch 9y ago
I've started one after listening to a lot of indiehackers podcast's. Mine is https://browserless.io , which is IaaS, and I just hist ~$1k/mo at about the 3 month mark. Still not providing the majority of my income,
170.
How I've Grown My Headless Browser Business to $1,000/mo(indiehackers.com)
5 points by mrskitch 9y ago|0 comments
171.
by mrskitch 9y ago
If you're looking to roll your own HTML rendering https://browserless.io/ is great for doing just that and allows you to use puppeteer to do the HTML generation. You could even go so far as to remove all unnecessary JS
172.
by mrskitch 9y ago
I don't have much to add, except to say that this landing looks incredible. Well done!
173.
by mrskitch 9y ago
I do agree with you (we should be tackling problems that have plagued humanity since we've been a species). I think it's just incredibly tough to find motivation when the cards are already stacked against your from the start. Larg
174.
by mrskitch 9y ago
Playing devil's advocate: I'm assuming that's because the things you have listed don't have a lot of (or any) laws/regulations around them. At least not to the degree that fixing wealth distribution does. Can you im
175.
by mrskitch 9y ago
Would love to talk more about this if folks are curious and why I made the decisions I did, just drop a comment and I'll happily discuss.
176.
Show HN: Headless Chrome as-a-service(github.com)
3 points by mrskitch 9y ago|2 comments
177.
by mrskitch 9y ago
I should note that this doesn't lock you into any particular lib, just solves the problem of running on Chrome in a service like fashion.
178.
by mrskitch 9y ago
I’d recommend puppeteer or some other Chrome driver. It’s fast and resilient even on single page apps. If you’re looking to run it on a Linux machine also take a look at https://browserless.io (full disclosure I’m the creator of
179.
by mrskitch 9y ago
Just started seeing issues as well on Comcast: http://downdetector.com/status/comcast-xfinity seems like there's potentially large issues rn
180.
Launch HN: Browserless. Hosted headless Chrome(browserless.io)
7 points by mrskitch 9y ago|0 comments

More ›