mrskitch

11 ms·

1.
by mrskitch 7mo ago
I enjoyed reading the first few chapters, but wanted a PDF as well. I run browserless.io, so threw a quick script together to PDF-ify this. Gist is here: https://gist.github.com/joelgriffith/0e6a2a774317e845206ca8d... .
2.
by mrskitch 2y ago
This seems decent in Theory, though I'm not familiar if GraphQL mutations can handle conditionals. Cool idea though, but that might be a deal breaker for a lot of folks
3.
I Ripped My Open Source Product Apart for a Complete Rebuild
13 points by mrskitch 3y ago|1 comments
4.
Browserless.io Now Supports GPU's(browserless.io)
2 points by mrskitch 3y ago|0 comments
5.
Browserless Now Works in LangChain(browserless.io)
3 points by mrskitch 3y ago|0 comments
6.
Using browserless.io to train your LLMs(browserless.io)
10 points by mrskitch 3y ago|0 comments
7.
How to horizontally scale headless Chrome(browserless.io)
9 points by mrskitch 4y ago|0 comments
8.
We pick puppeteer over Selenium almost every time(browserless.io)
6 points by mrskitch 4y ago|0 comments
9.
by mrskitch 4y ago
Thanks for that -- we did have quite a few good conversations over emails. I did read each personally and respond to them. Didn't justify the means.
10.
by mrskitch 4y ago
Hey folks, Joel here, I'm the original maker behind browserless. You've seen us before on HN -- I'm very sorry for this situation. We didn’t intend to SPAM you or send unsolicited emails, we just wanted to ask for feedback. B
11.
by mrskitch 5y ago
Wanted to say that browserless was on this podcast recently, and was great experience. I’d definitely recommend others do it as well
12.
by mrskitch 6y ago
Just JS for now since it compiles and runs entirely in the browser
13.
by mrskitch 6y ago
You’ve got it: the core service listens for inbound Upgrade http requests, starts a browser, then funnels the connection into the browser. This debugger simply sits on top of all that, and puts the code/execution context in the browser
14.
by mrskitch 6y ago
You can use our demo debugger (the address is in this blogpost). It might not match your version of puppeteer exactly, but it’s a close enough proximate that it’s still valuable
15.
by mrskitch 6y ago
Yup, There’s a lot going on here. Currently the tool uses a fixed IP for the running browser. That’s why you’re seeing that Cloudflare issue. As far as the hovering goes, the canvas element is “mirroring” interactions back through to the un
16.
by mrskitch 6y ago
Sure! Puppeteer is a node-based library, and pretty much all the web-apps out there that let you run puppeteer code do it in an elaborate node sandbox. This tool gets around that by running puppeteer in your own browser, making it a lot fas
17.
by mrskitch 6y ago
Just familiarity with puppeteer, eventually this tool will support both. Puppeteer has less “moving parts” for now
18.
by mrskitch 6y ago
You can actually install our docker image or use the npm module: https://github.com/browserless/chrome/blob/5627f1ef041ec23f3...
19.
by mrskitch 6y ago
Hey, Joel here, mostly responsible for this tool. Happy to answer questions — one thing not well covered is getting puppeteer to run in the browser, especially a webworker. Can talk more about it if there’s interest!
20.
The new browser-based puppeteer REPL, and how we built it(docs.browserless.io)
91 points by mrskitch 6y ago|30 comments
21.
by mrskitch 6y ago
This is exactly the same thought I came to with browserless.io. There simply wasn’t enough traffic to make informed decisions, and when there was it was really silly things (small copy changes and the like). Eventually we just tore it all o
22.
by mrskitch 6y ago
> But from a legal perspective that is not even close to the same thing. Very true. However, my rebuttal would be that the majority of folks reading this are of an engineering background, and seeing the words “no longer open source” can
23.
by mrskitch 6y ago
> This means that Elasticsearch and Kibana will no longer be open source software. This is categorically not true. The source is open, and will likely always will be. It’s not free for AWS going forward, however. Why is it that Amazon ha
24.
by mrskitch 6y ago
I think dual licensing is possibly the best way to go, if your product mitigates a risk. It's why we went that way with browserless.io Truth be told selling a small library probably isn't enough to make significant money on your p
25.
by mrskitch 6y ago
I’ve seen some of these trends in browserless.io as well. Good thing you went full time back in January! I postponed going full time on browserless until just a few days ago. I’m still a bit worried about how next year will shake out. Even
26.
Running Browserless.io in Production [audio](runninginproduction.com)
1 points by mrskitch 6y ago|0 comments
27.
The leap of faith: going full-time on browserless.io(indiehackers.com)
2 points by mrskitch 6y ago|0 comments
28.
Tell HN: Most recent Docker release breaks Docker-machine create
2 points by mrskitch 6y ago|0 comments
29.
by mrskitch 6y ago
I suppose it's open core. Open Source is hard because you have to separate people from their money even though the code is "free." I'm not saying it's _the_ answer, but browserless.io isn't VC backed, and it ce
30.
by mrskitch 6y ago
My own opinion: I think there is as a marketplace. Years ago when I started browserless.io, I wanted to find a way to sell access to the core image of ours. Docker kinda has/had a marketplace, where you can buy access to curated and se

More ›