The lesson here is: US nuclear power plant construction companies suck. They've lost all of their expertise and can't find their asses with both hands and a GPS.
If you want cheap power plants built on time, you should go to Rosatom or maybe to Areva in a pinch.
My house has it, air ducts to every room have electrically-controlled valves. You can also easily retrofit a house that doesn't have zonal AC by using motorized air vents, like https://keenhome.io/
So far Trump has sold off consumer interests by undermining FCC and the CFPB. He has also sold off the Grand Escalante Monument - it's already done.
And please note that Bush pissed away a freaking surplus and so Obama inherited the deepest deficit ever during his first year. So please sock up about corrupt politicians. You know nothing of what you're speaking.
It wasn't too useful as untrusted clients also can't use render and other important extensions. This also seems easily changed.
Not really. There's no accounting for buffer space, for example, or throttling for command streams in X.org. So one misbehaving client can still bring down everything. You can rewrite X.org completely from scratch using async primitives and threadsafe code everywhere. Sure. No problem at all.
Ok, so it starts from the other direction. So what? It isn't clear to me why - once all desired features and extensions have been added - the end result would be any better than what could be achieved by using isolated untrusted clients on X
The X.org codebase is crap. It can't be patched indefinitely, its core design is basically broken to be useful in a modern environment. The fact that somebody bothered to fake it with "security" extensions doesn't change it.
So we now have to maintain both X and Wayland. Wow, Genius!
With XWayland you can have each application running its own private crappy version of X.org.
"Since many of the underlying technologies in these environments were not designed with strong application isolation in mind, users should only install applications using these interfaces from trusted sources." Solved?
Yep. Ubuntu snaps are as good as containment mechanisms in Linux (i.e. not that good at all).
I would do it the other way - align short reads on contigs made from long reads. No need for de Brujn graphs, simple OLC (overlap layout consensus) is sufficient.
Former Illumina Long Read kit developer here. Nanopore reads are lousy with repeated nucleotides (to be fair, our kit also kinda was because of multiple PCR cycles needed) and it does have a certain GC bias.
Right now regular Illumina short reads with a little bit of long reads are enough to get phased SNP information from most relevant parts of a human genome. It's also cheaper at scale, human genome sequencing at 3x can be done for less than $500.
With de-novo assembly it's a bit different. Nanopores provide a good scaffolding for short reads, it's almost like magic.
Why not? The necessary hooks seem to be all there. Untrusted X Clients are isolated against trusted X Clients. This seems to work.
Who told you this nonsense? X.org doesn't have any real distinction between clients. They are all similarly "trusted".
There's a thin veneer of SECURITY and XAce extensions which are not used by anybody. They are not even build-enabled in Debian and CentOS. They are also utterly inadequate, for example, SECURITY extension puts all "untrusted" clients together as there's no per-client isolation and doesn't prevent all sniffing.
A wayland shell would also be shared by its clients, or? With the security hooks already there, why is there are need for re-architecting?
Wayland clients don't have access to each other without shell explicitly granting capabilities to do it. They _might_ have access to the shell but it's easy to isolate. For example, a browser application can be limited only to submitting requests for direct rendering manager and to reading its input stream.
I don't mind splitting up X or re-architecting parts of it (although I do not quite see why you think it is needed - we also have a monolithic kernel). The main problem I have with Wayland is that it breaks compatibility with the wire-protocol without a good reason.
Run XWayland for perfect backwards compat. Problem solved.
Well, if they can interact, then isolation is difficult and somehow I doubt they have solved this completely, and if they can not really interact, they are useless....
I pointed out the solution: X clients could be isolated against each other
No, they can not be isolated. X.org is shared across all clients and it can't be changed without re-architecting it. Attempts to do it (XAce) died ignominiously. You'll need to introduce multiple independent X servers and a layer above them to orchestrate input devices and access to direct rendering. In short, you'll get Wayland.
Wake me up if any Linux distribution ships with proper isolation between different programs from the same user.
Ding! Wake up call! Ubuntu does it quite well with snaps.
I worked on an input driver for a complicated device. The code in the X-server that I had to interact with was total garbage. It was designed in 80-s and patched to at least try supporting anything more modern than a Space Cadet keyboard.
For example, X.org is single-threaded so it doesn't need synchronization. Except that it isn't. Signal handlers for input devices can whack the cursor state directly. And if you want to do a device handover so an application can take exclusive ownership of a device you'll have to do a lot of interesting contortions.
Except that in X there can be multiple applications at different privilege levels. That sudo in an X terminal? Totally vulnerable for an application that runs in a browser and has somehow gained access to the X socket. Never mind that ptrace() can be effectively limited through a multitude of methods (LSM, namespaces, caps).
I worked on X codebase and I know it's shit. It's a patched-over shit, but still. Integer overflows, memory corruption, it has everything.
But even setting this aside, X.org is insecure by design. Any application can just send any events to any other application, so there's no point in trying to make it secure. If you have access to an X connection then you already have full access to the user's data. For example, you simply can inject "ctrl-t" into the shell to launch a terminal and then inject any commands you want into it.
And about "todays wonder boys" - Wayland is designed and written mostly by the same developers who are working on X.org
X server normally is accessible only locally through Unix domain sockets or through SSH tunnels bound to localhost. And if an attacker gets access to the X connection then they already own you.
Oh please do shut up. X.org codebase is a steaming pile of single-threaded shit that needs to be patched up from 10 different directions to be even able to deal with modern graphics. It's so full of security holes that it doesn't even make sense to look for them.
Why shouldn't I pick 2009? Is it worse than other years? After all, it's the year before Energiewende officially started. It was supposed to get better and better after the transition, right?
But don't worry, official data is in - Germany's CO2 emissions rose for the second year straight. Victory!
Actually proportionally Israel is way more popular than the US. Medical tourism to the US is basically an exception.
Here's the actual data: https://www.cihi.ca/sites/defa... The average treatment time for cancer in Canada is less than 20 days. In the US many people simply used to get NO cancer treatment whatsoever.
Look at the recent consumer drone wars. A Chinese company DJI won them fair and square, against many US companies with deep pockets. And not by producing cheapest possible knockoffs but by actually making superior products.
This is how things are going to be happening constantly in about 10 years or so. Nimen yinggai kaishi xue zhongwen.
Space travel - first man made object in space was the V2. Early space program in both US and USSR carried on from German rocketry, with German scientists
Early USSR rocketry experiments were done before and during the WWII, resulting in development of Katyusha ( https://en.wikipedia.org/wiki/... ). By the end of the WWII, the USSR already had a sophisticated homegrown rocketry program. As a result, Soviet rocket designs were completely unlike the German V2s.
German scientists were mostly captured by the US for obvious reasons.
I'm sorry. Perhaps you have trouble reading? Let me repeat the numbers:
2009: 145.6 TWh - lignite, 107.9 TWh - hard coal.
2016: 149.5 TWh - lignite, 112.2 TWh - hard coal.
Coal generation went up. Just slightly, but it's up. And it's not going down appreciably in the next several years.
Let's see:
2009: hard coal 27.3, lignite: 21.1
2016: hard coal 27.4, lignite: 21.4
In my book 2009 is earlier than 2016, 27.4 is greater than 27.3 and 21.4 is greater than 21.1
So yep, Germany is indeed increasing coal use, as shown by your very own link.
2009: hard coal 27.3, lignite: 21.1
2016: hard coal 27.4, lignite: 21.4
In absolute numbers coal use has slightly increased. In relative numbers it has decreased, since a lot of solar/wind/natgas generation was added.
So yep, Germany can talk tough but it can't get rid of coal power. And local greenie idiot "leadership" there knows this perfectly well, so there are no real large-scale protests against coal. And if they try to do it, then serious people from German industry will have some words with them.
Slashdot Mirror
The lesson here is: US nuclear power plant construction companies suck. They've lost all of their expertise and can't find their asses with both hands and a GPS.
If you want cheap power plants built on time, you should go to Rosatom or maybe to Areva in a pinch.
My house has it, air ducts to every room have electrically-controlled valves. You can also easily retrofit a house that doesn't have zonal AC by using motorized air vents, like https://keenhome.io/
Yeah, the statues of heroes like Taney from Dred Scott decision. True heroes of the slavery!
So far Trump has sold off consumer interests by undermining FCC and the CFPB. He has also sold off the Grand Escalante Monument - it's already done.
And please note that Bush pissed away a freaking surplus and so Obama inherited the deepest deficit ever during his first year. So please sock up about corrupt politicians. You know nothing of what you're speaking.
Yes, but for this particular worm it isn't. C.Elegans has fixed wiring that has been mapped completely.
It wasn't too useful as untrusted clients also can't use render and other important extensions. This also seems easily changed.
Not really. There's no accounting for buffer space, for example, or throttling for command streams in X.org. So one misbehaving client can still bring down everything. You can rewrite X.org completely from scratch using async primitives and threadsafe code everywhere. Sure. No problem at all.
Ok, so it starts from the other direction. So what? It isn't clear to me why - once all desired features and extensions have been added - the end result would be any better than what could be achieved by using isolated untrusted clients on X
The X.org codebase is crap. It can't be patched indefinitely, its core design is basically broken to be useful in a modern environment. The fact that somebody bothered to fake it with "security" extensions doesn't change it.
So we now have to maintain both X and Wayland. Wow, Genius!
With XWayland you can have each application running its own private crappy version of X.org.
"Since many of the underlying technologies in these environments were not designed with strong application isolation in mind, users should only install applications using these interfaces from trusted sources." Solved?
Yep. Ubuntu snaps are as good as containment mechanisms in Linux (i.e. not that good at all).
I would do it the other way - align short reads on contigs made from long reads. No need for de Brujn graphs, simple OLC (overlap layout consensus) is sufficient.
Former Illumina Long Read kit developer here. Nanopore reads are lousy with repeated nucleotides (to be fair, our kit also kinda was because of multiple PCR cycles needed) and it does have a certain GC bias.
Right now regular Illumina short reads with a little bit of long reads are enough to get phased SNP information from most relevant parts of a human genome. It's also cheaper at scale, human genome sequencing at 3x can be done for less than $500.
With de-novo assembly it's a bit different. Nanopores provide a good scaffolding for short reads, it's almost like magic.
You have port 600X open on a network-facing interface (i.e. not localhost)? Yeah, lol.
Why not? The necessary hooks seem to be all there. Untrusted X Clients are isolated against trusted X Clients. This seems to work.
Who told you this nonsense? X.org doesn't have any real distinction between clients. They are all similarly "trusted".
There's a thin veneer of SECURITY and XAce extensions which are not used by anybody. They are not even build-enabled in Debian and CentOS. They are also utterly inadequate, for example, SECURITY extension puts all "untrusted" clients together as there's no per-client isolation and doesn't prevent all sniffing.
A wayland shell would also be shared by its clients, or? With the security hooks already there, why is there are need for re-architecting?
Wayland clients don't have access to each other without shell explicitly granting capabilities to do it. They _might_ have access to the shell but it's easy to isolate. For example, a browser application can be limited only to submitting requests for direct rendering manager and to reading its input stream.
I don't mind splitting up X or re-architecting parts of it (although I do not quite see why you think it is needed - we also have a monolithic kernel). The main problem I have with Wayland is that it breaks compatibility with the wire-protocol without a good reason.
Run XWayland for perfect backwards compat. Problem solved.
Well, if they can interact, then isolation is difficult and somehow I doubt they have solved this completely, and if they can not really interact, they are useless....
Solved: https://github.com/snapcore/sn...
I pointed out the solution: X clients could be isolated against each other
No, they can not be isolated. X.org is shared across all clients and it can't be changed without re-architecting it. Attempts to do it (XAce) died ignominiously. You'll need to introduce multiple independent X servers and a layer above them to orchestrate input devices and access to direct rendering. In short, you'll get Wayland.
Wake me up if any Linux distribution ships with proper isolation between different programs from the same user.
Ding! Wake up call! Ubuntu does it quite well with snaps.
I worked on an input driver for a complicated device. The code in the X-server that I had to interact with was total garbage. It was designed in 80-s and patched to at least try supporting anything more modern than a Space Cadet keyboard.
For example, X.org is single-threaded so it doesn't need synchronization. Except that it isn't. Signal handlers for input devices can whack the cursor state directly. And if you want to do a device handover so an application can take exclusive ownership of a device you'll have to do a lot of interesting contortions.
I worked on the input stack.
Except that in X there can be multiple applications at different privilege levels. That sudo in an X terminal? Totally vulnerable for an application that runs in a browser and has somehow gained access to the X socket. Never mind that ptrace() can be effectively limited through a multitude of methods (LSM, namespaces, caps).
I worked on X codebase and I know it's shit. It's a patched-over shit, but still. Integer overflows, memory corruption, it has everything.
But even setting this aside, X.org is insecure by design. Any application can just send any events to any other application, so there's no point in trying to make it secure. If you have access to an X connection then you already have full access to the user's data. For example, you simply can inject "ctrl-t" into the shell to launch a terminal and then inject any commands you want into it.
And about "todays wonder boys" - Wayland is designed and written mostly by the same developers who are working on X.org
X server normally is accessible only locally through Unix domain sockets or through SSH tunnels bound to localhost. And if an attacker gets access to the X connection then they already own you.
Oh please do shut up. X.org codebase is a steaming pile of single-threaded shit that needs to be patched up from 10 different directions to be even able to deal with modern graphics. It's so full of security holes that it doesn't even make sense to look for them.
Why shouldn't I pick 2009? Is it worse than other years? After all, it's the year before Energiewende officially started. It was supposed to get better and better after the transition, right?
But don't worry, official data is in - Germany's CO2 emissions rose for the second year straight. Victory!
Actually proportionally Israel is way more popular than the US. Medical tourism to the US is basically an exception.
Here's the actual data: https://www.cihi.ca/sites/defa... The average treatment time for cancer in Canada is less than 20 days. In the US many people simply used to get NO cancer treatment whatsoever.
Look at the recent consumer drone wars. A Chinese company DJI won them fair and square, against many US companies with deep pockets. And not by producing cheapest possible knockoffs but by actually making superior products.
This is how things are going to be happening constantly in about 10 years or so. Nimen yinggai kaishi xue zhongwen.
People are also traveling to Israel for medical treatment. So?
Space travel - first man made object in space was the V2. Early space program in both US and USSR carried on from German rocketry, with German scientists
Early USSR rocketry experiments were done before and during the WWII, resulting in development of Katyusha ( https://en.wikipedia.org/wiki/... ). By the end of the WWII, the USSR already had a sophisticated homegrown rocketry program. As a result, Soviet rocket designs were completely unlike the German V2s.
German scientists were mostly captured by the US for obvious reasons.
I'm sorry. Perhaps you have trouble reading? Let me repeat the numbers:
2009: 145.6 TWh - lignite, 107.9 TWh - hard coal.
2016: 149.5 TWh - lignite, 112.2 TWh - hard coal.
Coal generation went up. Just slightly, but it's up. And it's not going down appreciably in the next several years.
Sorry, wrong link. Look at the one below that one. Here's the direct link to the underlying data: https://ag-energiebilanzen.de/...
2009: 145.6 TWh - lignite, 107.9 TWh - hard coal.
2016: 149.5 TWh - lignite, 112.2 TWh - hard coal.
Yep, Germany's coal use is growing.
Let's see:
2009: hard coal 27.3, lignite: 21.1
2016: hard coal 27.4, lignite: 21.4
In my book 2009 is earlier than 2016, 27.4 is greater than 27.3 and 21.4 is greater than 21.1
So yep, Germany is indeed increasing coal use, as shown by your very own link.
From your very link. Lookie here: https://www.cleanenergywire.or...
2009: hard coal 27.3, lignite: 21.1
2016: hard coal 27.4, lignite: 21.4
In absolute numbers coal use has slightly increased. In relative numbers it has decreased, since a lot of solar/wind/natgas generation was added.
So yep, Germany can talk tough but it can't get rid of coal power. And local greenie idiot "leadership" there knows this perfectly well, so there are no real large-scale protests against coal. And if they try to do it, then serious people from German industry will have some words with them.