I second this. Having worked with other J2ME devices, and then with BlackBerry smartphones, the latter is a dream by comparison. I would have to say that sticking with the MIDP & CLDC ways of doing things can be quite limiting. But like you mentioned, with the $100 key, you can do quite a lot beyond the usual J2ME set of limitations. Of course, as always, the more recent the BlackBerry OS version you develop for, the happier the developer you are. The only thing I do have to admit that I miss slightly is that the UI apis for BlackBerry phones are not thread safe as they are in the MIDP apis, but there are plenty of reasonable ways to handle this in code.
Don't be so quick to discount the NSLU2. I've got one on my desk here. I'm glad I replaced the old PC with this little device.
First it meets the usual set of goodness:
- No fans
- Can be put anywhere due to its (relatively) tiny size
- Quiet
- Much lower power usage
The 32MB of RAM sounds like a limitation at first, but I'd have to say its doing just fine. I'm running the device off of a USB flash stick, and have Apache2 (with PHP5), the default Samba install, and an FTP server. As soon as I get a bigger USB flash stick, I'll be able to install more. I'm trying to decide what to use the second USB port for; Bluetooth connectivity for my phone, or a second network connection for an enhanced firewall setup. Actually, the Asterisk HOWTO sounds interesting right now...
From TFA: This software is still in testing phase and is available from our Download Section free of charge and "as-is". Expiration date November 1st, 2005.
Any idea how easy it'd be to do an OSS version of this?
I agree. I've been doing programming w/ ESRI software in some way or another for 6 years now, and if its taught me anything, its that ESRI surrounds itself with a barrier: No input from the community, no source going out, and definately no help with (let alone acknowledgement of) any bugs/issues with their software. They're a heavily proprietary sw company w/ a tendancy to ignore standards they didn't create (think a GIS equivalent of MS). Don't expect anything back from them. I'm done venting now.:)
HTML is fine for displaying content, however the problem seems to lie in that Web content is much more now than HTML. The Internet is now used in ways not imagined during its early years, and the Web browser situation is similar.
I agree with posts saying plugins are bad. However, if its done in an open standards sort of way, I don't think we should have to hold ourselves back. The web has an opportunity to become a pseudo-desktop. At some point we have to cut the dead weight.
For those visually impaired, XML to voice translation has got to be more accurate than badly written HTML to voice.
If we as web developers plan, we should be able to move forward, eliminate bad HTML, browsers, etc, and still accomodate all those in a better way than we are today.
Slashdot Mirror
I second this. Having worked with other J2ME devices, and then with BlackBerry smartphones, the latter is a dream by comparison.
I would have to say that sticking with the MIDP & CLDC ways of doing things can be quite limiting.
But like you mentioned, with the $100 key, you can do quite a lot beyond the usual J2ME set of limitations.
Of course, as always, the more recent the BlackBerry OS version you develop for, the happier the developer you are.
The only thing I do have to admit that I miss slightly is that the UI apis for BlackBerry phones are not thread safe
as they are in the MIDP apis, but there are plenty of reasonable ways to handle this in code.
Don't be so quick to discount the NSLU2. I've got one on my desk here.
P age/
I'm glad I replaced the old PC with this little device.
First it meets the usual set of goodness:
- No fans
- Can be put anywhere due to its (relatively) tiny size
- Quiet
- Much lower power usage
The 32MB of RAM sounds like a limitation at first, but I'd have to say its doing just fine.
I'm running the device off of a USB flash stick, and have Apache2 (with PHP5), the default Samba install, and an FTP server.
As soon as I get a bigger USB flash stick, I'll be able to install more.
I'm trying to decide what to use the second USB port for; Bluetooth connectivity for my phone, or a second network connection for an enhanced firewall setup.
Actually, the Asterisk HOWTO sounds interesting right now...
For a list of ideas of what you can do with the NSLU2:
http://www.nslu2-linux.org/wiki/Applications/Home
http://www.nslu2-linux.org/wiki/HowTo/HomePage/
From TFA:
This software is still in testing phase and is available from our Download Section free of charge and "as-is". Expiration date November 1st, 2005.
Any idea how easy it'd be to do an OSS version of this?
The first thing I thought of when I read the title was keyword bookmarklets:t ml
http://www.squarefree.com/bookmarklets/keywords.h
One of those things that seems could be made more useful with some "Ajax" here and there.
Actually, I believe the BES supports Lotus Notes and a Novell email system as well.
Of course, none of these are absolutely necessary. I'm happily using my Blackberry over pop3 running on my Linux machine.
I agree. I've been doing programming w/ ESRI software in some way or another for 6 years now, and if its taught me anything, its that ESRI surrounds itself with a barrier: No input from the community, no source going out, and definately no help with (let alone acknowledgement of) any bugs/issues with their software. They're a heavily proprietary sw company w/ a tendancy to ignore standards they didn't create (think a GIS equivalent of MS). Don't expect anything back from them. :)
I'm done venting now.
Hm.... your security? Heh... Maybe you should submit it as an Ask Slashdot??
HTML is fine for displaying content, however the problem seems to lie in that Web content is much more now than HTML. The Internet is now used in ways not imagined during its early years, and the Web browser situation is similar.
I agree with posts saying plugins are bad. However, if its done in an open standards sort of way, I don't think we should have to hold ourselves back. The web has an opportunity to become a pseudo-desktop. At some point we have to cut the dead weight.
For those visually impaired, XML to voice translation has got to be more accurate than badly written HTML to voice.
If we as web developers plan, we should be able to move forward, eliminate bad HTML, browsers, etc, and still accomodate all those in a better way than we are today.