No clue, I've only seen either fully working or physically broken ones. Oldest one I have still has mini-usb and no degradation can be seen. Though I only rescued it this year, it seems like it was used pretty roughly.
And they've been very safe, as far as I've heard. I think generally you can use common sense and be extremely safe all around the world.
Unfortunately there are some exceptions and I believe the highest risk area is India. A lady vlogger on motorcycle was recently gang raped there by 7 men.
I assume this is mitigated by delaying the uploads by a month (which you may need anyway due to sporadic internet access & not always having the time to edit videos).
>For nearly all cases, Django’s built-in template language is perfectly adequate. However, if the bottlenecks in your Django project seem to lie in the template system and you have exhausted other opportunities to remedy this, a third-party alternative may be the answer.
>Jinja2 can offer performance improvements, particularly when it comes to speed.
Although we could say the same thing about Kafka, couldn't we? It's made for much higher throughput and has usually other use cases, but it's also great until it's not great.
At least the last time I used Kafka (which was several years ago so things might have changed) it wasn't at all easy to get started. It was a downright asshole in fact. If you pursue a relationship with an asshole, you shouldn't be surprised when they become cold to you
Also don't underestimate setting up e.g. views or materialized views even that you can use through the ORM to query. It helps a lot and allows you to combine fine tuning SQL with ease of use through Django, and get a lot of performance out of it. Just remember to create them in the migration scripts.
reply