News for hackers. Stuff that matters.
Re:Why we maintain desktop apps for OS X, Windows, and a web... by vbezhenar on Thursday July 09, 2015 @09:35PM (#9861852)
What I don't like is WebView distributed as a "native app". It's not native app and it's not something I want to install, don't cheat me. Webpages should stay in browser.

I expect native app to be written with Objective C (OS X/iOS user here), having very low memory usage, fast startup and offline usage. Also I expect as much integration with the system, as possible, native controls (not that buggy emulation without my favorite emacs-like keybindings) and native behavior.

Probably we miss an important piece of technology: installable web-apps. Website opened in the frameless browser window, identifiable as a different application which could be easily pinned to Launchpad. With all advantages that "separate webview" has, but with some important difference: sandboxing. So I can feel safe when I launch this application, because I don't need to trust all my files, passwords and system to another application. I've seen that kind of technology in the iOS: website bookmark could be pinned as a desktop icon, but it's just a bookmark.

Re:Why we maintain desktop apps for OS X, Windows, and a web... by Tiksi on Friday July 10, 2015 @12:30AM (#9862302)
You can launch chrome with

  google-chrome --app="http://app.com"
And get a frameless window.

Firefox used to have something like this, but it doesn't appear to work anymore. You can do

  firefox -chrome "file:///some/local/file.html" 
But obviously that's not quite the same, and I believe is limited to local files.
Re:Why we maintain desktop apps for OS X, Windows, and a web... by zippergz on Thursday July 09, 2015 @10:26PM (#9861983)
This is what I hate about Slack. It feels like a webapp inside of a very thin wrapper.
Re:Why we maintain desktop apps for OS X, Windows, and a web... by stephenr on Thursday July 09, 2015 @11:12PM (#9862097)
This type of app really bites us (users) in the ass when we try things real Mac apps have done literally for decades - drag and drop. Drag a file expecting it to be accepted as an upload, but oh wait no, the web view navigated to view that file. And I have no back button so I have to quit the app.
Re:Why we maintain desktop apps for OS X, Windows, and a web... by totallynotcool on Thursday July 09, 2015 @11:46PM (#9862194)
That's an issue as most webviews can ad a bit of js and support that feature. I'd email the dev a bug report.
Re:Why we maintain desktop apps for OS X, Windows, and a web... by wingerlang on Friday July 10, 2015 @01:40AM (#9862459)
CMD + arrow left works
Re:Why we maintain desktop apps for OS X, Windows, and a web... by baddox on Friday July 10, 2015 @03:04AM (#9862658)
That's one of a large set of things I hate about Slack.
Re:Why we maintain desktop apps for OS X, Windows, and a web... by grimgrin on Thursday July 09, 2015 @10:35PM (#9862014)
Slack feels like it should be in the browser for me, as a pinned tab. So at my job that's how I use it.
Re:Why we maintain desktop apps for OS X, Windows, and a web... by hobarrera on Thursday July 09, 2015 @11:36PM (#9862168)
The problem with these tabs is that closing that window, the tab is gone forever (on both chromium and firefox).

It's also easy to lose track of which window they were in quite fast. A separate app is faster to find on almost any WM/OS.

Re:Why we maintain desktop apps for OS X, Windows, and a web... by pbh101 on Thursday July 09, 2015 @11:48PM (#9862200)
Maybe I miss your meaning but on OS X/chrome: cmd-shift-T to reopen the last window with all tabs. Works even after a chrome restart. Saves me when 40 tabs open and I Cmd-Q for too long instead of Cmd-W.
Re:Why we maintain desktop apps for OS X, Windows, and a web... by hobarrera on Saturday July 11, 2015 @12:03AM (#9868480)
Yes, I'm aware of this, but it pretty much means the pinned tab behaves like "any other tab". If I closed those 40 tabs, the pinned tab should move elsewhere or persist. Otherwise, I'll have to manually re-pin it all the time.
Re:Why we maintain desktop apps for OS X, Windows, and a web... by ex3ndr on Friday July 10, 2015 @08:11AM (#9863427)
This is not problem of slack in webview. This is problem of slack. Actually interface in OSX is slower that web view. If you compare optimized Web app and OSX Native app, you will spot difference. Slack is just not optimized.

You can to check our own messaging to it's speed at our old hacker news thread: https://news.ycombinator.com/item?id=9757243 It is faster than native apps.

Re:Why we maintain desktop apps for OS X, Windows, and a web... by Cthulhu_ on Friday July 10, 2015 @10:14AM (#9864048)
I have to say though, for a webapp packaged in a wrapper it's a very good one.
Re:Why we maintain desktop apps for OS X, Windows, and a web... by 1123581321 on Thursday July 09, 2015 @11:07PM (#9862081)
The recent update is the first one that starts to feel like software to me because the download interface is much less "webby" (and faster for grabbing multiple files from someone.)
Re:Why we maintain desktop apps for OS X, Windows, and a web... by tracker1 on Friday July 10, 2015 @04:32AM (#9862858)
In chrome I can create application shortcuts... and with browser notifications it pretty much just works. I usually have pandora and slack as application shortcuts that run in their own windows... it really doesn't bug me that they run in a browser... they work as I expect them to (though not in osx iirc). I agree that the thin wrappers are a little annoying...

On the flip side, though I really appreciate that I can create more feature rich applications with the likes of nwjs or electron. There's a lot of things you can do that go a fair bit beyond just web applications in a thin shell... though most of the better ones are app centric first, and web instance second.

I do wish someone would build a nice mail client for Chrome/ChromeOS though... That part really sucks imho. I mean there's a browser based SSH client for chrome, so it's entirely possible to do.

Re:Why we maintain desktop apps for OS X, Windows, and a web... by tdkl on Friday July 10, 2015 @06:28AM (#9863144)
If user X uses Chrome. If not, there's extra 1GB+ bloat for one "browser app". No thanks.
Re:Why we maintain desktop apps for OS X, Windows, and a web... by tracker1 on Friday July 10, 2015 @07:54AM (#9863374)
So, you don't use any browser apps?

That must be pretty hard to do. I think going without a browser+javascript would be pretty primative... I mean, I pay my bills, send emails, hell view the site I'm on as browser applications. I remember being online in 1993 (vga, bbsing, dialup ftw), it wasn't nearly as diverse or capable as today.

Re:Why we maintain desktop apps for OS X, Windows, and a web... by Tiksi on Friday July 10, 2015 @08:06AM (#9863409)
> So, you don't use any browser apps?

That's not at all what they said. Some of us use browsers that are not chrome. That would mean having to run 2 browser runtimes to get a thin wrapper with chrome.

Re:Why we maintain desktop apps for OS X, Windows, and a web... by tracker1 on Friday July 10, 2015 @09:25AM (#9863776)
I believe Firefox has, or used to have the ability to launch a standalone browser without extra chrome for a specific site (maybe not via the UI)... IIRC IE on Windows 7+ offers the same functionality.

If you're using Opera or Safari, I have no idea.

Re:Why we maintain desktop apps for OS X, Windows, and a web... by jfb on Thursday July 09, 2015 @10:33PM (#9862009)
I use the Fluid SSB [1] for the latter. It sandboxes websites that I need to use but are not willing to allow access to my primary browser history/cookie store. It's a little clunky, but it gets the job mostly done.

[1] http://fluidapp.com

Re:Why we maintain desktop apps for OS X, Windows, and a web... by mosburger on Friday July 10, 2015 @11:24AM (#9864446)
I love fluid because of the thing the article mentions about Alt/Cmd + Tab... it's hard-wired into my brain to mean "task switch", so I have several web apps that I use all the time (GCal, Pivotal Tracker, Asana to name a few) with Fluid apps so I can quickly change to them.
Re:Why we maintain desktop apps for OS X, Windows, and a web... by jfb on Friday July 10, 2015 @05:34PM (#9866863)
Yeah, that too. Not having to hunt around for a browser tab is really nice.
Re:Why we maintain desktop apps for OS X, Windows, and a web... by vinkelhake on Thursday July 09, 2015 @09:44PM (#9861866)
Like "Create application shortcuts" in Chrome?
Re:Why we maintain desktop apps for OS X, Windows, and a web... by TD-Linux on Thursday July 09, 2015 @09:54PM (#9861897)
Or app manifests in Firefox?
Re:Why we maintain desktop apps for OS X, Windows, and a web... by jbigelow76 on Friday July 10, 2015 @11:42AM (#9864569)
Windows 10 will allow for installable web apps that behave like native (admittedly not much use to an audience that tends heavily toward OS X)
Re:Why we maintain desktop apps for OS X, Windows, and a web... by EGreg on Friday July 10, 2015 @11:23AM (#9864438)
vbehezar what if only the view layer was in HTML/CSS/JS?

How is that different from using gtk or some other gui toolkit?

Re:Why we maintain desktop apps for OS X, Windows, and a web... by dcdevito on Thursday July 09, 2015 @10:34PM (#9862011)
Chrome packaged apps do what your last paragraph is calling for
Re:Why we maintain desktop apps for OS X, Windows, and a web... by vbezhenar on Friday July 10, 2015 @09:52AM (#9863924)
Thanks, that's an interesting technology. Too bad that it's specific to Chrome and I can't expect any user to run Chrome or install Chrome. But that's a good direction, I only hope that major browser vendors will consider to adapt it or similar standard in the future. It shouldn't take too much resources to implement it, I suppose.