So, I interpreted your comment as "No, there's no use cases currently identified that couldn't be done far more effectively without a blockchain, and well, that's a fair point".
Here's the thing - I work with Kafka a lot. It's a complex piece of technology, people using it incur real costs, both financially and in terms of system complexity. But it's great for some use cases. And terrible for others. You could use it to replace RabbitMQ or ActiveMQ etc., but that would generally be a bad idea, a distributed log isn't a message queue.
However, it has use cases where it shines.
If you were to ask me about the use cases where Kafka is genuinely better than other technologies, I can easily provide them.
I wouldn't say "Well, you've really got to dive into the technology itself and the opportunities presented by the platform". I'd just give you actual use cases where a distributed log is superior to other technologies.
So, should be easy to do that for Web3 stuff right?
Here's the thing - I work with Kafka a lot. It's a complex piece of technology, people using it incur real costs, both financially and in terms of system complexity. But it's great for some use cases. And terrible for others. You could use it to replace RabbitMQ or ActiveMQ etc., but that would generally be a bad idea, a distributed log isn't a message queue.
However, it has use cases where it shines.
If you were to ask me about the use cases where Kafka is genuinely better than other technologies, I can easily provide them.
I wouldn't say "Well, you've really got to dive into the technology itself and the opportunities presented by the platform". I'd just give you actual use cases where a distributed log is superior to other technologies.
So, should be easy to do that for Web3 stuff right?