Part 1 is achievable with Java Web Start. Nobody needs Eclipse or Netbeans.
A third reason, you want your app to run anywhere and it needs features not available to webapps. -----Original Message----- From: Jim McDonnell <[email protected]> Sender: [email protected] Date: Wed, 7 Dec 2011 05:47:26 To: <[email protected]> Reply-To: [email protected] Cc: Jim McDonnell<[email protected]> Subject: Re: [The Java Posse] Re: I need clarity on Episode 371 OK, I'm derailing my own question about "how did Java lie" - something I was going to let others do (and they're doing a great job ;->), I look at internal applications as edge cases. If you are building a mission critical UI app in Java, how often are you concerned about WORA? Maybe my company is weird, but we are mostly standardized on a couple of models of computers running Windows XP or Windows 7 to help make support easy (because that support is outsourced and you can't make things difficult in that case). So for where I work, I can only think of a few reasons to create a mission critical UI app in Java: 1. You need to deploy an app for users to run locally on their computers. However you want to be able to easily update those apps without adding to your operational/support headaches. So you choose a Netbeans or Eclipse like platform (there may be others) that helps you build a UI that also has built in ability to download/apply updates over the network. 2. You just want to do it to experiment with Java UI and follow RDD principles (Resume Driven Development). I can understand the first reason, maybe users aren't connected to the company network (or any network) often, and need something they can run when disconnected, *and* need some functionality that is easier to provide using Java libraries. The second reason is more likely what the real motivation is. Hell, we all want to follow RDD principles! Outside of disconnected users, I would expect reasonable/just-get-it-done-fast people to either target a Microsoft (VB/C#) platform to create the UI (because the tooling just makes it easier than Java), or, more likely, target a web app for the UI. Perhaps for a company that runs on Macs the leaning might be more towards Java. (Is there a VB like tool for Mac? I don't know, the last time I worked on a Mac was nearly 20 years ago, when you could put a fast app together using Hypercard.) -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/TB53_rgiAGAJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
