Just another..
...piece of innovation that Microsoft see as a threat and are forced to chase the innovation AGAIN. Still cant think of anything that corporation have invented themselves
Microsoft has released Technical Preview 3 of Windows Server 2016, including the first public release of Windows Server Containers, perhaps the most interesting new feature. A container is a type of virtual machine (VM) that shares more resources than a traditional VM. “For efficiency, many of the OS files, directories and …
Caveman invented wheel.... OMG Ford, VW, Audi saw it as a threat and were forced to chase the innovation AGAIN.
With that brain-dead pattern of thinking, we'd never end up with any kind of standardization. In which case, the internet would not exist, computers would still be based upon 8 bit processors, and we'd probably be living in the world of "Fallout" style technology - with you reading this on a green CRT display.
Linux is no different, do you think things like KVM and Docker were original? Get real.. Containers have been around for decades, just because they are suddenly "cool" doesn't make them innovative.
I see some really good uses for Containers, they won't replace Virtualisation - but we might just be looking at the next generation of software installation and deployment systems (Note I've only recently started playing with Docker, but installation of Docker containers is painless!)
> we'd never end up with any kind of standardization.
We certainly won't wind up with standardization from Microsoft. Docker images for Windows won't run on any current (non-Windows) implementations.
> computers would still be based upon 8 bit processors,
8-bit computers were rather late to the mix, and were not originally intended to be computers anyway.
Seen this before, too many half baked ideas and chasing after hot youg things means they take their eye off security and stability. I hope they don't assume that they can release an continuous stream of patches and treat server like win 10 clients.
I wish they would fix the carp they have now and if I sound bitter, it's because today I can't print to the laser cutter, whereas yesterday I could and it's nowt to do with the laser. You would have thought MS could get printing working reliably in 32 years, but maybe not.
On server 2016, do you still have to stop the spooler service, navigate to the burried print queue, delete spool files and restart the service when print jobs get stuck or do you still require a 1980's style reboot?
"On CUPS" Really, never had that problem.
I think your loyalty to one platform or another is overiding your reality. Can you come over and fix my Windows install where it's decided to crash the spooler service when I attempt to engrave an enclosure, it was fine on Sunday, but I think it decided to take the bank holiday off.
It always used to be my impression that a computer program was supposed to do the same thing each time it is run, not occaisionally take the day off.
>"On CUPS" Really, never had that problem.
You never had that a problem so no-one else should either? And vice versa for your Windows problems. Puh-lease. I'm ready to admit that bad drivers can cause the Windows spooler to stop, and I've cleared Windows spoolers many, many times in my career. But I've had to do that to CUPS as well.
Just a random example: Archlinux instructs to fix stopped printers like this:
If all jobs sent to the printer become "stopped", delete the printer and add it again.
It is unfortunate that the Windows Docker Containerization will follow the Docker API, but br made "proprietary" in not being able to intergrate or be interactice with Docker Containers from Linux.
Will the Microsoft Docker Containers have same features and functionality as those in Linux Docker and BSD Container technologies? Will Microsoft docker containers preempt Docker develoers from using any relevant technology tools - as is possible in Linux Docker development, to only those specific Microsoft only tools?
In part, this is a return to making Open Standards technologies proprietary and fixed only to software from commercial by companies like Microsoft in a crass attempt to "force" users into their IT "lock-in", as usual.