Founders

positioning rants 🚀; bringing you ✍️ /buildbetter, 🎙️ /artistspotlight and🎙️ /web3magic; De*** & open-source HW/SW enthusiast; https://nf.td/bfg

in a the fragmented industry that is web3, i actually disagree with adopting the “one thing well” position because its creates more fragmentation. People need composability which means you can just execute on your one part of the system

web3 is perfectly suited for doing just "one thing well" exactly because of its composability

as a dev, i would love to learn how folks have done composability over more than 2 systems well at scale.
I worked as a data engineer over an e2e supply chain and even that experience was less painful than building in web3. 

observably, latency, and complexity are huge pain points here

Pointing out biz mistakes & solving them, Positioning nerd making products Unignorable, also bringing 📬 /buildbetter, 🎙️ /web3magic and /artistspotlight

Coming from an infrastructure background, smart contracts are just another class of micro services.

If you care about latency, then you are either not using smart contracts for writes, or use caches for reads.

Your observability stack is always a separate component anyway, which integrates across all layers via push or pull based collector patterns.

I don't understand your question well and I am just rambling here. If you like we can chat some more!

This is the alt account of Sister Hazel. Writings at https://powerlaw.systems. Curating https://protocol-particles.github.io.

imho we have to challenge this narrative. 

for blockchain to have pmf developers shouldn’t have to make these drastic trade offs. 
if i want to use blockchain for coordination, i should be able to do that without compromising features or using 5+ different tools. 

not just complaining here, im actively working on the fix for this problem.

what is social media if not a place to share your opinions and learn from others? :) 

innovation and progress comes when you demand more from a system, and in my case, build to solve that need, and as it appears, the need of many others. 
 
re: what i want: 

i want to build web3 apps the same way i build web2 apps. 

1. web developers write apps for the browser, not worrying if someone is using x86 vs arm, on an apple or windows machine. i want to have a system that feels like the web browser for web3: where the lower-level (chain) doesn’t matter, it just runs. 

2. in web2, data is abstracted over distributed systems with datastores like cassandra. 
as a dev, i want a unified way to structure, view, and transform my application data with predictable mutations, and the underlying plumbing of the data tier abstracted. meaning, i dont want to stream blockchain data from an indexer to interact with it, and i want more complex data architecture to exist onchain.

I am not sure which narrative you refer to. All there is in life are tradeoffs. The question might be what kind of coordination you are after and how you use a tool. I also don't know what features you are talking about.

IMO there is a blockchain design for every use case you could possibly have and people are working on those to become even better. You can use L1s, L2s, or L3s in all kinds of ways.

If you could provide more context then maybe I could be more useful. But it sounds like you know already what you have to work on, which makes me wonder what the rant here is about.