6 ms·
"Objective-J and SproutCore change all that. They allow you to create true desktop-like apps right inside the browser. " Why would I not prefer a true desktop
by jamesbritt 18y ago
"Objective-J and SproutCore change all that. They allow you to create true desktop-like apps right inside the browser. "
Why would I not prefer a true desktop app right on my desktop?
Using Java and JNLP I can get an app the can be auto-updated (as a Web app would be) but takes advantage of an arguably more robust and speedier language (Java, perhaps by way of JRuby or Scala or Jython) with true desktop features.
It seems that the "Build Apps in a Browser with JavaScript" pitch is mainly a win for Web developers who only know JavaScript. It isn't clear what the benefits are to the end user.
- llimllib 18y ago> what the benefits are to the end user. A UI that doesn't suck eggs comes to mind. I use strong language to get a point across; Java UIs today feel to me like Motif UIs did in 2000.
- michaelneale 18y agothey can suck. The best example of one that doesn't suck (for me) is the facebook image uploader.
- orib 18y agoThe problem is that even though Java GUIs tend to suck, web app guis suck more. I'm probably going to get a fair bit of hate from this, but seriously, web apps are a pain. - they have the browser's baggage. Address bar, back/forward buttons, etc - They don't use native widgets... except for some places (form widgets) - They're slow - They can't integrate with other desktop apps (drag and drop, saving to local disk, heck, even loading from local disk sucks) While web-app style development is going to get better, I somehow hope we could get to the "write your UI in a GUI description language, develop your logic separately, talking to a network server" stage without being stuck with compatibility baggage resulting from needing to be compatible with the browser. To be clear on what I mean -- Yes, currently developing and deploying desktop apps isn't fun. Who wants to write reams upon reams of code to pack widgets into containers, or whatever layout-method-du-jour your toolkit is using, when you can simply type some XML to describe your UI? Who wants to use a slow installer after a slow download to get an app installed? Web apps win here. However, web apps -- by design -- are unable to integrate properly into a desktop. They're trapped in a browser, cut off from interaction with the rest of your UI, and if they weren't, it would be an insanely bad design decision. On the flip side, with things like Glade, designing a desktop GUI is starting to hurt far far less. I think that pushing desktop app development frameworks towards being far more network aware, easily deployable, and faster to develop will lead to far, far better results than trying to make web apps not suck, while dragging the web browser legacy junk onto desktoplike web apps. [edit - expand on ideas]
- hello_moto 18y agoDeclarative UI idea is here: http://code.google.com/p/google-web-toolkit-incubator/wiki/DeclarativeUi http://code.google.com/p/google-web-toolkit-incubator/wiki/D... Whether you like GWT or not (cause it uses Java) is another discussion.
- llimllib 18y agoSo! I agree with you about your limitations, and agree that they suck. Where we disagree is on the valuation of those limitations. The benefits of web apps in consistency of interface elements, interoperability (hyperlinks!), customizability (greasemonkey!), toolset (FF, IE, Opera, Safari, Lynx, Emacs, mostly use whichever floats your boat), and portability (use the same app at work as you use at home) far outweigh the drawbacks. Which is not to say that we should not attack those drawbacks, we should, but we should do it in a way that we maintain the benefits we've gotten from web applications.
- warwick 18y agoI was thinking a lot like this, but recently I've changed my opinion. Just to contradict your 'only web devs like it', I'll mention that most of my work is done in Obj-C and Cocoa. Web apps have some inherent advantages. Being 'installed' by clicking on a link, which lowers the barrier to a user trying your app. Having data available everywhere. Autoupdating that doesn't involve a download and relaunch. Traditionally I've been opposed to putting full apps on the web. I didn't think I could deliver as good of an interface with it, but seeing SC and 280North changed my mind. I should mention that though I'm looking at porting one of my desktop products, I'm intending to maintain the desktop app and the port in parallel and give customers a choice if they want to download the desktop app.
- jamesbritt 18y ago"Web apps have some inherent advantages. Being 'installed' by clicking on a link, which lowers the barrier to a user trying your app. Having data available everywhere. Autoupdating that doesn't involve a download and relaunch." Java Web Start gives you the first, and common networking libs give you the second. For the third, something ina desktop app would need downloading and a restart, though, on the other hand, using a Web app means downloading something on almost every use; a desktop app is always there, so off-line use is likely more robust.