cross-posted from: https://piefed.social/c/technology/p/2007000/meshcore-io-why-the-split-meshcore-blog
Migrating to the new meshcore.io site
Drama happening at Meshcore.
cross-posted from: https://piefed.social/c/technology/p/2007000/meshcore-io-why-the-split-meshcore-blog
Migrating to the new meshcore.io site
Drama happening at Meshcore.
I have a hunch how that might just not happen. If it’s a singular developer pumping out all kinds of features, websites, software… There’s a good chance there’s little oversight nor any proper guardrails in place.
So hypothetically, sure?! In practice I also see how some things sometimes go hand in hand. And you better check who writes and maintains your software, if you’re planing to use it long term. At least that’s what I’ve seen. Once a project is mostly vibe-coded, there’s automatically a high chance there’s weird things going on. Or I’ll write something to the issue tracker and there’s nobody there. Or maintenance stops after a week because they vibe-code the next thing… So I’m a bit wary. I guess because in reality lots of people don’t use these tools responsibly.