ebenezerdon
Joined 7 years ago
Karma
37
Submissions
34
Member since
Sep 25
Recent submissions
Comment · 1 year ago
Comment · 1 year ago
Sorry it came off that way. Not my intention, and to be more direct, I'm not hiding it and do not wish to. Sorry again about that.
Appwrite is fully open-source, which is a big reason I stand behind it.
My role is to represent the developer community and surface their needs, not build the internals. So when I say I like where Appwrite is going, it's coming from that perspective.
You can check my HN post about Appwrite Sites here: https://news.ycombinator.com/item?id=44027691
And just to circle back: Appwrite is fully open-source. I use it in my own products and experience it as a user: https://github.com/ebenezerdon
Comment · 1 year ago
Yes and open about it. You can check my other HN posts, including the last one about Appwrite Sites, where I mentioned I'm a team member: https://news.ycombinator.com/item?id=44027691
I also build with Appwrite, so I experience it as a user. You might have noticed some of my products on GitHub, including https://nextjob.work
Comment · 1 year ago
Link to Appwrite Sites: https://appwrite.io/products/sites
I don't think it is. At least, not yet.
Useful? Sure.
Production-ready? Not even close.
MCP introduces a new layer you now have to secure, monitor, and debug. It relies on stateful connections, breaks serverless patterns, and opens up some scary security holes if you're not careful.
Don't fall for the "spec equals maturity" trap. It's okay to wait.