So many products are like this - it sounds good on paper to consolidate a bunch of tasks in one place but it's not without costs and the benefit is just not very high.

"Are you sure you aren't just having trouble?"

Similar concept imo.

My eye doctor said it was my eyes optimizing for what they do the most. And that makes sense, I have no eye strain using a computer.

Interestingly my vision is better in the summer, and when I take holidays during the summer and spent time away from the computer my eyes essentially fix themselves. It takes a couple months back behind a screen to need my glasses again.

I wonder if there could be a variant for Drop which is world wide - imagine being able to join a chat in a foreign country (hopefully you speak the language!) and chat with the locals. I imagine moderation would be a big pain but I could see it being fun and sort of in the spirit of the old web.

I'm more interested in 1) usages of wasm in the browser that don't involve running unmodified unix programs and 2) wasm outside the browser for compile-once-run-anywhere usecases with sandboxing / security guarantees. Could it be the future for writing native applications?

Languages like Kotlin, C#, Rust, as well as C/C++ etc support wasm quite well. Could we see that be a legitimate target for applications in the future, if the performance gap was closer to 10%-ish? I would personally prefer running wasm binaries with guaranteed (as much as possible ofc) sandboxing compared to raw binaries.

edit: it's from 2019, there have been significant improvements made to wasm since then.

Remote: Preferred

Willing to relocate: Yes

Technologies: Typescript, Go, Kotlin, React, Next.js, Svelte, Vue, Postgres etc.

Website: https://benten.ca

Résumé/CV: https://www.linkedin.com/in/bentonbc/

Email: on website

I've been working as a software developer for the last four years, majority of which has been full stack. I have a kinesiology degree and I'm primarily looking to integrate my education with my professional experience, so companies in the health/fitness field basically, but I'm open to all interesting positions. Please check out my site at https://benton.ca, it goes into detail on some of the recent works that I have shipped. Cheers :)

First, I think it's a fact that the average user does not consider a URL to be a state container. The fact that developers in this thread lament the "new school" React developers who don't use the URL as a state container is proof of this. If it follows that a React developer, no matter how inexperienced, is at least as knowledgeable if not more about URLs than the average person, if they don't even consider the URL to be a valid container for state than neither does the average person.

Putting state in the URL breaks a fundamental expectation of the user that refreshing a page resets its state. If I put a page into an unwanted state, or god forbid there is a bug that places it in an impossible state, I expect a refresh of the page to reset the state back. Putting state in the URL violates this principle.

Secondly, putting state in a URL breaks the expectation of the user for sharing locations. When I receive Youtube links from friends, half of the time the "t" parameter is set to somewhere in the video and I don't know if my friend explicitly wanted to provide a timestamp. The general user has no idea what ?t=294833289 means in a URL. It would be better to store that state somewhere else and have the user explicitly create a link a timestamp parameter if the desired outcome was to link to an explicit point in the video. As it stands now, when I send YouTube links to friends I have to remember to clear the ?=t parameter before sharing. This is not good UX.

There are other reasons why I think its a bad idea but I don't want this comment to be too long.

That doesn't mean not to use search parameters though. Consider a page for a t-shirt, with options for color and size. This is a valid use case for putting the color and size in the URL because it's a location property - the resource for a blue XL shirt is different from a red SM shirt, and that should be reflected in the URL.

That's not to say that state should never be put in the URL - in some cases it makes sense. But that's a judgement call that the developer should make by considering what behaviour the user expects, and how the link will most likely be used. For a trivial example, it's unlikely that a user wants to share their scroll position or if a dropdown is open when sharing a page. But they probably want to share the location they've navigated to on a map, as it's unlikely they're sharing a link to `maps.google.com` with others (although debatably that's not state, but rather a location property).