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”.
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.
We have over a 100 places now, and are getting ready for closed beta in September. You can sign up by emailing [email protected] or DM-ing us on Instagram @doggable.app.
Sounds interesting, but what are good examples of "Visualizer" part? Screenshots section [1] only has 6 (pretty primitive [2]) images out of about a 100 total, but maybe that is outdated?
Given that `int + bigint` throws in JS, this exact thing will never happen imo, otherwise, you can't differentiate between types.
Maybe something like `{"x": 10n}`, but at that point, might as well do reviver, especially if you already agreed on a format and use some to parse out class instances vs plain objects.
