petemilly

Thanks. I also just saw Ben Werdmuller recommends Zen https://werd.io/why-im-all-in-on-zen-browser

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:

> If GitHub Gists could run,

> And AWS Lambda were fun

> 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.

Thank you!

https://blogroll.org is a neat project that curates personal blogs. One of the curators (Manu) also has a weekly blogger interview series that I enjoy: https://peopleandblogs.com

Great! Thanks for following up.

And yep, the browser date picker (https://developer.mozilla.org/en-US/docs/Web/HTML/Element/in...) is a major time saver. This project uses the native color picker, too.

Oh nice, I hadn't heard of Bliss.js, but the creator (https://lea.verou.me/) is great.

Oh cool, I didn't know about field-sizing. Thanks.

And yeah, this definitely set off my alarm bells like "maybe I shouldn't be using React here." I guess the initial goal was just getting something that works out there using the thing I know best (React), and the second phase could be a rewrite using a better tool for the job-open to any thoughts and suggestions on that.

I was thinking about this, too. Allowing setting a date of death felt pretty morbid...

Thanks. And yeah, I was talking to my roommate about enabling edits in the future. I guess the spirit of the site is letting each person do with it what they wish, so I suppose I should open up future dates for edits.

Thanks for pointing this out (all comments in this subthread). I just updated the date picker to only re-render the grid of weeks when the input is unfocused (onblur) and avoid the unnecessary intermediate updates. Still more work for me to address lag, but hopefully that helps.

Feel free to fork the repo and run locally! https://github.com/pmillspaugh/weeksofyourlife

Maybe I could add an export feature that downloads the data in a .csv or something. The URL storage is definitely a bit wonky, but more robust persistence felt like overkill (maybe I'm wrong about that, though!).

Thanks for pointing this out. I just updated it to only re-render the grid of weeks when the date input is unfocused (onblur) rather than unnecessarily updating the grid while you're still entering the date.

Ah, sorry about that. It is the native date picker as n8cpdx pointed out.

I just pushed an update to only update the grid of weeks once the date picker is unfocused (onblur event) rather than recomputing unnecessarily on every change event. I suspect that is what caused the bug you're describing, but let me know if it's still broken.

Thanks, and go for it! I'd be interested to see your remix if you end up getting to a landscape/place footer

Thanks for pointing this out. I updated it to allow drag/pull on mobile (prevent the pull-to-refresh with CSS `overscroll-behavior: none` on touch events).

Setting a cookie is a good idea—I honestly just didn't think of it. I created a todo for myself to explore that whenever I can get around to it.