Sorry, you don’t have a clue. Most plastic used for packaging will burn very cleanly. You’re probably thinking about PVC, and maybe computer casings that (used to) contain toxic fire retardants. PE just turns into water and CO2.

Here in Germany, many of the super spreading events happened in confined environments with bad air circulation (e.g. a carnival session, a meat processing facility where the cool air seems to have contributed, and several church and choir incidents).

I would take the aerosol theory very seriously.

btrfs may not be as battle-proven as zfs is, but for most of the use case of zfs, it’s the more modern alternative that’s actively developed within the Linux kernel community.

In case you’re worried about its maturity: You can get enterprise support for it from SUSE and Oracle (!)

First of all, claiming that this decision came out of the blue just proves that the author doesn’t know how Red Hat does upstream open source work. All of this has happened in the open and was easy to predict if you watch what’s going on in Fedora (and openSUSE Tumbleweed just the same).

Second, it’s not at all a Red Hat only thing, and there’s no IBM conspiracy behind this. Everyone but the Docker guys themselves is going for the Podman stack and the cri-o runtime (for Kubernetes) and ditching the Docker stack. And this all started way before IBM acquired Red Hat.

As an end user, you won’t experience a real difference because the alternative stack has drop-in replacements for all of the parts of Docker and is compatible with the same container images and registries.

Not sure you got it: Iâ(TM)m working for SUSE and I know we are not flooded with service requests about systemd. To the contrary. Migration was really smooth. And this is for a Linux distribution that is offering in-place updates from previous versions.
As for the increasing size of the project: This is not just what is typically perceived as the systemd init system, but includes a lot of code like udev that used to exist separately on a pre-systemd Linux and was just merged into the systemd project for maintenance reasons. Thereâ(TM)s virtually no bloat as in adding yagni features.

If any of that was true, companies like SUSE that have been shipping systemd as the default on our enterprise offerings for years would be flooded with service requests from angry users. We simply arenâ(TM)t. Systemd as we are using it today is rock solid and enables many use cases like our transactional MicroOS with read-only filesystem that would be very hard or impossible to implement without it.

Significantly larger.

Unfortunately a lot of developers and companies who are publishing code under open source licenses do not get what open source means to their code: You are giving away a lot of control. The less viral the license, the more control you give up. Up to the point where you are basically donating them to the public with no moral or actual right to be compensated for it.

If you want to fully control monetization, keep your code proprietary. But then good luck with having to pay developers for every single line of code and every tiny little bugfix. No standing on the shoulders of giants.

Face it: If you want to build a business on open source, trying to fight others who make use of your code is futile. It is often unfair itself as well: Because there hardly is a successful open source project that has been possible without countless other open source projects that came before it. Projects that created the tools, programming languages, libraries and frameworks that make your own work possible.

If you take that upstream code for granted (which you would have to make or buy if it was not open source), you should also take for granted that others will take your open source code for granted and make money with it without caring for your precious montetization strategy. This is not unfair. It is playing by the rules. The rules just are not built to protect the interests of the original authors of the code, but to protect the freedom of the code itself.

Is there any trick for getting an apostrophe instead of this â when posting from Safari on iOS? This is really annoying. :-(

I just checked what I could find about wind turbine recycling in Germany. First, as I had expected, the cost of removing the turbine after its end of life is factored into the costs from day one. So when the time comes, the owners have to have reserves set aside to pay for the destruction and removal of the turbine. Second, many turbines can still be re-sold and get a second life in another wind park. Third, even today there is a complete recycling chain in place for everything from the concrete or steel of the towers to the blades. The blades are shredded and are used as fuel for cement manufacturing. No landfills involved, except for the ashes. The metals that can be recycled are covering a lot of the actual recycling cost, so most operators donâ(TM)t even spend all the money set aside for removal. Improvements in recycling will further increase the overall profitability.
I am not saying that this is not a problem in the U.S., but it is a problem others have solved with the right accounting principles and technologies.

Are you telling me that it is 2018 and this site is still not getting character encoding right? :-(

Renewable energiy isnât a toy, but a reality:
https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.energy-charts.de%2Fpower.htm%3Fsource%3Dall-sources%26amp;year=2018&week=26
https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.energy-charts.de%2Fenergy_pie.htm
Here in Germany weâ(TM)re close to producing 50% of all electricity from renewable sources. And thereâ(TM)s a lot of free roof space to add more solar panels. What these production charts donâ(TM)t show is that we are currently producing much more energy than we consume because the coal and nuclear plants canâ(TM)t easily shut down when their power isnâ(TM)t needed. So, in terms of total power consumption, once the storage problem is addressed, the solar and wind peaks, together with the bio gas and water plants that can be shut down in times of over-production, can be used to deliver energy all day and night.