4 ms·
I believe the author has been very careful in saying "if no perfect solution exists they seem ok with inaction", highlighting a different problem from "let's ba
by riffraff 11y ago
I believe the author has been very careful in saying "if no perfect solution exists they seem ok with inaction", highlighting a different problem from "let's bang out code that sorta works and move on.
Also, poor communication skills and "immaturity" have also been a "traditional" problems in FLOSS too.
Being unwelcoming to new devs is especially a big problem for a project that _is already_ losing the old trusted devs.
- kang 11y agoUnwelcoming to new devs is not true. Who wrote code & wasn't let in? Also, go to the bitcoin irc and try asking technical questions and observe how everyone is so willing to help new devs looking to get in.
- microcolonel 11y agoI feel like people are generally comfortable making the assertion that the community is unwelcoming; but those making the assertion generally don't seem to be able to back it up. A welcoming community doesn't need to coddle everyone who might send a patch, because that's a lot of people. If they want to succeed, they should document enough to get started, and review unfinished patches.
- riffraff 11y agosorry if I was unclear but I am not backing the assertions, I am just saying that the critique to what is written is invalid. The comment I replied to does not challenge the assumptions, but the conclusions. Whether the assumptions are true or not, I do not know.
- makomk 11y agoFor context, here's the Bitcoin Core developers' position on why they're not simply raising the block size right now: https://bitcoin.org/en/bitcoin-core/capacity-increases-faq#size-bump https://bitcoin.org/en/bitcoin-core/capacity-increases-faq#s...
- Angostura 11y agoThank you. That clearly shows that some people associated with the core team have very good communications skills.
- jackgavigan 11y agoDon't be so bitter. ;-)
- jeremyjh 11y agoWhy do you think a bitcoin core developer wrote the FAQ? In a large project like this it is not at all unusual to have documentation written by people outside the core development team. In fact you can go look at the history of this page, David Harding wrote most of it and I do not see any commits from him in core. https://github.com/bitcoin-dot-org/bitcoin.org/commits/master/en/bitcoin-core/capacity-increases-faq.md?author=harding https://github.com/bitcoin-dot-org/bitcoin.org/commits/maste...
- ikeboy 11y agohttps://github.com/bitcoin/bitcoin/commits?author=harding https://github.com/bitcoin/bitcoin/commits?author=harding
- nullc 11y agoPart of having effective communication is having people on your wider team that are experts in that area, even if they aren't one of the people writing all the software.
- Angostura 11y agoI don't - I said specifically: "people associated with the core team" As long as the core coders can associate and work well with good communicators, it's all good as far as I'm concerned.
- Angostura 11y agoUntil you get half way down the article and discover that the Core developers aren't simply proposing inaction: > It is worth noting that bitcoin core’s response to scaling has been to propose a solution called segregated witness. While it is a well done piece of technology, I believe it would be quite risky
- Natanael_L 11y agoSegWit can only reduce bandwidth for clients that don't need to perform full validation. Blocksize is otherwise unchanged. Miners' and payment processors' bandwidth requirements are unchanged. Lightweight wallets does benefit, as does the nodes/servers they get their data from.
- ikeboy 11y agoThe point is increasing transactions that can be included without hard forking.
- Natanael_L 11y agoAll fully validating nodes must still download all the signature data. The total can not exceed 1MB per block without forking. SegWit does not reduce transaction sizes. SegWit is not a compression technique, it is a bandwidth redundancy reduction technique. It simply makes it so that some nodes doesn't need to fetch all of the transaction data.
- sonoffett 11y agoTake a look at the discount for segregated witness transactions. You'll see that in a world with segwit there are more transactions per block than without.
- Natanael_L 11y agoCan't be done without forking if the total data per block required to validate all the transactions exceeds 1 MB. Old full nodes will reject the blocks. Only compression or merging can increase the transaction count per block without becoming incompatible with old full nodes.
- Angostura 11y agoUntil you get half way down the article and discover that the Core developers aren't simply proposing inaction: > It is worth noting that bitcoin core’s response to scaling has been to propose a solution called segregated witness. While it is a well done piece of technology, I believe it would be quite risky