I've read the x.org codebase. Mostly to discover the grey areas in the protocol when I was working on a X/Window server running on ms-windows. The x.org code is not pretty but that is mostly due to being an old code base.
The X protocol has its problems and quirks too, particularly when dealing with long latency between server and client. It was designed when using high-level primitives (eg "draw line to (x,y) in color Z") made sense. When client just use such primitives the speed is impressive. But some 10 years ago clients started doing client rendering and just sending bitmaps to the display server. Mostly that meant higher bandwidth and fewer round-trips.
Bandwidth does not matter nowadays and using Xrender than drawing commands does not really use more round-trips. In fact, Xrender was exactly designed for this purpose. The round-trips come from badly-designed clients, and synchronous use of the X protocol although it is designed for asynchronous use. I have have image viewers which work perfectly fine over the network also they move a lot of pixels.
The code base of X is OK. Yes, I have read the code of many different open-source projects (and some close-source). But the real problem is not the code at all, I don't mind if somebody decides it needs to reimplement the X server for some reason. The real problem with Wayland is breaking backwards and forwards compatibility with a universally supported protocol instead of carefully revising it in a backwards compatible way (which would easily be possible with extensions). This is just insanely stupid.
Nokia was the largest smartphone vendor with with faster growing sales than everybody else. Not saying they didn't have trouble: There was competition entering the market, and they were in an internal state of disarray, but they had lots of options: The best one would have been to just bring a few Meego phones to market just as planned and transition Symbian developers to Meego via QT. I owned a N9 and it was really good and Android still wasn't really big at that time (and even today is still not as good as Meego was in my opinion). Ofcourse, adopting Android would also have been far better than switching to Windows phone.
I disagree. They should just have executed their previous plan which was excellent: Push Meego and keep Symbian alive. Transition Symbian developer to Qt and then to Meego with Qt. Meego was very good and obviously ready (they released the N9 in the same year after anouncing the switch to Windows phone). I still consider the N9 a much better phone than my current Android phone. And people tend to forget: Android wasn't nearly as big as today. At that time Nokias was still the biggest smartphone vendor and had faster growing smartphone sales than all other vendors. Of course, after Nokia imploded Android quickly filled the void.
Abortion, of which I'm pro, is already a step towards eugenics. In 200 years, many diseases will have ceased to exist because of this.
Down's Syndrome has already been reduced over 90% in Europe, and by about 70% in America. The American parents almost certainly include a number of hypocrites, since 44% of Americans think abortion should be illegal.
Down syndrome happens by change so it will not cease to exist in the future just by having abortions today.
Absolutely. And even for the phone and tablet space is big mistake to switch away from X. Where could be more useful to move windows freely between devices than with mobile devices....
shell scripts are great. They are flexible, powerful, transparent, easily changeable, debug-able... With systemd you have a blackbox and have to learn magic keywords. It is like windows - for idiots - not for hackers. Yes, the shell script based system sometimes was a mess. But the solution is to clean the scripts up not to replace them...
Which has nothing to do with VLAs. A regular array (or any other data struture) can also be allocated on the stack or on the heap. In both cases this can decided by the programmer (by placing the array on the stack or on the heap). I don't know of any C compiler which would allocate a VLA defined as local variable (on the stack) using malloc behind the back of the programmer.
In the example I gave, the size is encoded in the type. This makes it simple and cheap for the compiler to add bounds checking (which can also often be optimized away if it can prove that the access is not out-of-bounds).
This does not reserve memory. This declares ptr to be a pointer to an array of length 256. This is exactly what a bounded pointer is. And yes, compilers can sometimes detect out-of-bounds accesses at compile time (not only for literals) and because out-of-bounds accesses are undefined behavior, there are free to add run-time bounds checking when the pointer is de-referenced. And this is exactly what the undefined-behavior sanitizer for clang and gcc does if you use it. I know, because I fixed this for gcc because it wasn't working.
void foo(int n, char (*buf)[n])
{
(*buf)[n] = 1;
}
int main(int c, char* argv[])
{
char buf[10];
foo(10, &buf);
}
$ clang-3.5 -fsanitize=undefined -O3 c.c
$./a.out
c.c:4:2: runtime error: index 10 out of bounds for type 'char [n]'
They had a huge amount of broken pebbles during operations. Now read your own statement above about why there is no radioactivity in the coolant and whether it still makes sense in the light of the fact that pebbles broke all the time in this reactor.
There is highly radioactive material in the cooliong system exactly because they had so much broken fuel pebbles (apparently caused mostly by control rods ). This was one of the major flaws with this reactor which was not anticipated. According to the spiegel (1986; 24:28-30), this specific incident the jammed pebble was not a fuel pebble but a bor-filled pebble used as moderator. During the attempt to get it free, they damaged quite a lot of (moderator) pebbles and also accidentally released cooling gas (helium) from the system during an attempt to clean the pipe with it (and the cooling gas is contaminated by dust from previously broken fuel pebbles). How much radioactivity was released is unknown as monitoring equipment did not work just around this time. The new statement is that this release was not accidental but intentional because they didn't want to wait for a filtering system to arrive which would have allowed to do the cleaning without releasing unfiltered gas.
Nonsense. There were broken pebbles (and not only from this incident - this was major problem with this reactor). It is still a major problem with cleaning up the site.
Your conclusion would be right if you premises were. But renewables generally tend to *reduce* the span between prices for peak and base load. So the electricity generally fits much better to a modern economy. In fact, the demand for pumped-storage went down in Germany. And yes, there is a lot of engineering talent in Germany and this has been studied a lot. The conclusion is that it not a big challenge to scale up renewables a lot more without a hard requirement to expand storage.
Good data can be obtained from here http://www.ag-energiebilanzen..... Germany rapidly expanded the production of electricity from a very low level. In 2015 Germany produced 196 TWh of electricity from renewable sources (from a total of 652 TWh). This is huge and more than nuclear did at its best times. Two decades of aggressive government programs to support renewables were already much more successful than half a century of subsidies for the nuclear industry which still isn't able to deliver a modern plant at a competitive price.
Sure, and RF-coils too (as does NMR), but RF-coils and gradient coils generate relatively small fields. The point is that you do not need a huge superconducting magnet to do MRI.
Slashdot Mirror
I've read the x.org codebase. Mostly to discover the grey areas in the protocol when I was working on a X/Window server running on ms-windows. The x.org code is not pretty but that is mostly due to being an old code base.
The X protocol has its problems and quirks too, particularly when dealing with long latency between server and client. It was designed when using high-level primitives (eg "draw line to (x,y) in color Z") made sense. When client just use such primitives the speed is impressive. But some 10 years ago clients started doing client rendering and just sending bitmaps to the display server. Mostly that meant higher bandwidth and fewer round-trips.
Bandwidth does not matter nowadays and using Xrender than drawing commands does not really use more round-trips. In fact, Xrender was exactly designed for this purpose. The round-trips come from badly-designed clients, and synchronous use of the X protocol although it is designed for asynchronous use. I have have image viewers which work perfectly fine over the network also they move a lot of pixels.
The code base of X is OK. Yes, I have read the code of many different open-source projects (and some close-source). But the real problem is not the code at all, I don't mind if somebody decides it needs to reimplement the X server for some reason. The real problem with Wayland is breaking backwards and forwards compatibility with a universally supported protocol instead of carefully revising it in a backwards compatible way (which would easily be possible with extensions). This is just insanely stupid.
Nokia was the largest smartphone vendor with with faster growing sales than everybody else. Not saying they didn't have trouble: There was competition entering the market, and they were in an internal state of disarray, but they had lots of options: The best one would have been to just bring a few Meego phones to market just as planned and transition Symbian developers to Meego via QT. I owned a N9 and it was really good and Android still wasn't really big at that time (and even today is still not as good as Meego was in my opinion). Ofcourse, adopting Android would also have been far better than switching to Windows phone.
I disagree. They should just have executed their previous plan which was excellent: Push Meego and keep Symbian alive. Transition Symbian developer to Qt and then to Meego with Qt. Meego was very good and obviously ready (they released the N9 in the same year after anouncing the switch to Windows phone). I still consider the N9 a much better phone than my current Android phone. And people tend to forget: Android wasn't nearly as big as today. At that time Nokias was still the biggest smartphone vendor and had faster growing smartphone sales than all other vendors. Of course, after Nokia imploded Android quickly filled the void.
Abortion, of which I'm pro, is already a step towards eugenics. In 200 years, many diseases will have ceased to exist because of this.
Down's Syndrome has already been reduced over 90% in Europe, and by about 70% in America. The American parents almost certainly include a number of hypocrites, since 44% of Americans think abortion should be illegal.
Down syndrome happens by change so it will not cease to exist in the future just by having abortions today.
Ask any child of five.
I would recommend to look at facts and hard data instead.
Absolutely. And even for the phone and tablet space is big mistake to switch away from X. Where could be more useful to move windows freely between devices than with mobile devices....
Or it might be, that they people who care are simple not yet organized enough and it just takes some time until this happens....
shell scripts are great. They are flexible, powerful, transparent, easily changeable, debug-able ... With systemd you have a blackbox and have to learn magic keywords. It is like windows - for idiots - not for hackers. Yes, the shell script based system sometimes was a mess. But the solution is to clean the scripts up not to replace them...
Which has nothing to do with VLAs. A regular array (or any other data struture) can also be allocated on the stack or on the heap. In both cases this can decided by the programmer (by placing the array on the stack or on the heap). I don't know of any C compiler which would allocate a VLA defined as local variable (on the stack) using malloc behind the back of the programmer.
In the example I gave, the size is encoded in the type. This makes it simple and cheap for the compiler to add bounds checking (which can also often be optimized away if it can prove that the access is not out-of-bounds).
This does not reserve memory. This declares ptr to be a pointer to an array of length 256. This is exactly what a bounded pointer is. And yes, compilers can sometimes detect out-of-bounds accesses at compile time (not only for literals) and because out-of-bounds accesses are undefined behavior, there are free to add run-time bounds checking when the pointer is de-referenced. And this is exactly what the undefined-behavior sanitizer for clang and gcc does if you use it. I know, because I fixed this for gcc because it wasn't working.
void foo(int n, char (*buf)[n]) ./a.out
{
(*buf)[n] = 1;
}
int main(int c, char* argv[])
{
char buf[10];
foo(10, &buf);
}
$ clang-3.5 -fsanitize=undefined -O3 c.c
$
c.c:4:2: runtime error: index 10 out of bounds for type 'char [n]'
Sorry, a VLA has nothing to do with stack vs malloc. This is a common misconception. The pointer in my example could refer to memory on the heap.
A bounded pointer-type already exists: char (*ptr)[256];
The funny little known fact is: C99 already has a bounded pointer type: A pointer to a variable-length array.
void foo(int N, char (*ptr)[N]) // undefined behaviour
{
(*ptr)[N + 3] = 10;
}
Using the undefined-behaviour sanitizer, you can also have the compiler add automatic checks.
They had a huge amount of broken pebbles during operations. Now read your own statement above about why there is no radioactivity in the coolant and whether it still makes sense in the light of the fact that pebbles broke all the time in this reactor.
There is highly radioactive material in the cooliong system exactly because they had so much broken fuel pebbles (apparently caused mostly by control rods ). This was one of the major flaws with this reactor which was not anticipated. According to the spiegel (1986; 24:28-30), this specific incident the jammed pebble was not a fuel pebble but a bor-filled pebble used as moderator. During the attempt to get it free, they damaged quite a lot of (moderator) pebbles and also accidentally released cooling gas (helium) from the system during an attempt to clean the pipe with it (and the cooling gas is contaminated by dust from previously broken fuel pebbles). How much radioactivity was released is unknown as monitoring equipment did not work just around this time. The new statement is that this release was not accidental but intentional because they didn't want to wait for a filtering system to arrive which would have allowed to do the cleaning without releasing unfiltered gas.
There are still 3000 broken pebbles in the reactor... http://nuris.org/wp-content/up...
Nonsense. There were broken pebbles (and not only from this incident - this was major problem with this reactor). It is still a major problem with cleaning up the site.
This *was* a fuel damage accident.
AC, I gave a number. It is a significant number. It is very obvious that continuing this path with cut into carbon-based fuel real quick.
Your conclusion would be right if you premises were. But renewables generally tend to *reduce* the span between prices for peak and base load. So the electricity generally fits much better to a modern economy. In fact, the demand for pumped-storage went down in Germany. And yes, there is a lot of engineering talent in Germany and this has been studied a lot. The conclusion is that it not a big challenge to scale up renewables a lot more without a hard requirement to expand storage.
Good data can be obtained from here http://www.ag-energiebilanzen..... Germany rapidly expanded the production of electricity from a very low level. In 2015 Germany produced 196 TWh of electricity from renewable sources (from a total of 652 TWh). This is huge and more than nuclear did at its best times. Two decades of aggressive government programs to support renewables were already much more successful than half a century of subsidies for the nuclear industry which still isn't able to deliver a modern plant at a competitive price.
Sure, and RF-coils too (as does NMR), but RF-coils and gradient coils generate relatively small fields. The point is that you do not need a huge superconducting magnet to do MRI.
Earth-field MRIs do exist too.
http://www.magritek.com/produc...
Ofcourse, it takes 4 hours to get a blurry image of a fruit (which does not move).