I'd say mainly it's nice seeing your data in the new blob sidebar panel next to sqlite data and the code that uses both. But also from the blog post:
> Scope blob storage is isolated by val, rather than by account. This simplifies things for when you might need to transfer a val from one organization to another, or list only the blobs that were created by one specific val.
> In the old days (before yesterday), blob storage was scoped by your user account or organization. In the rare case that two vals wanted to access the same blobs, this was nifty, but in the more common case we'd see vals accidentally overwriting each others data. And there was no connection between a blob and the val that wrote it, so you couldn't transfer a val without losing access to all of its blobs.
Thanks! And btw I didn't perceive your comment as negative! More a helpful confirmation of what we've been thinking: "yeah, we have a messaging/positioning problem"
This comment thread was a nudge to push out a quick experimental change to the val.town landing page, so thank you. Very open to feedback on that messaging if anyone has any. Most customers these days ask about using val town with claude code, so you could also think of us as a deployment platform for vibe coded apps
Hey, I work at Val Town, and we definitely struggle to describe what it is because the platform is so broad, but I'll try: a javascript code editor in the browser that auto-deploys that code to our servers whenever you edit a file. You can run code by clicking a button, on a cron, via HTTP. And there's other stuff like SQLite and blob storage
So yes, like Cloudflare Workers in some ways. Or like CodePen but fullstack. Or Replit. The val town "founding poem" was:
> You can change which resolver you use in your network settings. I switched to 1.1.1.1 on my machines - it's noticeably faster than my ISP's default resolver.
Noticeably faster as in just loading a website? Or in some script where small differences add up? I thought typical DNS lookup was sub 100ms, but I've never tried switching my resolver so I'm curious
This is a first draft blog post version of a talk I'm giving at a startup conference next week. I am looking for feedback.
Please comment here or reply on the blog itself if I got something wrong or you have something to add. Personal anecdotes and cited sources are great, but I'm also curious to hear end-of-the-bar opinions.
> Scope blob storage is isolated by val, rather than by account. This simplifies things for when you might need to transfer a val from one organization to another, or list only the blobs that were created by one specific val.
> In the old days (before yesterday), blob storage was scoped by your user account or organization. In the rare case that two vals wanted to access the same blobs, this was nifty, but in the more common case we'd see vals accidentally overwriting each others data. And there was no connection between a blob and the val that wrote it, so you couldn't transfer a val without losing access to all of its blobs.