Earlier quoted context omitted.
Web3 is decentralized web, like web 1.0 - but with tokens this time! Tokens solve the issue because you can buy and hold them and get rich! Buy my shitcoin! Seriously web3 is just another way to create hype for arbitrary crypto tokens and Ethereum. In a few years there will be something else - quantum web or something to suck new buyers in.
This doesn’t provide any value to the conversation. Imagine having good intentions, working in web3, and always seeing this type of comment on HH. Would you want it that way in whatever field you’re working in?
Show HN: 0xFast – Faster Web3 APIs
51–60 of 71 posts
Re: Show HN: 0xFast – Faster Web3 APIs
#52Earlier quoted context omitted.
The descriptions made absolute sense to me, the target audience - someone developing with these systems. You can complain about it if you want, but it's like complaining that serverless things need servers underneath - maybe technically accurate but not a helpful discussion to have.
"Serverless" is a terrible adjective, and yet it's still considerably more precise than "web3". Even so, in a technical setting I often hear engineers refers to "hosted function" or "function service" when referring to "serverless" infrastructure.
Re: Show HN: 0xFast – Faster Web3 APIs
#53No sure what the purpose of this really is. But the pricing seems bizzare. Hetzner cloud costs 1€ per extra TB (20 included) while this costs 2$ per Gb. That is an order of magnitude so what am I paying for?
Re: Show HN: 0xFast – Faster Web3 APIs
#54Earlier quoted context omitted.
It's not arguing about the difference between web2 and web3. It's arguing two main things 1. Web3 data is different from what most classic databases are optimised for, because of how it's accessed and the (mostly) immutable guarantees. 2. This service is better than other web3 api providers. FWIW I'm consulting in this space currently, specifically dealing with blockchain data itself and it makes perfect sense to me.…
> The only thing relevant here is that blockchain data is almost exclusively append-only and so you can build something neater because you've got guarantees that many other problems don't have. Append only databases have been around for decades. Heck Kafka is an obscenely popular example today. I've talked to people working in fields with legally mandated immutable databases, again decades old technology. In the most…
Re: Show HN: 0xFast – Faster Web3 APIs
#55Earlier quoted context omitted.
Web3 is decentralized web, like web 1.0 - but with tokens this time! Tokens solve the issue because you can buy and hold them and get rich! Buy my shitcoin! Seriously web3 is just another way to create hype for arbitrary crypto tokens and Ethereum. In a few years there will be something else - quantum web or something to suck new buyers in.
This doesn’t provide any value to the conversation. Imagine having good intentions, working in web3, and always seeing this type of comment on HH. Would you want it that way in whatever field you’re working in?
Re: Show HN: 0xFast – Faster Web3 APIs
#56Earlier quoted context omitted.
Name one Web3 use case. There are more use cases for email than scamming.
I could list examples like this[0] or convince you that I'm a pretty healthy web3 skeptic who still doesn't round the valid use cases to 0, but I suspect you've already made up your mind and are just trying to be a stubborn internet arguer [0] https://www.cnbc.com/2022/03/23/ukrainian-flees-to-poland-wi...
Re: Show HN: 0xFast – Faster Web3 APIs
#57Earlier quoted context omitted.
Name one Web3 use case. There are more use cases for email than scamming.
I could list examples like this[0] or convince you that I'm a pretty healthy web3 skeptic who still doesn't round the valid use cases to 0, but I suspect you've already made up your mind and are just trying to be a stubborn internet arguer [0] https://www.cnbc.com/2022/03/23/ukrainian-flees-to-poland-wi...
Re: Show HN: 0xFast – Faster Web3 APIs
#58> The solution to this problem becomes more complex with scale. Distributed transactions, sharding, replication, and fault tolerance are notoriously slow. And yet, suprisingly (not) they power everything at scale unimaginable to anything happening in crypto. The "amazing scalable crypto" barely manages the complexity and scale you can easily run from a Raspberry Pi with a sqlite database. > We built a cheaper and sim…
> Translation: you are dumping blockchain data into traditional databases running on traditional servers and backed up by a traditional Elastic Search. It's ironic that the solution to blockchain problems is so often re-centralization.
It's absurd to claim that something is decentralized when there is always team at the core of this so-called decentralized network whose self-appointed job is to maintain its state of decentralization.
I would argue that there is no such thing as any intentionally decentralized anything, and all claims as such should be treated with extreme skepticism. "trust us, it's trustless."
The only decentralized phenomena are ones that come to us from the universe itself. And even those can ultimately be traced to an origin so the decentralization is only a local phenomena anyway.
Re: Show HN: 0xFast – Faster Web3 APIs
#59Maybe I'm misunderstanding this. However - the bottleneck in the blockchain is not the read/writing of the APIs (which might be slow), but the main bottleneck is the settlement of the chain usually. For example, the settlement of a block on the Bitcoin blockchain takes about 10 mins. No matter how fast you make the throughput of all the APIs, settlement will still be slow. If this is strictly for the historical use c…
Re: Show HN: 0xFast – Faster Web3 APIs
#60> The solution to this problem becomes more complex with scale. Distributed transactions, sharding, replication, and fault tolerance are notoriously slow. And yet, suprisingly (not) they power everything at scale unimaginable to anything happening in crypto. The "amazing scalable crypto" barely manages the complexity and scale you can easily run from a Raspberry Pi with a sqlite database. > We built a cheaper and sim…
> Translation: you are dumping blockchain data into traditional databases running on traditional servers and backed up by a traditional Elastic Search. It's ironic that the solution to blockchain problems is so often re-centralization.