elmigranto

My guess it’s a joke.

Especially for things used directly, you need to understand both, own and third party code, roughly to the same level. With own code, you only care for your own use case; with third-party — you have to kind of get everyone else's.

Depending on what you do and the dependency's scope, either way can make sense.

Third party dependencies are very easy: you just have to intimately know how it is implemented in addition to knowing your own code and stack, and then you are golden!

Nothing to learn, just focus on making your app, it’s all taken care of by This One Simple Package ;)

These things are so far from free as our tooling presents with “just nuget it or whatever”.

Or you can have a single checkbox “Problem with the vehicle”.

Purple tick box is how GitHub formats links to merged PRs and closed issues.

Classic case of "focus on building your app, not infrastructure". Here's another multi-million dollar idea: put this cache directly inside your own video processing server and upload there.

Use managed language, it will handle memory stuff for you, you don’t have to care.

But also read these 400 articles to understand our GC. If you are lucky, we will let you change 3 settings.

Right. That’s why all the software from, say, Microsoft works flawlessly and at peak efficiency.

What if your phone’s kernel panics? :)

> This project […] contains only the necessary parts for realistic benchmarking

> The test program is a simple […] return string

I understand how this is required to measure the effects of sandboxing in isolation. And the result is impressive.

In what ways would you expect performance to be affected when workloads are more realistic as well?

I would guess there is more than one computer :)

Pixar's stuff famously takes days per frame.

So if most of the issues with GraphQL are the same as with the other approach, what is the point of GraphQL that justifies all the complexity?