That's a really great suggestion and I feel a bit silly for not having thought of it. (FWIW, there is a test form on the RapidAPI site, but it's more complicated to try and not as fun.) We'll add that. Thank you!
Hi, one of the authors here. We originally built this link preview API for our own apps. (A link preview shows a summary of the page referenced by a URL. Given a link, our API will return the corresponding title, author, publisher, and so on.) Since it worked well for us, we figured why not make it available to everyone?
The reason we decided to build our own (there are several out there) is that we wanted to pull all the data a publisher wanted to share, including all the media, and we wanted it to be fast. Specially, we wanted to edge cache that data as aggressively as possible given the source.
Hopefully, others find this useful. Let us know if there are features you'd like to see. We also launched this on RapidAPI, so let us know if you've had good or bad experience using that platform. This is our first API launch, so we're still figuring out the best way to do this. Thank you!
In fact, our thesis in this article is not about REST at all, but the design goals of projects like Falcor, which may be unrealistic. And it's those unrealistic expectations of what's possible are why people are turning from HTTP.
Technically speaking, with respect to the whole argument that React is “just a library,” part of the problem is that it isn't perceived that way by many developers. The first auto-complete option (for me anyway) when I type “Web Components vs…” is React.
That said, the developer experience around Web Components is meh. Part of our frustration is that it would have been cool to see Facebook invest all the effort into Web Components-based technologies instead of going off on their own.
Right. And then when those features aren't available in the browser, that's used as a justification going back to proprietary (aka native) platforms. It's a circular argument made by people determined to return to the days before we had an Open Web, for whatever reasons. If you don't want to use the features, nobody is forcing you to do so.
Not on the list, and I'm not a physicist so from that standpoint, I may not have gotten everything right. Still, I'd like to think Qubit would pass muster.
That may be deliberate, since it's not really understood. Robert J. Sawyer's Neanderthal Parallax series and Factoring Humanity (which is listed for a couple of other reasons) also hinge on quantum computing to one degree or another.
Short version: Convince great software developers to work mostly for stock options ($150K for 3 employees) and “harass [them] into programming day and night,“ while selling promises that they will need to back up with working software.
The amount of risks everyone in this story took is pretty psychopathic. It's not sane, but those are the people who make it big. Those are the people we reward. Those are the people who get away free when the entire mortgage industry collapsed in 2008.
...and for everyone one of these success stories, there are probably 8, 10...12 or more stories of people who totally failed and ended up with $200k in debt still paying it off from failed startups.
There's a side not talking about on Hacker News and it needs to be.
Hey, that's what I thought too, but you do need someone to sell customers and investors on the concept. Also it sounds like he had a huge product and project management role as well.
Is it so much of a stretch to believe that a vendor might believe it is in their best interest to control the application platform? Why give Apple the benefit of the doubt here? Ironically, one reason to do that is that Apple is active in defining and implementing Open Web standards, many of which are aimed at improving the Web as an app platform. Which, in turn, is exactly why this is still an “interesting narrative”--both Web and native are rapidly evolving.
I think it is in their best interest to control, but I've seen that spun as the end not the means. Apple's ultimate goal is not control of the app ecosystem, but to improve end-user experience. Control is a necessary part of that.
And the narrative I'm referring to is web VS. native. like one is going to kill the other. We keep talking about this battle but there is no winner, each has their place. period
