3 ms·

> However, their no-code approach generates awful code difficult to follow, making apps less reliable. Moreover, using a UI is slower than coding, especially no

> However, their no-code approach generates awful code difficult to follow, making apps less reliable. Moreover, using a UI is slower than coding, especially now that AI assistants are here to help you. I don't get this one, the sentence "their no-code approach generates awful code". If it's no-code, why do you care about code ? Also, in what way are you relying on "coding" ? No information on this on the front page, to me it seems just like a config file only. Are you saying that the config only generates the boilerplate that the user will modify afterwards ? If that's the case, it's really not obvious.

brunaxLorax 2y ago
Hi there ! Dev here, thanks for the feedback. Yes the example in the homepage (https://manifest.build/ https://manifest.build/) generates the DB, Admin panel and REST API, we will adapt if it is not clear. You asked an interesting question: "should you care about code quality if you use no-code tools?": As a developer, I would say definitely say yes because not understanding your own code (or your team's code) will soon or late lead to issues. If you work on a team with PR validations or similar, how can you validate your teammates' code if the code is unreadable ?
- kiwicopple 2y ago
  (Supabase team member) Congrats on shipping, this looks nice and well thought-out One possible correction: the only code we generate for a user is either SQL migrations or TS types (if devs want to use the TS client). I’m not sure many would classify Supabase as NoCode, and we strongly recommend users use CI/CD development with our CLI and database migrations https://supabase.com/docs/guides/cli/local-development#database-migrations https://supabase.com/docs/guides/cli/local-development#datab...