duttonw

Interesting read. Would be more interesting to note if the mutations in the offspring were better or worse off.

It is all allege and from a nation that sees saving face above all things. It is not all that surprising.

Someone was playing/checkin out a virus, its in a place which exotic animals are sort after to be consumed. It would not surprise me if someone 'pinched' a couple of bat's from the lab to make some $$$ on the side at the markets and then the rest is how its been portrayed (except for the constant finger pointing its from other countries, china knew about it, they blocked local flights but continued to let international flights out, if you put 1 and 1 together, it does make 2. No way around that.

Nice write up. It still boggles the mind when coming from a Java background how things change but also get worse.

Having zip's (.jar/.war) which had the source and compiled artefacts available and not cluttering the OS with unzip items.

I've run into huge issues dealing with deployments to AWS Lambda nodejs, where the previous developer could not work out how to make a 'slip' deployment and just zipped the whole folder node_modules and all and shipped that, this included all testing tools including an entire browser exe etc. 150mb file expanded to 350mb with 300k in files. And 95%+ of it was boiler-pate to test the api endpoint logic...

I've still not come across the simplest way to have dependences on modules with testing and still be able to deploy a slim zip. There is more and more push to do container layers for the node_modules, but still many of these has 100'000 objects which are not needed causing lambda stutter(startup sleepyness).

I still don't have a clear understanding on when you would need such a thing.

This does not help the people who want to use git for video hosting since it puts the storage and usage back onto a persons credit card again (tho if you come into a line of credit it may be useful).

Hosting on AWS like this does not match the dark web requirements for hiding in plain sight and not easily killable. To spread this over multiple aws accounts and s3 buckets alone would need some form of sts cross linking for the permissions to allow pushing to be granted.

Can you provide a business use case or scenario this would be useable. Else it will continue to have the smell of 'resume driven development'.

To block force push, would also suggest that branch deletion would not work either. Is that the case?

if you left crypto on an exchange, you took a risk, this is the wild wild west.