3 ms·

There are many use cases for service workers you probably haven't heard of. For example at my last job (at a YC startup) we built a service worker that used P2

by inglor 6y ago

There are many use cases for service workers you probably haven't heard of. For example at my last job (at a YC startup) we built a service worker that used P2P to serve mp4 video over WebRTC. It was the correct place to interop with the download - it was explicit and it would have been impossible without it. ---- I think the common use case (of much control over caching) is also quite reasonable. I agree the API and usage is too hard.

fxtentacle 6y ago
"it would have been impossible without it" C++ desktop app It'll even have 2x the throughput at the same CPU level. Plus users can choose when they want to run your app, as opposed to you accidentally draining their battery because they left an old tab open. Boom, possible and better :p
- SirHound 6y ago
  Better = higher barrier to entry?
  - fxtentacle 6y ago
    Less behavior that users are surprised by in a negative way.
    - srtjstjsj 6y ago
      Except for the remote code execution.
- jakelazaroff 6y ago
  "Better" is subjective. Web apps sacrifice performance, but you get an app that you don't have to install, that can't do anything malicious to your system without your consent, that's (at least in theory) easily shareable and deep linkable. Maybe that tradeoff isn't worth it for you, but it is for a lot of people!
  - corytheboyd 6y ago
    Yeah this is the point right here that seems to be so easily forgotten. You lost every non-programmer at “okay download this binary and run it from the terminal with these flags”
    - Santosh83 6y ago
      Not really. Non-programmers have also been using computers ever since the PC revolution and are quite used to downloading, installing and running programs, provided it has a usable GUI. After all, web apps are very recent. Even now, most programs are installed, and the rest are websites.
      - jakelazaroff 6y ago
        Web apps are relatively recent, sure. But the web is three decades old at this point. The majority of people using computers today grew up with web apps being a thing. It's difficult to verify, but my guess is your stats are backward: most programs are websites, and the rest are installed.

by inglor 6y ago

fxtentacle 6y ago

"it would have been impossible without it" C++ desktop app It'll even have 2x the throughput at the same CPU level. Plus users can choose when they want to run your app, as opposed to you accidentally draining their battery because they left an old tab open. Boom, possible and better :p

SirHound 6y ago
Better = higher barrier to entry?
- fxtentacle 6y ago
  Less behavior that users are surprised by in a negative way.
  - srtjstjsj 6y ago
    Except for the remote code execution.
jakelazaroff 6y ago
"Better" is subjective. Web apps sacrifice performance, but you get an app that you don't have to install, that can't do anything malicious to your system without your consent, that's (at least in theory) easily shareable and deep linkable. Maybe that tradeoff isn't worth it for you, but it is for a lot of people!
- corytheboyd 6y ago
  Yeah this is the point right here that seems to be so easily forgotten. You lost every non-programmer at “okay download this binary and run it from the terminal with these flags”
  - Santosh83 6y ago
    Not really. Non-programmers have also been using computers ever since the PC revolution and are quite used to downloading, installing and running programs, provided it has a usable GUI. After all, web apps are very recent. Even now, most programs are installed, and the rest are websites.
    - jakelazaroff 6y ago
      Web apps are relatively recent, sure. But the web is three decades old at this point. The majority of people using computers today grew up with web apps being a thing. It's difficult to verify, but my guess is your stats are backward: most programs are websites, and the rest are installed.