The most common conflation I see around BSV is lack of sepa…
The most common conflation I see around BSV is lack of separation between app and network expectation.
The network being the sum of all traffic and all aspects (listed previously), and the app being varied and often constrained by specific aspects.
Replies
For successful app deployment, BSV remains better being thought of as a transactional system focused on peak and sustained TPS, but there is wide open space in how to deal with latency and data synchronization dependencies of the app.
Ok services can built for problems but doing this with an app demanding them isn't the way forward. The proposal seems to be that the apps are built to the service.
The apps need to be built to the requirements, that might lead to common services.
what I see ahead, of my own prognostication, is gradual realization that more demanding requirements actual apps are best pursued by designing away legacy server stacks and diminishing of the type of services that some people right now want to build.
meant 'without'