jotto

13 ms·

91.
CloudFront Pre-rendering with Lambda@Edge(github.com)
3 points by jotto 9y ago|0 comments
92.
Prerendering for CloudFront(github.com)
1 points by jotto 9y ago|0 comments
93.
Show HN: Pre-rendering JavaScript apps on CloudFront(github.com)
10 points by jotto 9y ago|0 comments
94.
Show HN: Server-Side Render React Apps on CloudFront (with Lambda@Edge)(github.com)
1 points by jotto 9y ago|0 comments
95.
Brute force search is fast enough(jonathanotto.com)
4 points by jotto 9y ago|0 comments
96.
How Long Does It Take Ruby/Node/Go to Linear Search 200MB?(jonathanotto.com)
3 points by jotto 9y ago|1 comments
97.
Linear Searching 200MB with Ruby, Node, and Go(jonathanotto.com)
2 points by jotto 9y ago|3 comments
98.
How long does it take to linear search 200MB in memory?(jonathanotto.com)
5 points by jotto 9y ago|1 comments
99.
by jotto 9y ago
No pricing info on c5 or whether c4 has changed in either the blog post or https://aws.amazon.com/ec2/pricing/on-demand
100.
by jotto 9y ago
Thank you - I had an overaggressive rate limiter for non auth'd accounts, it's _improved_ now.
101.
by jotto 9y ago
I've been working on something similar: https://www.prerender.cloud/docs/api // URL to screenshot service.prerender.cloud/screenshot/https://www.google.com/ //
102.
by jotto 9y ago
is eul open source?
103.
Ask HN: Should we block non-gzip HTTP bots to reduce bandwidth costs?
11 points by jotto 9y ago|6 comments
104.
by jotto 9y ago
> Under what traditional model would you spawn off an entire server instance for such a minor function I think that's the point - would you rather run your own VPS and manage the logs/errors from a cron job? Or simply write cod
105.
by jotto 9y ago
$7 per 10,000 is $0.0007 per screenshot Get it for $0.000365 per screenshot from me (shameless) [1]: https://www.prerender.cloud/docs/api curl http://service.prerender.cloud/screenshot/https:&#x
106.
by jotto 9y ago
$7 for 10,000 is not that cheap ($0.0007 per screenshot). I'm charging $0.000365 per screenshot and I thought that was on the higher end. https://www.prerender.cloud/docs/api curl http://service.prer
107.
Ask HN: Should we block non-gzip HTTP bots to reduce bandwidth costs?
4 points by jotto 9y ago|1 comments
108.
Ask HN: Should we block non-gzip HTTP bots to reduce bandwidth costs?
1 points by jotto 9y ago|0 comments
109.
Intelligence Reconsidered(mailchi.mp)
1 points by jotto 9y ago|1 comments
110.
by jotto 9y ago
Ditto: https://www.prerender.cloud/docs/api // URL to screenshot service.prerender.cloud/screenshot/https://www.google.com/ // URL to pdf service.prerender.cloud&
111.
by jotto 9y ago
By default: if Headless Chrome hits a redirect to a file:// it returns: net::ERR_UNSAFE_REDIRECT window.location.href = 'file:///' will return console error: "Not allowed to load local resource"
112.
by jotto 9y ago
We've been dealing with scale for over a year at https://www.prerender.cloud/docs/api if you want to try a hosted service: https://service.prerender.cloud/screenshot/https://google.c
113.
How Much Can You Make Mining Ether and How Much Does It Cost to Run?(learn2ai.com)
20 points by jotto 9y ago|9 comments
114.
How Much Can You Make Mining Ether and How Much Does It Cost to Run?(learn2ai.com)
2 points by jotto 9y ago|0 comments
115.
by jotto 9y ago
I've been working on a similar project - if you want a similar solution with a little less setup, navigate to your build/dist directory and: npm install -g prerendercloud-server prerendercloud-server . If you want to run
116.
by jotto 9y ago
<div id='root'></div> <script src='https://cdnjs.cloudflare.com/ajax/libs/react/15.6.1/react.js'></script> <script src='https:/&
117.
by jotto 9y ago
> Crawl a SPA and generate pre-rendered content (i.e. "SSR"). I've been maintaining (thanks to this team and Headless Chrome) a convenience API based on this feature. Some additional features: * React checksums for v14
118.
by jotto 9y ago
(Shameless promoting): for an API version of the prerendering functionality, with no warm-up latency, we're running a large cluster of Chrome headless instances here: https://www.prerender.cloud/
119.
by jotto 9y ago
You could indeed do that, it's just more work. The beauty of server-side rendering a React app in a headless browser is that since the environment is the same as what the app was originally designed for (a browser), things _just work_.
120.
by jotto 9y ago
Because rendering in a Node process is more complicated when async state is involved - using a browser eliminates that complexity. For simpler apps without any async state (AJAX or WebSockets), a Node process may suffice.

More ›