Prosammer

I have very little understanding of geopolitics or economics, so these tariffs don't make sense to me, and they don't seem to make sense to most people.

What’s the best steelman argument for them?

I’ve read a bit of Peter Navarro and others who support this line of thinking, but I’m trying to understand: is there a coherent endgame here that benefits the country long-term, or is this just short-term political theater dressed up as strategy?

What would the best possible version of this policy look like if it were smart?

Check out lanceDB, it looks awesome for this.

Looks cool! Do you see this as something that should be handled by the MCP spec in the future? I'm surprised this isn't built in already.

I wasn’t suggesting anyone should duplicate code or that duplication doesn’t have downsides. My point was more about how LLMs, by default, tend to produce less “clever” (and often more repetitive) code. We know that duplicated code can be painful when bugs need fixing across multiple places, but I’m curious how programming practices will evolve moving forwards as I don't see this going away in the short-term.

>So if you're as clever as you can be when you wrote it, how will you ever debug it?

LLMs do not write very "clever" code by default. Without prompting them continuously to make it more "clever", they tend to write lots and lots of simple code, vs writing "clever" code that reduces redundant code, improves performance, etc.

What I am curious about is if these slop-filled codebases will be a problem or not in the future - traditionally it's been bad practice to have duplicate code everywhere, but with LLMs it feels like it matters less, as long as the code is simple and readable.

Loco is awesome! Hoping that the openAPI generation comes soon - then I can generate zod schemas from the openAPI doc! It would be really cool to use something like hygen/plop or maybe tera (idk) to automatically generate svelte or react CRUD pages, similar to what loco is already doing for htmx.

Caltrain runs reliably and safely for me, can you elaborate?

I'm a big fan of LLMs generally, but does anyone even want incoming texts summarized like this? Like even if they were accurate summaries, seeing "Wife expresses frustration with her husband's messiness" is a lot less fun than "Clean up your clothes, dipshit".

Very cool, congratulations! Would this work for graphql APIs with introspection disabled?

I've been playing with loco.rs to do this! Really cool, let's you use htmx or sveltekit (or whatever you want)

Looks cool! You should fix the "this is how our embedded demo looks like" grammar to say "This is what our embedded demo looks like"

I see what you're saying now, thanks for clarifying.

Sorry for the late response. I must be misunderstanding your comment. I read your comment as "RAG doesn't pre-compute KV for each document, which is inefficient". With RAG, you convert your text into vectors and then store them in a DB — this is the pre-compute. Then you just need to compute the vector of your query, and search for vector similarity. So it seems to me like RAG doesn't suffer from inefficiency you were saying it suffers from.