> the third party, unaffiliated, developer experience is better on an EVM than it is is on a traditional centralized database.

This is definitely a take, given how easy it is to write a program with security bugs using Solidity due to specific concerns like reentrancy that only exist due to the unique way smart contracts work. The inability to "undo" a fraudulent or mistaken transaction without requiring all validators to fork the chain also makes this a non-starter for many developers.

> your users pay to update the state of your application

Also a weird thing to call a "feature" for developers when this actively drives away potential users.

> Also a weird thing to call a "feature" for developers when this actively drives away potential users.

while being a funnel of 1 step for the users already in the ecosystem that find your application

the ecosystems turns the entire Web 2.0 marketing funnel industry on its head because the initial call to action is a payment. All of the mystery of converting to a paying customer is obsoleted in favor of unbridled commerce

this just points out another way its optimal for developers with ideas, when aiming for revenue in a web3 architected project for crypto natives. they have frictions, you solve them, they pay you. If you aren’t catering to crypto natives already, don’t launch a web3 application. the space is already big enough to ignore other potential users, and if you want that to be your cause to help the UX to grow the space, you can do that too.

> security bugs using Solidity

To your other point, I don't see 2016's smart contract coding problems as show stopping criticisms, because this is the lowest hanging fruit of experience for anyone learning solidity, all while standardization of open source methods has solved those building blocks just like in other languages. additionally, you can write an insecure application in the web 2.0 space as well.

There are enough and a growing number of developers that aren't afraid of deploying code on a blockchain. a lot has happened in the last ... decade? developer tooling has improved.

yes, the developer experience is better on a platform where you can write code (potentially with bugs) than a platform where you can’t write code or do anything programmatic at all.