Mixmax | San Francisco or REMOTE | Full-stack engineer or INTERN in Fall '18 | https://mixmax.com/careers
We're a profitable, fast-growing startup looking for full-stack engineers.
Mixmax is the hub for all your business communications. We integrate with your company's existing toolchain - email, calendar, chat, CRM, and more - to bring all information into one place. This means we're syncing, storing, & indexing hundreds of millions events a day into our system, and then building fast APIs and delightful front-end UIs to make the data actionable for our users. Additionally, we have an extensive Developer API (developer.mixmax.com) that powers entire third party products.
“The purpose of estcoin is to accelerate [development of Estonia's e-residency program], while also providing additional funds and interest for the development of our digital nation.”
This minimal (no-dependency) npm package is used throughout Mixmax in browser and server-side code. Check it out, welcome any comments! https://github.com/mixmaxhq/search-string
Major differences I can see (OP feel free to correct if I'm wrong):
Link.fish
* doesn't provide a web crawler
* relies heavily on microdata, schema.org, RDFa, etc
* relies on manual parsers for sites that don't have microdata embedded
* doesn't full-render pages by default (Diffbot renders every page, so it can use computer vision to automatically extract the data)
* doesn't support proxies
* doesn't support entity tagging
Probably plenty more, but that's what jumps out to me at first blush.
--
Since I see other people have mentioned price as a concern, we're always willing to help out bootstrapped startups. Just shoot me an email: dru@diffbot.com
Hard to say and compare in what regard exactly? Price wise, much cheaper. Data wise, it depends. Mainly on in what kind of data you are interested in. Will probably return better results on text-heavy pages, but the data is probably often less "deep". So really depends on the use case. If you have a question to your use case, you can simply write to api@link.fish .
