Row 31889

Row ID: 31889 | Dataset Entry | Axioma AXP Content Repository

Content Data

This page contains data entry 31889 from the Axioma AXP content repository. The structured data below represents the complete record for this entry.

I've worked a little bit in Go-Ethereum, and to me it seems like a lot of unnecessary complexity has been added very recently. I first considered using older versions, but now using recent ones for now. The problem isn't the codebase, it's that the protocol itself has been changed. And probably not in a good way. Part of it is the chase after scalability. Ethereum was a revolutionary technology. It was already a complete product, but still wanted to turn itself into some kind of sharded parallelized system. So then you have the "Dank Sharding" thing, that as far as I know could run as a separate service using state channels (thus add zero complexity to the Ethereum protocol and node codebase), but instead it is being built-in to the protocol and validators/miners are made to participate in it. Then you have to add a second transaction type, and you need to generalize an interface for transaction types, and with enough similar (and unnecessary as in the protocol would work without it) changes, you get a lot of complexity. The whole EIP system too, with changes constantly, means you have codebases that account for all changes, and when (at what block or time) they happened, and then you get a lot more complexity that is not really necessary if the system was planned out from the start, but have to be added when you change it on the fly. That I don't think is too much of a problem, it's more things like "Dank Sharding" that is destroying the codebase and protocol I think.

FieldValue
text I've worked a little bit in Go-Ethereum, and to me it seems like a lot of unnecessary complexity has been added very recently. I first considered using older versions, but now using recent ones for now. The problem isn't the codebase, it's that the protocol itself has been changed. And probably not in a good way. Part of it is the chase after scalability. Ethereum was a revolutionary technology. It was already a complete product, but still wanted to turn itself into some kind of sharded parallel…
label r/ethereum
dataType comment
communityName r/ethereum
datetime 2024-05-21
username_encoded Z0FBQUFBQm5Lak1HVHIzbHo5MU0yaTFqb3lRNXVOSTlzdTdrNTRvS1RVNHp0NlprZmJOaXk5MXFwbDFkd2pKZnh2UGRfRHF2VUgzWVRMMG5VMm14b2dUNzdsaU9xQnluLUE9PQ==
url_encoded Z0FBQUFBQm5Lak9XcFBaUW1HcTl5SnJMNHRuX2d1WVhjV1hKUFgxa0NhbVRQTjNFSWtHU2JZeDREdXFfTlZEaTFUaTVBejVWRk5FZ1F2aDM5ejVhd19DbkI4Q29reVFjaENBUVc4SjdhTXdvNmhXRUt5czVrS1hGR1JVNVQ4a05ERkNmTkQtbVc2MjdGcnRZcmpSbDNUaS0yZW9QWmowdlFLWktrdi12dmRGMmluMzJIRER1ZG5wZWQ1ZXo0QnFBRkVBblhOMzlDS1ds

Raw Record

{
  "text": "I've worked a little bit in Go-Ethereum, and to me it seems like a lot of unnecessary complexity has been added very recently. I first considered using older versions, but now using recent ones for now. The problem isn't the codebase, it's that the protocol itself has been changed. And probably not in a good way. Part of it is the chase after scalability. Ethereum was a revolutionary technology. It was already a complete product, but still wanted to turn itself into some kind of sharded parallelized system. So then you have the \"Dank Sharding\" thing, that as far as I know could run as a separate service using state channels (thus add zero complexity to the Ethereum protocol and node codebase), but instead it is being built-in to the protocol and validators/miners are made to participate in it. Then you have to add a second transaction type, and you need to generalize an interface for transaction types, and with enough similar (and unnecessary as in the protocol would work without it) changes, you get a lot of complexity. The whole EIP system too, with changes constantly, means you have codebases that account for all changes, and when (at what block or time) they happened, and then you get a lot more complexity that is not really necessary if the system was planned out from the start, but have to be added when you change it on the fly. That I don't think is too much of a problem, it's more things like \"Dank Sharding\" that is destroying the codebase and protocol I think.",
  "label": "r/ethereum",
  "dataType": "comment",
  "communityName": "r/ethereum",
  "datetime": "2024-05-21",
  "username_encoded": "Z0FBQUFBQm5Lak1HVHIzbHo5MU0yaTFqb3lRNXVOSTlzdTdrNTRvS1RVNHp0NlprZmJOaXk5MXFwbDFkd2pKZnh2UGRfRHF2VUgzWVRMMG5VMm14b2dUNzdsaU9xQnluLUE9PQ==",
  "url_encoded": "Z0FBQUFBQm5Lak9XcFBaUW1HcTl5SnJMNHRuX2d1WVhjV1hKUFgxa0NhbVRQTjNFSWtHU2JZeDREdXFfTlZEaTFUaTVBejVWRk5FZ1F2aDM5ejVhd19DbkI4Q29reVFjaENBUVc4SjdhTXdvNmhXRUt5czVrS1hGR1JVNVQ4a05ERkNmTkQtbVc2MjdGcnRZcmpSbDNUaS0yZW9QWmowdlFLWktrdi12dmRGMmluMzJIRER1ZG5wZWQ1ZXo0QnFBRkVBblhOMzlDS1ds"
}
Explore Dataset Explore Row

Entry Information