[brailleblaster] Re: Why Java

  • From: Alex Jurgensen <asquared21@xxxxxxxxx>
  • To: brailleblaster@xxxxxxxxxxxxx
  • Date: Thu, 4 Nov 2010 19:48:02 -0700

Hi,

Take for instance the non-Intell Linx machines and the iPad.

See my last message about memory requirements, as these have a greater impact 
on battery performance of smaller systems.

Regards,
Alex,


On 2010-11-04, at 6:10 PM, qubit wrote:

> What devices? smart phones?  I think whatever device that supports a screen 
> reader that is capable of handling the interface of brailleblaster (which 
> I'll call bb) should be supported.
> --le
>  
> ----- Original Message -----
> From: Alex Jurgensen
> To: brailleblaster@xxxxxxxxxxxxx
> Sent: Thursday, November 04, 2010 6:46 PM
> Subject: [brailleblaster] Re: Why Java
> 
> Hi,
> 
> Thank you for the quick response.
> 
> Don't these libraries have C equivalents? The C equivalents may not be as 
> advanced as their Java counterparts, but I am sure that this is a better 
> long-term goal.
> 
> This still does not address the issues of devices that do not support Java.
> 
> Regards,
> Alex,
> 
> 
> On 2010-11-04, at 3:45 PM, qubit wrote:
> 
>> Perhaps because there are java libraries available that are tempting to use 
>> as a base?  As for Apple and Microsoft, the java runtime is not being 
>> supported by them any longer, but third parties may still develop such 
>> support to be distributed with java programs.
>> Any other things I have missed?
>> --le
>>  
>>  
>> ----- Original Message -----
>> From: Alex Jurgensen
>> To: Brailleblaster@xxxxxxxxxxxxx
>> Sent: Thursday, November 04, 2010 2:25 PM
>> Subject: [brailleblaster] Why Java
>> 
>> Hi All,
>> 
>> I mention this now, at the relative beginning of the project, so as to avoid 
>> unnecessary work.
>> 
>> Why are we using Java and not writing most of the code in C, with a true, 
>> native UI on top, such as WX-Widgets for C. Because the code would not need 
>> to be exicuted in a virtual machine, we would avoid many of the slowdowns 
>> associated with Java.
>> 
>> We must also think about embeded devices, where the overhead of Java is 
>> either too much for hte battery to tolleratte acceptably or there is no Java 
>> Virtual Machine available.
>> 
>> Furthermore, both Microsoft and Apple have dropped support for Java within 
>> their Operating Systems, it doesn't seem to make sense to continue coding in 
>> Java because we may one day soon need to rewrite all of our code to aadapt 
>> to a whole new class of machines that don't have Java Available.
>> 
>> I feel that if we write the core of our code into C libraries, we should be 
>> able to bring about new UI's, such as a Cocoatouch UI for IOS devices, OR an 
>> QT UI for Nokea and Intel's new project.
>> 
>> Just my two cents.
>> 
>> Regards,
>> Alex,
>> 
>> 
>> Alex Jurgensen,
>> VoiceOver Trainer,
>> ASquared21@xxxxxxxxxxxxxxxxx 
>> 
>> Visit us on the web at: www.vipbc.org
>> 
>> 
> 
> Alex Jurgensen,
> VoiceOver Trainer,
> ASquared21@xxxxxxxxxxxxxxxxx 
> 
> Visit us on the web at: www.vipbc.org
> 
> 

Alex Jurgensen,
VoiceOver Trainer,
ASquared21@xxxxxxxxxxxxxxxxx                    

Visit us on the web at: www.vipbc.org

Other related posts: