After some time developing on nostr, "simple protocol" makes development a real pain. Nostr isn't picking up steam anytime soon. Less devs => worse UX => slow death.
There is a need for good frameworks/programming libraries, but from the experience of Ethereum web3, I can confidently state that no breakthrough libraries are on the horizon.
I'm thinking that NIPs should be gatekept by introducing libraries to deal with said NIP first.
lynn / Lynn Zenn
npub1ze…wp3st
2023-04-11 19:18:12
Author Public Key
npub1zenn0vgcy2st7dz7gexxtuuan860ucryg26kdlnap2kndwrqmy0swwp3stPublished at
2023-04-11 19:18:12Event JSON
{
"id": "95feb771bb9deed3f9a4aab4e1d2c5b255815b92db2fd1714ec31e6191724c7a",
"pubkey": "166737b11822a0bf345e464c65f39d99f4fe606442b566fe7d0aad36b860d91f",
"created_at": 1681240692,
"kind": 1,
"tags": [
[
"client",
"coracle"
]
],
"content": "After some time developing on nostr, \"simple protocol\" makes development a real pain. Nostr isn't picking up steam anytime soon. Less devs =\u003e worse UX =\u003e slow death.\n\n\nThere is a need for good frameworks/programming libraries, but from the experience of Ethereum web3, I can confidently state that no breakthrough libraries are on the horizon.\nI'm thinking that NIPs should be gatekept by introducing libraries to deal with said NIP first.",
"sig": "9bc233565f0c307cdeda0a2e5dba4d1ba960950e2630de80808d99d8afc1a49da8e1ced042de997307672ee134d315d4369167af4e835183503777b69bde9ef4"
}