Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!news.ecp.fr!news.glorb.com!news-spur2.glorb.com!homer.glorb.com!.POSTED!not-for-mail From: Steve Sobol Newsgroups: comp.lang.java.programmer Subject: Re: Android?Why Dalvik? Date: Thu, 2 Jun 2011 20:50:40 -0700 Organization: Glorb Internet Services, http://www.glorb.com Lines: 20 Message-ID: References: NNTP-Posting-Host: xoAFiuXnRqdiUJrjkwExXQ.user.posting2.glorb.com Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 8bit X-Complaints-To: abuse@glorb.com NNTP-Posting-Date: Fri, 3 Jun 2011 03:50:50 +0000 (UTC) User-Agent: MicroPlanet-Gravity/3.0.4 X-Notice: Scanned by Mr. Bill Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:4918 In article , Lawrence D'Oliveiro says... > > Nope. Batch files and shell scripts work just fine, and it's easy enough > > to include one with your app. Or you can create a native executable > > stub. > > Sounds like you?re reinventing the work done by GNU Autoconf, only now it?s > happening on every execution, instead of once at build time. You're right, but if I create an app for someone and give them a file they can execute at the command line, or double-click in the GUI, who the hell cares? You can be as puritannical and as nit-picky as you want, but in the end, as long as the end-user can run the app, it doesn't matter. -- Steve Sobol - Programming/WebDev/IT Support sjsobol@JustThe.net