This is the correct view. Docker is a company selling some useful products, but the OCI (Open Container Initiative) format is what is interesting, and it can be used with many different tools not just Docker's.
I really don't get the semantic arguments against serverless. The name perfectly describes what it is: an abstraction where the developer doesn't have to worry about a server. It's really that simple.
If you have another model that you think is better, why don't you come up with a name for it, instead of trying to co-op a perfectly cromulent term that is already in wide usage?
I work for a non-profit scientific research organization and we pay for a DockerHub Team subscription. It's where we host almost all of our images. But we also had a small Free Team that was used for one project just to put it in a different namespace, which we now have to scramble to move somewhere. It doesn't make any sense to double our costs just for that one project.
This move by Docker does not inspire any confidence in their long-term management, and will very likely drive us away from DockerHub entirely. It's really sad to watch this company fall from grace. I was an early adopter and always rooted for them from the very beginning.
The fact it was a coronavirus coming over from animals was also highly predictable, given SARS and MERS. There is a fantastic book called Spillover by David Quammen which lays all this out and explains why it was virtually guaranteed to happen.
This format is meant for visualization in 3d, and even though it's lossy, it's "visually lossless" for humans. We to start with the archived lossless stacks (compressed with bz2) for any reprocessing.
What you're suggesting with a lossless movie codec would be a great addition, we just haven't had the need for it yet.
I work with large-scale neuroscience imaging, and this is exactly how we compress 3D image stacks (i.e. 3d volumes) captured with confocal microscopes. Since adjacent frames are usually quite similar, there's a ton of redundancy that H.265 can exploit, and the compression ratios are amazing. For multi-channel volumetric imaging, we use ffmpeg to encode each channel as a movie and then combine all the channels into a single HDF5 file.
Can anyone actually load the website (https://vams.cdc.gov)?
I get a "too many redirects" error, which is quite a bit worse than "the buttons are poorly placed".
Docker Swarm fills that gap pretty well in my experience. The best part is that it's an almost trivial migration to move from Compose to Swarm. Swarm to K8s is not so easy, even with tools like kompose.
I've often found myself wanting something like this, a bootstrap to spin something relatively complex up quickly and then start customizing it. I think it would be nice if there was a way to export to the format native to whatever cloud you're targeting, e.g. CloudFoundry. This is something I've found missing in tools like Serverless Framework.
I see the problem: I read the date in American format (mm/dd/yyyy) and it's dd/mm/yyyy. That's a very confusing date format, yyyy/mm/dd is better as an international format.
Take a look at the Howard Hughes Medical Institute, which uses a well-known billionaire's money for funding basic research in biology and neuroscience.
Thanks a lot for clearing that up! The gateway seems difficult to use without the dashboard, and I gave up on installing the dashboard at the point in the instructions where it said I had to get a trial license. I didn't realize you could keep renewing the "trial", as long as its just a single node. I'll give it another shot, because we might be able to get by with a single gateway, and if not, the non-profit discount sounds promising.