Are you talking theory or is there anyone of import (besides you and some members of the bitcoin community who actually bought bitcoins) who is actually opposed to seg wit?
My understanding is that even "developers" Gavin and Jeff Garzik are in favor of seg wit, and Gavin and Jeff Garzik are the only two "developers" who had been proposing a need to hardfork (through XT and Classic).
So, what's the deal, is there someone else who is notable who is opposed to Segwit?
How could a softfork be more dangerous in the deployment of seg wit and in such actual real world circumstances, if there is actually no opposition seg wit?
There is no known obvious flaw in SegWit, even implemented as soft fork with Luke's script hack (as Blockstream is doing). It does fix those malleability problems. The other alleged benefits are small: it saves a little bandwidth for simple clients (only for them; not for full nodes) and may give a little more block space (depending on how many clients adopt the new format).
Who fucking cares how much value it adds? The main point is that seg wit is not controverted by any significant player. There are people whining about seg wit, but in the end, no one of significance disagrees with its implementation, so therefore, it can be implemented as a softfork.
Regarding value and how much it adds to blockchain capacity, we will see about that, once it is implemented. Currently, there is a lot of speculation about how much it will add and whether it is enough, and in that regard, it seems very reasonable to let it go live (since it is not controverted), and then to determine thereafter whether additional measures will need to be taken in order to accomplish additional objectives (such as further increasing capacity).
SegWit is just a disgusting hack. The same benefits could (should) have been implemented in a cleaner way, with a hard fork, without having to change the format of blocks.
Could have, should have, so what!!!!
no one really disagrees about seg wit.. so why continue to make it an issue, except for the purpose of spreading FUCD. The point is it is already done.. been agreed to and in the process of going live... the only likely way of stopping seg wit from going live is if there is some kind of significant problem that is discovered before it actually goes live.. so why continue to cry over spillt milk?
I have seen complaints from wallet developers about the extent of changes that it will require to their code. Others have complained about the huge risk of having such a pervasive change (more than 500 lines of code, last I read) made to the core of the protocol, with relatively little critical review, and under such pressure. (Testing can reveal accidental flaws; but one will not know about security flaws until it is implemented, and malicious hackers try to break it.)
Others are unhappy that Blockstream is putting so much effort into deploying SegWit, instead of other things like fast block propagation. The reason for the hurry is that SegWit is needed for the LN (or some other thing that Blockstream is planning and did not tell).
OK??? Besides a bunch of whiners on reddit or some other bitcoin forum, who of significance is actually opposed in any meaningful way to seg wit? Name someone, or cite to their objections. As far as I know, there is no meaningful disagreement to the implementation of seg wit, except for insignificant whiners in various bitcoin forums. There is no one with a meaningful position in bitcoin, either merchants, developers or miners who are voicing any meaningful objection to seg wit. They may be complaining about other things, such as also wanting to get a hard increase in the limit, but those are convoluted arguments, and in the end, there is no meaningful objection to seg wit - if so show who that is.
Hard forks are not more dangerous than soft-forks. One can argue that they in fact safer, because they must be executed openly and be accepted in advance by a large segment of the users.
They are more dangerous if there is disagreement regarding their implementation, and they are more dangerous if they attempt to change bitcoin's governance in order to make changes (consensus rules) easier to achieve.
.......
Besides, there will be some hard fork in the future, for other reasons (such as increasing the min block size). The alternative malleability fix (that does not require the split-block format) could be deployed in the same hard fork.
Yes, likely there will be some hardforks in the future, and probably those hardforks will be regarding non-controverted topics (and likely have a very large consensus, such as much more than 95%).
SegWit makes bitcoin more complicated: the split blocks and transactions, Luke's script hack, the fee formulas, etc.
Increasing the complexity of the protocol makes it harder to explain and master (many docs will have to be edited) and harder to maintain. Increased complexity means that fewer people will qualify to maintain the code, and to write applications that depend on the format.
You keep going back over the point to argue against something that is not controverted, and it does not really matter, at this point how complicated it is, etc. etc.. because it is already in the pipeline to be implemented, and you better come up with some more major flaws in order to cause a reverse of this course of action. So, you can whine and whine and whine, but it is really not very productive because the substance of your whining does not rise to a high enough level to be material enough to change what's already in the works. On the other hand, if you were working on solutions to various problems, rather than just whining about the existence of problems, then that would likely be more productive towards the dialogue - rather than attempting to cause confusion amongst people (but, when by definition you are in the business of spreading FUCD, then I suppose you are not really capable (or you won't get paid) of more meaningful kinds of contributions to the discussion).