The relation between the increase of the capacity factor of the wind and the decrease of the capacity factor of the natural gaz is the main point of the article. Please read it.
I didn't say that, but I agree that I should have used "a difference of 5" instead of 5% to avoid confusion.
As the wind capacity factor increase make the natural gaz capacity factor decrease, then there should cross in the future. Actually the natural gaz is at 62% and wind at 37%, so the cross could be somewhere around 50% capacity factor. It's only a difference of about 13. With a progression of 5 in a single year, this look entirely possible to cross in less than 10 years.
According to the article: 14H2 32% 15H1 35% 15H2 37% It's a 5% progression in a single year. At this rate it will probably need less than 10 years to cross the natural gaz capacity factor decline.
The outcome is clear: the future mainly rely on large number of interconnected wind and solar plants. An other probable consequence is that the price will change more quickly than now, because the production will be less adjustable. This price yo-yo will certainly push big investments to any kind of energy storage.
And the question is not about if the bug hang the system or not. The bug hang the system very clearly in a perfectly reproducible way. I will not disclose it here for obvious security reason. Anyway, in that case I was very disappointed by the reaction of the multiple maintainers concerned (the bug is a problem between several layers), while some others developers agree on the bug and even signed-off the proposed patches but can do nothing because there are not maintainers.
Agree about the details, sorry. We disagree on the adjectives to use to talk about the words Linus used in some cases. That also a detail, as Linus himself say that he is unable to act nicely in cases like that. And while I highly respect Linus work, like every human he is not prefect. At least it acknowledge the problem publicly, witch is not an easy step. From that point to the point that this kind of brutal relation should be normal on the LKML is a completely different issue. Sarah was talking about the LKML, not only about Linus.
Clam down. I can assert you that the bug is very real. I build embedded Linux systems since more than 15 years, I do pretend that I know what I am talking about.
Linux can fix the bug himself, no need to yield as he is the only one that decide if a patch is merged or not. The reality is that he don't want to make it.
You don't understand that the main problem is that the bug is ignored. Most of the actual maintainers are so busy filtering developers patches that there don't care anymore to user bug reports. Developers don't care either to the actual users as there make features that users don't actually uses.
Explain to me why a critical bug that completely hang the system with probably any distribution kernel since years is ignored for a good reason ? Happen to me no less than last week.
My own experience proved that your claim is generally false. In reality most peoples already over react on small details that can be insignificant from you point of view. So let's imagine where you are very explicit on your emotion. You can joke between fiends that you known well, but the same joke can be a mess in public.
Yes I know this case perfectly well thanks you. And I also get inappropriate response from kernel maintainers no less that last week, so I completely share the Shara point of view. That said the "completely abusive" part in my sentence is referring to the fact that Linux abuse of his position by using brutality. As Shara explained Linux already enjoy a undisputed power over the merge of the mainline tree, so he don't even have to use any harsh word to deny a merge. If he don't merge there no any possibility to get the patch in. That's very simple.
Try yourself to submit patches to a project where you are unknown and see what happens. I do since more than 15 years and I have see the change from the time where project maintainers was happy to help contribution to the today state of too many project where the maintainers act only on the attack or ignore attitude on the new comers. And it's not because of filtering. I have myself multiples patches for the kernel that have started brutal response for no valid reason.
The problem is that Linus defended his few bad attitude so well that this validated this kind of bad attitude to too much maintainers. The LKML is really a stress to post a patch on.
As the Linus Torvalds git tree is the only reference repository for Linux (mainline), if he decide to not merge a patch, it will make your work completely useless in the long term. It's possible to fork the Linus tree for a mid term period, the time to develop and cleanup a patches set, but this always require to rebase from the Linus Trovalds tree to get in sync. If you don't rebase on a regularly basis, your patches can go very quickly obsoletes and impossible to apply. There is constantly project trying to maintain fork of the Linus Torvalds tree, but none have the power to last in the long term because it require a lot of effort. So at the end and to simplify, either your patch is in mainline Linus Troavals tree, or either you patch is lost. This why Linus Torvalds enjoy a very high power compared to anyone else.
Have you ever posted to the LKML recently ? I do. And I can assure you this is actually a stress to get something right on it without getting attacked for nothing or completely ignored. The LKML was no so extreme 15 years ago. Shara was absolutely right to react to the abusive attitude. And yes a professional attitude require that you control your emotion. Only peoples that abuse of there position can lost control without consequences.
I can assure you that Shara code is fine, just read it, it's open source. I also share the view that too many maintainers are brutal for nothing, and unable to express there view in a professional way.
I experienced this no later than last week with 2 very simple patches after reporting 2 bugs. The first was minor but a developers asked me to submit a patch and that started a fight between two others developers. The second one is critical. I proposed a patch that was no view as acceptable, so i do a better one with many others proposals. I got a brutal reject without any hint on how to solve the problem. The bug will probably stay for years, since it's already affect almost any kernel since years.
So yes the LKML is a toxic place where it's really not fun to post an contribute.
Shara reaction was perfectly normal to the completely abusive Linus brutality. I myself got last week a brutal response from a Linux maintainer for futile reason that started a fight with two developers. Now the patch is ok and so there don't even merge it or talk about it. Also last week I submitted patch to fix a catastrophic kernel crash that complete hang the system and that affect almost every kernel since years and, I get only two rejections and no hint at all on how to properly fix it after proposed many different approach.
It's now a strange insupportable attack or ignore place. The kernel wasn't like that 15 years ago.
It's not only about Linus. There are others maintainers that are brutal for no reason and this happen too often. That said Linus as a uncontested leader of the project take a big responsibility to not take the problem seriously.
Slashdot Mirror
The relation between the increase of the capacity factor of the wind and the decrease of the capacity factor of the natural gaz is the main point of the article. Please read it.
I didn't say that, but I agree that I should have used "a difference of 5" instead of 5% to avoid confusion.
As the wind capacity factor increase make the natural gaz capacity factor decrease, then there should cross in the future. Actually the natural gaz is at 62% and wind at 37%, so the cross could be somewhere around 50% capacity factor. It's only a difference of about 13. With a progression of 5 in a single year, this look entirely possible to cross in less than 10 years.
Did you realize that wind is the consequence of heat convection in the atmosphere ?
According to the article:
14H2 32%
15H1 35%
15H2 37%
It's a 5% progression in a single year.
At this rate it will probably need less than 10 years to cross the natural gaz capacity factor decline.
The outcome is clear: the future mainly rely on large number of interconnected wind and solar plants. An other probable consequence is that the price will change more quickly than now, because the production will be less adjustable. This price yo-yo will certainly push big investments to any kind of energy storage.
No, I do not insulted him, sorry.
And the question is not about if the bug hang the system or not. The bug hang the system very clearly in a perfectly reproducible way. I will not disclose it here for obvious security reason. Anyway, in that case I was very disappointed by the reaction of the multiple maintainers concerned (the bug is a problem between several layers), while some others developers agree on the bug and even signed-off the proposed patches but can do nothing because there are not maintainers.
I never insulted you, so keep it for yourself.
You obviously never understand Linus position about breaking user space.
Agree about the details, sorry. We disagree on the adjectives to use to talk about the words Linus used in some cases. That also a detail, as Linus himself say that he is unable to act nicely in cases like that. And while I highly respect Linus work, like every human he is not prefect. At least it acknowledge the problem publicly, witch is not an easy step. From that point to the point that this kind of brutal relation should be normal on the LKML is a completely different issue. Sarah was talking about the LKML, not only about Linus.
Clam down. I can assert you that the bug is very real. I build embedded Linux systems since more than 15 years, I do pretend that I know what I am talking about.
Linux can fix the bug himself, no need to yield as he is the only one that decide if a patch is merged or not. The reality is that he don't want to make it.
You don't understand that the main problem is that the bug is ignored. Most of the actual maintainers are so busy filtering developers patches that there don't care anymore to user bug reports. Developers don't care either to the actual users as there make features that users don't actually uses.
Explain to me why a critical bug that completely hang the system with probably any distribution kernel since years is ignored for a good reason ? Happen to me no less than last week.
Fully agree. This is exactly why public email should be wrote especially carefully.
My own experience proved that your claim is generally false. In reality most peoples already over react on small details that can be insignificant from you point of view. So let's imagine where you are very explicit on your emotion. You can joke between fiends that you known well, but the same joke can be a mess in public.
Things go generally like you describes if you are a developer making a new feature. This very different when a user found a bug and try to fix it.
Yes I know this case perfectly well thanks you. And I also get inappropriate response from kernel maintainers no less that last week, so I completely share the Shara point of view. That said the "completely abusive" part in my sentence is referring to the fact that Linux abuse of his position by using brutality. As Shara explained Linux already enjoy a undisputed power over the merge of the mainline tree, so he don't even have to use any harsh word to deny a merge. If he don't merge there no any possibility to get the patch in. That's very simple.
Try yourself to submit patches to a project where you are unknown and see what happens. I do since more than 15 years and I have see the change from the time where project maintainers was happy to help contribution to the today state of too many project where the maintainers act only on the attack or ignore attitude on the new comers. And it's not because of filtering. I have myself multiples patches for the kernel that have started brutal response for no valid reason.
The problem is that Linus defended his few bad attitude so well that this validated this kind of bad attitude to too much maintainers. The LKML is really a stress to post a patch on.
As the Linus Torvalds git tree is the only reference repository for Linux (mainline), if he decide to not merge a patch, it will make your work completely useless in the long term. It's possible to fork the Linus tree for a mid term period, the time to develop and cleanup a patches set, but this always require to rebase from the Linus Trovalds tree to get in sync. If you don't rebase on a regularly basis, your patches can go very quickly obsoletes and impossible to apply. There is constantly project trying to maintain fork of the Linus Torvalds tree, but none have the power to last in the long term because it require a lot of effort. So at the end and to simplify, either your patch is in mainline Linus Troavals tree, or either you patch is lost. This why Linus Torvalds enjoy a very high power compared to anyone else.
Have you ever posted to the LKML recently ? I do. And I can assure you this is actually a stress to get something right on it without getting attacked for nothing or completely ignored. The LKML was no so extreme 15 years ago. Shara was absolutely right to react to the abusive attitude. And yes a professional attitude require that you control your emotion. Only peoples that abuse of there position can lost control without consequences.
I can assure you that Shara code is fine, just read it, it's open source.
I also share the view that too many maintainers are brutal for nothing, and unable to express there view in a professional way.
I experienced this no later than last week with 2 very simple patches after reporting 2 bugs. The first was minor but a developers asked me to submit a patch and that started a fight between two others developers. The second one is critical. I proposed a patch that was no view as acceptable, so i do a better one with many others proposals. I got a brutal reject without any hint on how to solve the problem. The bug will probably stay for years, since it's already affect almost any kernel since years.
So yes the LKML is a toxic place where it's really not fun to post an contribute.
Shara reaction was perfectly normal to the completely abusive Linus brutality. I myself got last week a brutal response from a Linux maintainer for futile reason that started a fight with two developers. Now the patch is ok and so there don't even merge it or talk about it. Also last week I submitted patch to fix a catastrophic kernel crash that complete hang the system and that affect almost every kernel since years and, I get only two rejections and no hint at all on how to properly fix it after proposed many different approach.
It's now a strange insupportable attack or ignore place. The kernel wasn't like that 15 years ago.
Try yourself in your job and give us your feedback in a few months.
It's not only about Linus. There are others maintainers that are brutal for no reason and this happen too often. That said Linus as a uncontested leader of the project take a big responsibility to not take the problem seriously.
Even flat out rejection don't require to use any harsh word if you enjoy a very asymmetric power ratio like Linus.