> Yes, it hasn't taken any shortcuts or sacrifices to the blockchain trilemma
Eth has sacrificed on scalability. Whether you find that the balance is subjective.
Cardano's issue to this point is that their eUTXO model and their smart contract tooling is a bit too esoteric for the current crypto community. What you get in return is deterministic and verifiable smart contracts. Whether that will matter in practice time will tell
Eth didn't come up with the rollup design.
I agree with your Steve Balmer take, but the rest of your assessment is something else.
How do you manage sensitive data with this workflow (i.e. do you do it manually everytime, do you automate it, what scripts, etc.)?
I get changing passwords, but say that data leaks (whether by a vulnerability in the clone environment, or by a dev gone rogue), how do you mitigate possible damage done to real users (since you did clone from prod).
I ask not because I question your actions, but because I've been wanting to do something similar in staging env to allow practical testing, but I haven't had the chance to research how to do it "properly".
This is no different from the "first" comments in youtube or when sharing a meme to a friend that has already seen it and says "I've seen that already" instead of discussing essence of the content itself.
I'm not a fan of modern js-ridden site implementations but a search engine that displays a resource different from what will actually be consumed by the user is a bad search engine.
Perhaps you can put the blame on the creator of the site, but that won't bring us anywhere if we just allow people to game the system.