Either way, the Core devs should come with a solution and that must be quick. This is not good for the community and the image of Bitcoin. I hope there will be a change to 2MB blocks as that is an appropriate midway solution to keep the people happy.
I do agree that it will have an impact on those who are trying to spam Bitcoin with massive amounts of shitty dust transactions. And it surely will make Bitcoin more future proof, but this whole discussion / keyboard fighting is splitting the community in 2 parts and will cause severe damage if there isn't a solution where both sides are happy with. Pools are maestro, and the majority of them clearly don't want BIP 101.
Why isn't it a better idea to raise the blocksize to 2MB for now, and then increase it with 1MB per year to keep up with the natural growth of Bitcoin?
https://bitcointalksearch.org/topic/separate-fact-from-fiction-re-blocksize-1273567
There are also opinions and perceived risks involved. For instance, if the block size is increased 2MB for now and then 1MB per year, when should that stop? What if the 1 MB / year outruns technology and we have to have another hard fork to discontinue it because we guessed wrong? Is there even a proposal available to instigate that hard fork? If we just hard fork to 2MB, then we will inevitably need to hard fork again (this may be argued for 8MB as well, but only on a much larger time table).
That's definitely a good point you have there. However, the BIP 101 will double from 8MB to 16MB after just two years. Which is even worse than the 1MB per year growth. One thing is for sure, this will probably not be solved within a reasonable amount of months. It will only cause more people to split up and join the BIP 101 or BIP 100 side. I hope the devs will find a good mid way solution that will end this discussion.