I think that are specifically wrong in saying that you are anti controversial hard forks, I think that increasing the blocksize will always be controversial because of the culture of believe that has now been build up in the Bitcoin community, according to that reasoning we should therefore never increase the blocksize limit? I think this is fundamentally flawed, especially considering how important a parameter this blocksize limit actually is. I think part of the difference in our opinion is that you are also not taking the competition into account.
No, that's not what a controversial hard fork is. A consensus based upgrade (via a HF) of the block size limit is very possible. A controversial fork would be one trying to push only up to a certain percent of miners, which make up a 'majority' or even a minority, which is far different from upgrades based on consensus.
Of course it is possible but whether something is practically attainable within a reasonable time frame is a different question. I understand the difference between a consensus based hard fork and a controversial hard fork. My point is that is that this entire subject has become controversial and there are some very staunch defenders of the blocksize limit, even within the Core development team itself. It would only take one of these developers to veto the code in order to block the change. Since any code that does not come from core would be regarded as controversial? I could see this taking years if any change is even achieved at all, there is a good reason why large democracies vote by a simple majority and not consensus, consensus in the literal sense of the word is almost impossible to achieve among large groups of people.
I can see Bitcoin easily being overtaken during this period, this is one of the reasons I am also invested in the altcoins. Bitcoin truly seems stagnant in comparison to me, the alternatives are able to innovate much faster and already have much greater transactional capacity then Bitcoin.
My argument stands on its own, if Core simply increased the blocksize limit to two megabytes it would reunite much of the community and Bitcoin would not be currently suffering from a congested network, which is currently causing transaction delays, increased fees and unreliability.
We have been down this path before,
it is unsafe to do so. Just because you may not know or understand why that is, that doesn't make it any less true. There may even be security issues at 1 MB that are not publicly disclosed for the obvious purposes. Whoever you ask about such, I doubt that they would disclose them outside of their 'inner' circles due to safety reasons.
I think it is ridiclous for you to say that 2MB is not safe. We have discussed the reosons for this extensivly already, for anyone intrested just look at our post histories.
I am presently mining 17MB blocks on the testnet using Bitcoin Unlimited.

I know you like to paint me as being an extremely unreasonable person, however what I am proposing here is very reasonable, most people outside of this field would recognize that the small blockist are taking an extreme and fundamentalist position. Most big blockist are applying pragmatic rationalism. Ideally I would just remove the blocksize limit completely or use an adaptive blocksize, as a compromise we proposed the mechanism within Classic, for an increase to two megabytes, we went from 20MB to 8MB and finally to 2MB, and I could argue using Bitcoin Unlimited we could even agree to a 1.1MB blocksize limit. There has been zero compromise from the small block camp, after 18 months. There is not even a blocksize limit increase on the Core road map.
As soon as the quadratic validation time problem has been solved, I see a semi-near future in which it is possible to increase the block size to a total of ~3-4 MB (includes the base expected amount that Segwit should provide, which is around 180%, i.e. 1.8 MB). However, the parameters are certainly going to be much different that you guys are expecting them to be. Doing a HF, which requires ALL custom implementations to be upgraded (this takes time for big businesses) just for a block size limit upgrade is also inefficient. The next HF should be optimally carry desired changes that require a HF in addition to a capacity increase with a grace period of 6-12 months.
So one year from the time that it is announced, and it has not even been announced yet and probably will not be any time soon. Great, lots of luck with that, I would advise you and everyone here to diversify their investments, this is the reason why Bitcoin has become stagnant.
Fortunately there are many alternatives to Bitcoin out there, I personally like Dash, and its solutions to governance, Ethereum and Monero are also both good cryptocurrencies, all of these cryptocurrencies do not have problems with scaling, Dash has a second tier, incentivized and collateralized voting full nodes that can handle a much greater load, because of the build in incentive. Ethereum already has far greater capacity then Bitcoin and it will have even more in following releases. Monero simply has an adaptive blocksize, with some very interesting incentive structures to keep the blocks from becoming to large.
I am pointing this out, because I think that you are underestimating the competition and overestimating the network effect of Bitcoin. Waiting several years for a simple capacity increase while the network is congested with all of its negative consequences is terrible for mass adoption, meanwhile the market share of Bitcoin is now 79.6%, there is a good reason for that and the trend will most likely continue as Bitcoin will continue to lose market cap to its competition.