It looks like you're new here. If you want to get involved, click one of these buttons!
Issue: EOS currently appears to have an ineffective RAM policy which is hostile to all but the most trivial dApp developments.
Recommendation: Please do not approve the mainnet launch until these issues have been properly addressed.
Concern: Launching the mainnet with such a serious outstanding issue could render it very difficult to change or repair in the future, leading to a situation where EOS itself is simply forked into a new project which does not suffer from the deficiency. This may conceivably lead to a situation where all stakeholders in EOS lose.
A recent thread has started on the github discussion forum surrounding the apparently new requirements for staking RAM in order to create an account on the mainnet.
EOS is a smart contract platform, not an end user platform. It is the dApps built on top of EOS which will ultimately give the project value. Understanding this, it is important to properly address the needs of the smart contract and dApp developers. This means the contracts need to be the ones staking RAM and bandwidth, not the individual user accounts. The user experience is paramount. EOS should not get in the way of this, meaning a dApp needs to look and feel independent, with all aspects of the EOS chain hidden from the user experience.
The consequence of this is that most users should not even realize they are working on top of EOS, and they could have dozens of different accounts on the mainnet, each one belonging to a different dApp. Middleware may develop in the future to help end users manage these different identities, but in order to get marketshare, it is important that EOS be viewed by the development community as a tool, and not an obstacle to be worked around. The working philosophy should recognize that many end users will not hold EOS at all.
Failure to adopt this attitude will ultimately lead to a split in the nascent community, and a fork into a new community that does accept these principles. Such a community is likely to be ultimately more successful than EOS, as it is friendlier to the developers and to the end users.
Unless Dan or Blockone can explain why the issues raised in the above thread are incorrect, I recommend everyone hold off on approval of the mainnet until this very serious is resolved.