https://iselmdead.info/ https://dev.to/lucamug/elm-2021-a-year-in-review-4pho
I think most of the Intl api could work reasonably well with ports and custom elements. The formatters in particular, which make up most of the API, would probably work quite nicely as custom elements. It's really only…
A really small thing that would be immensely useful to me would be a quick way to to copy or save as plain text a full HTTP request & response, with a little bit of nice formatting to make it human readable. I often…
Well, now that we have WebRTC, peer-to-peer data transfer is possible in the browser. Perhaps you could imagine a p2p scenario where browser crypto is useful?
It's not always as simple as a PUT landing. Imagine you're tracking something like a phone call in real time. You want to fetch the current state of the call and start tracking it, but it's changing relatively rapidly.…
Disabling the cache by default can be troublesome. I'd say it breaks the principle of least surprise - I wasn't aware of this behavior in Chrome, and it's a good thing I develop with Firefox, as I just resolved a bug…
https://iselmdead.info/ https://dev.to/lucamug/elm-2021-a-year-in-review-4pho
I think most of the Intl api could work reasonably well with ports and custom elements. The formatters in particular, which make up most of the API, would probably work quite nicely as custom elements. It's really only…
A really small thing that would be immensely useful to me would be a quick way to to copy or save as plain text a full HTTP request & response, with a little bit of nice formatting to make it human readable. I often…
Well, now that we have WebRTC, peer-to-peer data transfer is possible in the browser. Perhaps you could imagine a p2p scenario where browser crypto is useful?
It's not always as simple as a PUT landing. Imagine you're tracking something like a phone call in real time. You want to fetch the current state of the call and start tracking it, but it's changing relatively rapidly.…
Disabling the cache by default can be troublesome. I'd say it breaks the principle of least surprise - I wasn't aware of this behavior in Chrome, and it's a good thing I develop with Firefox, as I just resolved a bug…