mrskitch

24 ms·

1. 211.▲
   by mrskitch 9y ago

   I hear a lot of folks mentioning the pain working with headless chrome. This was the inspiration for Navalia, which is inspired by the API from nightmare. It also handles the case where you want to run simultaneous scripts by using new tabs
2. 212.▲
   by mrskitch 9y ago

   I'm working on a high-level API to solve a lot of what you're describing. It's still in its infancy, but soon will be runtime agnostic: https://github.com/joelgriffith/navalia . File an issue for what&#x2
3. 213.▲
   by mrskitch 9y ago

   This type of high-level scraping is what I'm trying to achieve with https://github.com/joelgriffith/navalia , but also handle use cases like JavaScript SPA's. Interesting how differently some libraries/ru
4. 214.▲
   by mrskitch 9y ago

   I've written a fair bit about it. We use it at AppNexus internally for our UI's, and it simply maps back to a REST API. Since each API has its quirks and oddities, it's a nice abstraction layer for consistency. http:/&#
5. 215.▲
   by mrskitch 9y ago

   I'm employing a similar strategy for my library https://github.com/joelgriffith/navalia as I couldn't find any solution to manage headless chrome (plus the API for that protocol is pretty heavy). Building for
6. 216.▲
   by mrskitch 9y ago

   Right, so my particular use-case is scraping SPA's for meta since they don't initially have it on load. Because this can be slow (thanks a lot JavaScript), I needed a way to parallelize multiple instances so my app remains snappy.
7. 217.▲
   Show HN: Navalia – Queue and manage headless chrome(github.com)

   4 points by mrskitch 9y ago|3 comments
8. 218.▲
   by mrskitch 10y ago

   Not the Bible in its typical sense, but Crockfords "JavaScript: The Good Parts". It's like the Bible in that I seem to learn something new on every read through, and it's fairly quick to do so
9. 219.▲
   Show HN: CashCloser, a full react-native app with all the trimmings

   2 points by mrskitch 10y ago|0 comments
10. 220.▲
    by mrskitch 10y ago

    The idea was rather intriguing, however I haven't ran into perf issues in clients yet where this would be beneficial.It does sort of negate one of the benefits of the spec, which is human-readable static queries. It did very much feel
11. 221.▲
    2016 GraphQL Conference takeaways(joelisawesome.com)

    3 points by mrskitch 10y ago|2 comments
12. 222.▲
    Lessons learned wrapping an existing API in GraphQL(joelgriffith.net)

    2 points by mrskitch 10y ago|0 comments
13. 223.▲
    Require JavaScript files the sane way: with symlinks(joelgriffith.net)

    1 points by mrskitch 11y ago|0 comments
14. 224.▲
    by mrskitch 11y ago

    You do realize you're using an app from a phone with this service? I'm pretty sure paying in cash won't do much in this case...
15. 225.▲
    by mrskitch 12y ago

    I've spent some good time on: https://github.com/appnexus/sicksync It's a one-way syncer utility in Node, and backed by a CLI. I Was tired of Ruby file watchers running rsync and waiting the seconds it took f
16. 226.▲
    by mrskitch 12y ago

    This is the first iteration, looking to just get UX feedback and initial impressions.
17. 227.▲
    Show HN: An isomorphic deal-aggregator built with Node and React(dealbait.me)

    2 points by mrskitch 12y ago|2 comments
18. 228.▲
    by mrskitch 12y ago

    Quick summary of why here: http://joelgriffith.net/announcing-sicksync/ Feel free to submit an issue (obviously)!
19. 229.▲
    Show HN: Sicksync, a one-way file-system mirror that's incredibly quick(github.com)

    6 points by mrskitch 12y ago|1 comments