41–49 of 49 posts
> Remember! AESTHETICS ARE VERY IMPORTANT. All apps should LOOK AMAZING Why are your database instructions giving instructions about the UI design?
The GET request method is supposed to be safe. "Request methods are considered 'safe' if their defined semantics are essentially read-only; i.e., the client does not request, and does not expect, any state change on the origin server as a result of applying a safe method to a target resource." -RFC 9110 section 9.2.1 https://www.rfc-editor.org/rfc/rfc9110.html#name-safe-method...
Here's my argument: In practice many GET requests don't adhere to this spec. For example, when you load a page, your "view" generally changes lots of things on the backend. Those changes come back to you in ways too: for example, consider view counts on Youtube videos or X posts.
This is very cool! But why do we need this? An agent can just have a local DB using SQLite for example.
Two reasons this could make sense: 1. With this, agents can actually deploy a full backend with their credentials [^1]. 2. If your agent ever wants to add auth, or real-time presence, or file uploads, or streams, they'll be able to do that too [^1] Alas we don't offer static site hosting, so to push the website you would need to use something like a vercel cli.
> Remember! AESTHETICS ARE VERY IMPORTANT. All apps should LOOK AMAZING Why are your database instructions giving instructions about the UI design?
Instant gives you a database, but it also gives you a sync engine that you can use in the frontend. We included this instruction because you would ideally use this to build an app.
What if the app is headless and the LLM tries to stick a UI on it? What if the app is a TUI and the LLM gets stuck on terminal fonts? What if my UI aesthetic is grungy hackercore and the LLM tries to make it look like every other Tailwind website?
This criticism/feedback is less about what's written, and more about why it was deemed appropriate. You're getting direct input to the development process of your customer's products, and you're using that responsibility to... make pointless comments about design?