[deleted]
Show HN: %%30%30: A Game
51–60 of 100 posts
Re: Show HN: %%30%30: A Game
#52Earlier quoted context omitted.
Yeah, I strenuously object to the fad of calling wrapped web pages 'native apps'. They get zero benefits that would normally accrue to real native apps. They just launch 'as if' they were native.
"They just launch 'as if' they were native." That's a pretty big benefit to most end-users.
That could be the greatest thing in the world, but it doesn't make it a native app.
Re: Show HN: %%30%30: A Game
#53This works in Chrome on Android as well. Of course it's way easier than on desktop.
Not for me: https://i.imgur.com/bzScUUn.png
Re: Show HN: %%30%30: A Game
#54Earlier quoted context omitted.
Yeah, I strenuously object to the fad of calling wrapped web pages 'native apps'. They get zero benefits that would normally accrue to real native apps. They just launch 'as if' they were native.
Thank you. People calling web-render wrappers "native applications" must not realize how great it is when applications are mere coördinators on top of an integrated platform full of services designed to improve user productivity. I guess if that demographic did, there would be less "unix philosophy" cultism, as the efficacy of the unix shell is merely on par with that provided by other relatively coherent software to…
> Attributes like a11y, embeddability, composability, and effective resource sharing tend to simply fall out of well-designed platforms. The web has an effective answer for none of these desirable concerns.
...what? The web is better than most native platforms in these.
The web is accessible. It has many features for screen readers and such, but more importantly, it is inherently flexible and allows content's form to be adapted to the reader's needs, thanks to the separation of content from style. A single web page, unmodified, can work on a desktop PC with a mouse and keyboard, a capacitive touch device the size of your palm, a stylus-input device the size of a laptop, a printed page, a screen reader, a ten key mobile phone from yesteryear, and more. The web lets users define custom styling that meets their needs, lets users selectively remove content (ads, for example), etc. No native platform is that flexible. Yes, some sites break screen readers, but this is true of native apps as well.
The web is incredibly embeddable. Any web page can, with one line of code, incorporate any other web page, and it "just works". You simply can't do that with native apps.
The web is composable as well. Sites can load JavaScript from each other very easily.
The web also supports resource sharing in various forms, but people don't necessarily use them.
Re: Show HN: %%30%30: A Game
#55Re: Show HN: %%30%30: A Game
#56My inspector even crashes when trying to hover over the link node!
Re: Show HN: %%30%30: A Game
#57Earlier quoted context omitted.
Explanation for why this is occurring: Slack's desktop apps are HTML5 webapps wrapped inside native desktop wrappers. Specifically, Slack uses Github's Electron (formerly, Atom Shell) which is basically Chromium. The desktop app is a webpage inside Chromium.
Yeah, I strenuously object to the fad of calling wrapped web pages 'native apps'. They get zero benefits that would normally accrue to real native apps. They just launch 'as if' they were native.
Don't think I've ever heard or read anyone claim this, just that they live in a native wrapper.
Re: Show HN: %%30%30: A Game
#58Earlier quoted context omitted.
Explanation for why this is occurring: Slack's desktop apps are HTML5 webapps wrapped inside native desktop wrappers. Specifically, Slack uses Github's Electron (formerly, Atom Shell) which is basically Chromium. The desktop app is a webpage inside Chromium.
It's Chromium? Then why do the Slack folks keep saying the preferences UI bug is a Webkit bug? It can't be a Webkit bug if they're using Chromium.
Depends on the platform. For Apple devices and workstations it's a wrapped Safari web view, which is not affected by the bug, and does not crash.
Re: Show HN: %%30%30: A Game
#59Earlier quoted context omitted.
Yeah, I strenuously object to the fad of calling wrapped web pages 'native apps'. They get zero benefits that would normally accrue to real native apps. They just launch 'as if' they were native.
Thank you. People calling web-render wrappers "native applications" must not realize how great it is when applications are mere coördinators on top of an integrated platform full of services designed to improve user productivity. I guess if that demographic did, there would be less "unix philosophy" cultism, as the efficacy of the unix shell is merely on par with that provided by other relatively coherent software to…
I agree that these are all legitimate problems, but over time the wrappers themselves will eliminate a lot of them. There will always be "native" wrapped HTML apps that do a bad job of taking advantage of the platform. That's the case with any adapter platform that lets you code once and deploy everywhere (look at 90% of Java-based apps). But that doesn't mean that it will inherently be a bad idea.
Indeed, Electron already is starting to provide these kinds of facilities. For example, it allows you to load native node modules, and it provides some tools for integrating with the desktop envirionment (see https://github.com/atom/electron/blob/master/docs/tutorial/d...).
Side note:
> coördinators
I knew I wasn't the only one who loves this pretentious diaresis style. Stay strong, brother/sister/sibling. Stay strong.
Re: Show HN: %%30%30: A Game
#60You know you've been working with ASCII for a long time when you can automatically unescape the title... and then pause, considering whether to unescape again. I think reading the comments on that bug is also rather enlightening; points of note include a 62-level-deep stack trace, comments to the effect of "we don't know what the bug is/how this is supposed to work", and discussions about whether escaping multiple ti…
It's surprising that this issue was brought up multiple times as a bug, but wasn't taken seriously until it got special attention. This bug is definitely notorious, I wonder setting a similar URL as the homepage of Chrome will cause Chrome to continuously crash and make it useless.