If you find it necessary to compare Rossi to Tesla to support your point, I think Rossi is the clear winner of the exchange.
You will never reach the denialists with facts and logic.
Seriously, what's so broken about X? Is it just a pain in the ass for developers to work with?
You might seek out some of the tech talks given by Wayland developers. They lay it out pretty clearly.
Here's a good one: https://www.youtube.com/watch?v=RIctzAQOe44
From memory, X11 is full of cruft that no longer makes sense. Everyone wants beautifully rendered, anti-aliased fonts, but X11 not only doesn't give you that, if you comply with X11 you can't do that.
Wayland took a look at how X11 is actually used, today, and throws away the cruft that nobody uses anymore. Also Wayland adds a sane API versioning system.
Wayland is exactly as network-transparent as X11 is in actual use these days: not very but you can make it work. Everyone is pretty much asking X11 for a drawing canvas, drawing on it, then giving it to a compositor to display. See above comments about beautifully anti-aliased fonts.
My favorite comment: "Everybody says the UNIX way is small programs that do one thing well. What is the 'one thing' that X11 does well?" He pointed out that at one point X11 had a print server embedded in it (it wasn't a good idea).
TL;DR Several of the top X11 developers think Wayland is a very good idea.
1) Destroy instutionalized education and rebuild it with features like Oh, I don't know...how about not penalizing people who think differently and degrees based on contribution to society and not paper exams?
2) How about not destroying our economic base by giving bankers hundreds of trillions in benefits for raping society and well, maybe using that money to build something we need...like a new propulsion tech not based on Newtonian Physics?
I would be willing to bet with 17 trillion dollars that the Bankers go we could probably do something interesting....like open the entire resource base of the solar system to a growing humanity with lots of problems.
It means I know nothing about Windows Server or Docker.
It means I know nothing about Windows Server or Docker.
It means I know nothing about Windows Server or Docker.
It means I know nothing about Windows Server or Docker.
It means I know nothing about Windows Server or Docker.
IT MEANS?
FAG RABBI!!
Now he gonna carve your putz, right after he KISSES THE BROWN SPIDER!
Strainers are like baskets - I aren't they all receptacles with leaks?
Actually I know shit all about "Docker" and haven't bothered to understand "application virtualization" or how it differs from "server virtualization". Let's not get to docker as a specific app virt with defined constraints and capabilities.
Hey! Let me add this piece of non-information, related to my opening statement: "colander".
Docker is sort of an extremely lightweight virtual machines system.
Docker organizes software into "containers". Each container has a complete set of libraries and files, and each container is isolated from the rest of the system. Thus if you need a specific and touchy set of libraries to run Software X, and you need a different specific and touchy set of libraries to run Software Y, you can simply make two containers and run them side by side.
As I understand it, Docker container images use a "snapshots" system to store changes; so the two containers for Software X and Software Y will together be much smaller than two VM images would be.
Using Docker, if developers make a server-side application, they can then hand a container over to production for deployment, and everyone can be confident that the application will run the same in production as it ran in development. (Of course it would still be possible to break things, for example by having different data in the production database compared to the dev test database.) Or, developers could run containers on their laptops and expect them to run the same as on the servers in the office.
Unlike VMs, the Docker containers don't run their own kernels. So you can't run a Linux server with Docker that in turn runs OpenBSD in a container.
As I understand it, many people use Docker to run a single process per container. The web server in one container, the email server in another, the SSH server in another, etc. One use case: if you have a web site hosted in the cloud, and the Slashdot effect starts slamming on the web site, the cloud hosting service could spin up another 500 instances of the web site (500 fresh instances of the Docker container, each container running a single process, the web server).
I talked to an expert sysadmin, and he told me "This is the future." I'm going to set up a Docker server at home and learn my way around it.
https://www.docker.com/whatisdocker/
My reading of the press release is that Microsoft is going to (a) implement the Docker APIs for Windows, so that Windows server applications can be container-ized; and (b) add the ability to run Linux containers. The latter is not implausible; Windows NT has always had so-called "personalities" and Posix has been available as a personality for decades.
Reply weeks late? Stop living in the past!
This post, complete with anti-gay slurs, is a typical example of the "sickness" that Lennart recently spoke about among those in the FOSS community. Absolutely disgusting.
Contextualize the observation you make, with the homo-erotic Bowie lyric in the sig. Now? Go meta, pea-brain.
Let me preface this with the fact that I'm an intellectual property specialist. I bill $450/hour, and still have lots of time to work on my startup without having to take venture capital.
I thought about some educational answers for your questions, but the insult at the start of your comment rubs me wrong and I decided I don't owe you anything. So, I'll save them.
The bigamy case against his mother may be able to use this information. Most bank records are readily available to law enforcement without a warrant.
"I've seen it. It's rubbish." -- Marvin the Paranoid Android