Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Chrome Apps are dead, as Google shuts down the Chrome Web Store section

arstechnica.com

Post reply on HN
Print view View original

111–120 of 144 posts

Re: Chrome Apps are dead, as Google shuts down the Chrome Web Store section

#111

Post by MBCook »

TheAdamAndChe wrote: post #110
MBCook wrote: post #104

Earlier quoted context omitted.

Why is it different? What makes YouTube different from TV or radio or newspapers? Someone always says ‘but the internet is different’ but I’ve never seen a good explanation for why. Just things along the lines of ‘that’s how it’s been’ or ‘TV and radio are wrong’. How is paying money to support something not an endorsement?

> What makes YouTube different from TV or radio or newspapers? This is a good question. TV, radio, and newspapers all need to cater to the lowest common denominator(LCD) in order to obtain the greatest amount of viewership as possible, because distribution is expensive. A focus on the LCD combined with data analytics is why channels like The Learning Channel(TLC) and History Channel only show reality TV nowadays: The…

That explains why channels like Ben Heck and Techmoan and GameSack have enough of a market to make a lot of content. The long tail works much better than mass media, which is one of the reasons so many of us love YT.

I don’t see why that means advertisers aren’t, in some way, endorsing the content. If anything the fact there are so many channels and the content is more specific seems like a stronger endorsement than mass media.

Re: Chrome Apps are dead, as Google shuts down the Chrome Web Store section

#113

Post by ensignavenger »

smt88 wrote: post #51
PuffinBlue wrote: post #31

Earlier quoted context omitted.

What is 2FA? It's 'something you have'. It's not 'one single thing on one device only'. It's just 'something you have'. 'Something you have' relies on physical security, so if you have the same physical security for both your laptop and phone, there's no reduction by having a 2FA token on each device.

That's only true if there's a physical barrier to propagating your tokens to new devices. The concern is that Authy changes the second factor from physical security back to something cloud-based and hackable. I don't know if that's legit because I don't know how Authy works.

From reading the Authy docs, it sounds like all your Authy data is encrypted before leaving the device, so if the encryption works, it should be pretty secure. You can also turn off the multi-device support and backup, if you don't want those features. But tome, the risk of losing my single device and being locked out of my accounts is too high without it. I just wish Authy was open source so it could get more security review.

Re: Chrome Apps are dead, as Google shuts down the Chrome Web Store section

#114

Post by 5ilv3r »

dragonwriter wrote: post #102
oneweekwonder wrote: post #85

Earlier quoted context omitted.

> who needs the low level functionality will end up with a native app All please note. Electron is not a native app. It is a horrible hack that everybody use because it is easy. Hybrid apps will always suck! ~ <3 hobbyist hybrid gamedev with client side js crypto mining on his mind }:‑)

> All please note. Electron is not a native app. Electron is an extremely heavyweight native app frsmework, not a native app, but Electron apps are (bloated, sure) native apps.

Native means it uses the os rendering engine and widgets. Electron is not that. I don't know when web devs decided they could put a website in a box and call it native, but it's not very nice.

Re: Chrome Apps are dead, as Google shuts down the Chrome Web Store section

#115

Post by 5ilv3r »

ctrl-j wrote: post #84
owebmaster wrote: post #36

Earlier quoted context omitted.

> Now we're probably going to turn to Facebook and try to get some traction there.. And that is why the web is dying.

You have an alternative to offer? Facebook is where the users are. What is your non-facebook approach to get visibility from new users?

Local seems to be the next frontier. As in, a storefront. What's old is new again (again)!

Re: Chrome Apps are dead, as Google shuts down the Chrome Web Store section

#116

Post by pjmlp »

carussell wrote: post #73
icebraining wrote: post #45

Earlier quoted context omitted.

Technically, you can have all those advantages with Qt/QML, since it uses JavaScript and runs on desktop, mobile and even web. That said, I never used it. Another alternative would be React-Native, now that react-native-web exists...

> Technically, you can have all those advantages with Qt/QML GTK+, too. There was a big uproar several years ago when GNOME tried to anoint JS as the "official" language for GNOME app development. They eventually backpedaled, and overall their story for JS today seems to be technically decent but thoroughly undocumented. Keep in mind, this was all before GitHub announced Atom and (what was not-yet-then called) Electr…

JavaScript is one of the official GNOME languages.

https://wiki.gnome.org/Projects/Gjs

https://2017.guadec.org/talks-and-events/index.html#abstract...

Electron apps across GNU/Linux users are the final nail of the desktop Linux aspirations.

When the world is a Web VM, the kernel and everything UNIX related is irrelevant.

Re: Chrome Apps are dead, as Google shuts down the Chrome Web Store section

#118

Post by pgrote »

bane wrote: post #59

What's the future for Chrome Remote Desktop?

They are deprecating the app and going to a web application.

There is also a companion extension, but I am unsure what purpose it serves.

https://productforums.google.com/forum/#!topic/chrome/uVCvle...

https://remotedesktop.google.com/

Re: Chrome Apps are dead, as Google shuts down the Chrome Web Store section

#119

Post by mephitix »

Klathmon wrote: post #109
JepZ wrote: post #96

Earlier quoted context omitted.

Wow, thats a bummer. Didn't know about that. Anybody knows why Apple is doing that?

I've heard a few different things. The cynical part of me wants to think that it's because by hurting it in WebViews and in a desktop-shortcut they can "support" these technologies without fear of them cutting into their app store sales/numbers. But I have heard that there are some shitty technical problems with it. Safari is not the same as a WebView when it comes to the code, and apparently a desktop-shortcut app r…

This is news to me. I thought WkWebview used the same internals as mobile safari. So it's just the JS engine/Nitro that's the same?

Re: Chrome Apps are dead, as Google shuts down the Chrome Web Store section

#120

Post by Klathmon »

mephitix wrote: post #119
Klathmon wrote: post #109

Earlier quoted context omitted.

I've heard a few different things. The cynical part of me wants to think that it's because by hurting it in WebViews and in a desktop-shortcut they can "support" these technologies without fear of them cutting into their app store sales/numbers. But I have heard that there are some shitty technical problems with it. Safari is not the same as a WebView when it comes to the code, and apparently a desktop-shortcut app r…

This is news to me. I thought WkWebview used the same internals as mobile safari. So it's just the JS engine/Nitro that's the same?

I'm not even sure what is the same and what is different, and there isn't anywhere that I found that explains it easily (if it can even be explained easily).

I think the difference might just be in the rendering engine. So Safari uses "safari", and WkWebView uses straight WebKit? But even that isn't true since there are things that WkWebViews support that WebKit doesn't...

But there are many differences between them. The WebRTC stuff above as one, but also things like appcache manifest stuff didn't work in WkWebView in iOS 9 (even though it worked in Safari). And that violation was especially egregious because it could be enabled by calling a single private Objective-C method like this

     [_wkWebView.configuration.preferences _setOfflineApplicationCacheIsEnabled:YES];
However apple would then deny your app in the app store if you did that...

So I genuinely don't know what to think.

Oh, and SFSafariViewController won't even save you, as that doesn't support WebRTC either...

Post reply on HN