41–50 of 100 posts
This is a beautiful experiment. To OP: i wonder, how did you find this bug?
I found it because someone posted about it in a school Facebook group I am in.
Creative. Nice project.
http://github.com/%%30%30 pasting this in slack also crashes Slack.
Earlier quoted context omitted.
"They just launch 'as if' they were native." That's a pretty big benefit to most end-users.
I don't know why you're getting downvoted. I've seen studies that say 80% of users prefer apps over the mobile web. I know I've certainly seen an almost hostile attitude towards web app offerings over native app versions. And it all seems to boil down to one thing. You can get good-enough access to just about everything on the phone through an HTML5 app--certainly enough for a large proportion of apps--except for "in…
Earlier 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.
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 toolsets. The shell is really pretty barebones compared to the rich semantics provided by many toolkits and object systems on which user interfaces have been built: GObject and NeXT are two modern examples.
[That said, where shell shines is by providing so few abstractions that virtually any garbage has the same semantic depth as things which were designed to be used in the shell. Bytes are universal on the common computing substrate.]
The web, on the other hand, is a platform "designed" by the erosive flow of eyeballs during the 1st-nth browser wars, without much of a direction beyond tacking on additional pretty features without breaking backwards compatibility too much.
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. Look at how screen readers break on js-heavy and dynamic web pages, the ongoing security disasters of XSS and iframes (and the complexity of login services like Facebook's/oauth/openid), the disappearance of Google reader, and the half-assed way CDNs offer partial, ad-hoc offloading of some resources via surrender to centralization.
Earlier 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.
http://github.com/%%30%30 pasting this in slack also crashes Slack.
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.