all 11 comments

sorted by: hot top controversial new old
[–] 8 points 6 months ago (4 children)

I've noticed a lot of consumer embedded products have been using PWAs for flashing and configuring devices (Meshtastic, Meshcore, Betaflight, am32 configurator, etc). I have to open Chromium to use them because they don't work with my normal browser (and I probably don't want my normal browser being able to access arbitrary USB devices).

  • source
  • hideshow 4 child comments
  • [–] 1 point 6 months ago (2 children)

    Do you prefer to have everything as a native application then?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 5 points 5 months ago (1 child)

    I guess there's a blurry line between an "application" and a web site. But, generally, for open source applications, I'd rather them be native. Preferably, the applications would actually be native (e.g. Qt, GTK, Jetpack Compose, etc).

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 5 months ago

    No, there's a clear distinction between a native application and a website. I could go on and on about my hate for native app and it's difficulty to develop for more than one platform, but the point is only SOME apps needs to be native IMHO. Apps like CAD, multimedia editor and player, server application, and developer toolchain. Something like instant messaging, video conference, multimedia streaming, forum can be a web app.

  • source
  • parent
  • [–] 7 points 6 months ago

    The author just push LLM nonsense. PWA's are great for field app where internet is scarce and without the need to rely on google to keep side loading possible. Not to mention the nightmare if you even want to deploy the side loaded app to a fleet of phone without needing to use google play store to publish it as an internal app.

  • source
  • [–] 3 points 5 months ago* (2 children)

    The author seems to predicate his arguments on the assumption that "the web needs to be the development platform of choice" or something like that? I feel like I kept asking "why does the web need to do all these things" while reading the article; it feels like the author just assumes that a maximalist web platform is desirable? That having everything authored on/for the web is a forgone conclusion?

  • source
  • hideshow 2 child comments
  • [–] 2 points 5 months ago

    Before publishing, that text really needed a self-review/read-through. So many obvious issues to spot. Numerous typos like 'techjnical ', issues like double words 'missing missing', and so on.

  • source
  • [–] 1 point 5 months ago

    Unfortunate, that they didn't include Edge in the Browser feature coverage comparison list.

  • source