Earlier quoted context omitted.
It's an ASUS 300M. A pretty high end model when I bought it 4 or 5 years ago, and as a basic PC, running a standard Linux it would be fine for at least 5 more years. But running Chrome OS, it may become a doorstop any time.
Looks like your model should be compatible with GalliumOS: https://wiki.galliumos.org/Hardware_Compatibility So you could go that route, if you like. I ended up doing something similar with my original Chromebook Pixel when Google stopped supporting it: I removed the write-protect screw from the motherboard, flashed a normal BIOS, and installed Linux Mint on it.
Google is finally killing off Chrome apps, which nobody really used
231–240 of 275 posts
Re: Google is finally killing off Chrome apps, which nobody really used
#232Earlier quoted context omitted.
There are some chrome apps that you can't do as a PWA or Chrome extension. For example, there's a local webserver that serves up a folder over http. https://chrome.google.com/webstore/detail/web-server-for-chr...
A local web server is something that can easily be setup on desktop and mobile outside of Chrome.
Re: Google is finally killing off Chrome apps, which nobody really used
#233First of all, this was announced more than 3 years ago, and it still won't happen for another 2.5 years. Second of all, this should be treated as good news for the HN crowd: Google is transitioning from a proprietary, Chrome-only app model to the open-standard, PWA model. Who doesn't support that? There are a bunch of "typical Google cancelling a product" comments here. But for real, I simply cannot imagine any Chrom…
people supporting enterprise. enterprise software is bad to begin with and often has long shelf lives. ActiveX, old java, flash et al are all still flourishing at a large corp near you
Re: Google is finally killing off Chrome apps, which nobody really used
#234Earlier quoted context omitted.
https://developers.chrome.com/apps/migration Everything except advanced File System APIs are supported by PWAs, including Bluetooth through the Web Bluetooth API. [1] The replacement Native File System API is in origin trial and is pre-standardization, however. [2] [1] https://developers.google.com/web/updates/2015/07/interact-w... [2] https://web.dev/native-file-system/
Another big gap is the sockets API. Chrome apps have direct access to TCP and UDP sockets. PWAs can't have this for obvious reasons.
I don't work there anymore but if one of the schools using that app bought Chromebooks without support for Android apps it's going to be a shit show in 2021.
Re: Google is finally killing off Chrome apps, which nobody really used
#235Otherwise... yeah, I can't say that I remember using any of these.
I think I'd rather have all of the Electron apps that I use now share a version of Chrome rather than each package the whole shebang themselves though.
Re: Google is finally killing off Chrome apps, which nobody really used
#236Earlier quoted context omitted.
Costing a many billion dollar multinational corporation $10-20 isn't sending a message at all. It's just a waste of your time.
Not if you expand the $10 into a class action. That however is a lot of work.
Re: Google is finally killing off Chrome apps, which nobody really used
#237I feel like chrome apps were actually ahead of their time and very much better than embedding a full browser per app with electron. Of course, they were not perfect but IHMO made much more sense than what we have today, at least on a technical standpoint and could have evolved into something truly great.
Re: Google is finally killing off Chrome apps, which nobody really used
#238First of all, this was announced more than 3 years ago, and it still won't happen for another 2.5 years. Second of all, this should be treated as good news for the HN crowd: Google is transitioning from a proprietary, Chrome-only app model to the open-standard, PWA model. Who doesn't support that? There are a bunch of "typical Google cancelling a product" comments here. But for real, I simply cannot imagine any Chrom…
Actually is bad news. PWAs are pretty useless and when I say useless I mean no better than a website. All the web restrictions(i.e cors) apply to PWAs. It's just a "webpage shortcut". The alternative to Chrome apps are really Electron apps not PWAs.
Re: Google is finally killing off Chrome apps, which nobody really used
#239Note that Chrome Apps != Progressive Web Apps, which you can still install on desktop Chrome and the new Edge and hopefully will gain more traction.
I just wish apple would finally support push notifications for PWAs: https://caniuse.com/#search=push%20api A lot of use-cases like e.g. chat apps, depend on that kind of technology.
Re: Google is finally killing off Chrome apps, which nobody really used
#240Earlier quoted context omitted.
> Google routinely floats out APIs, services, and platforms and encourages their use despite fatal flaws that mean they are doomed from day one. For most use cases, there are better options now than Chrome apps. ServiceWorkers didn't exist when Chrome apps were introduced. Neither did wasm, and its precursors NaCl and PNaCl were scoped to just Chrome apps, not to the public web. Chrome did a very good job at a) build…
Is there any way to bypass CORS in a PWA? Because Chrome Apps were a really handy way of writing GUI utilities without having to go full Electron.