In the case of web apps, I'd start by asking the vendor what their commitment to using open standards is and what browsers they officially test with and support. A good answer to that question would be that they are committed to using open standards and they support the most widely used browsers. Any answer other than that should set alarm bells ringing.
You can and should do your own testing on top of that. You can even stick to IE if you don't like version numbers incrementing every other week, but the important thing (to me) is not to get locked in to the point you can't jump ship to something else later down the line.
No compatibility with your vendor locked in software maybe, but that's not the case for everyone. When evaluating software my business uses, not being stuck in a vendor locked in solution is a very high priority and I wouldn't want it any other way.
So look, I will give you that eSata would be nice, but you couldn't do it for the same BOM. The connector and controller will drive the price up. So let us give up this fiction/pipedream that you could produce it for the same price. In the future, maybe, but right now? no.
If you read what I said, you'll notice I said I look forward to the time (as in, the future) when SATA and GigaE can be included at that price point. Not now, but in 12 to 18 months when it should be feasible.
But as for Gigabit Ethernet, just how much data do you think you can pump though a single core 1GHz ARM? What are you doing that 100Mbit isn't enough? Or is this just some kind of megapixel war thinking that bigger is better?
There are other devices with similar ARM processors that can handle gigabit. I don't know if the CPU in this Beagle device could do so, but again, in a year or so, a similar priced CPU would hopefully be able to. As for uses, there are many, but if you agree that SATA woud be useful then I'm sure you could understand why people may want faster than 100Mb/s network connectivity to go with it.
I think you would have a hard time proving that GigaE has enough demand to make a difference for the fast majority of [BeagleBone] users.
Yeah, I agree with this and that's why the Beagle / Pi is what it is for now. I've no complaints with that either, but future SoCs with GigaE and SATA will get down to the same price point eventually and no doubt we'll see these devices sporting that functionality in a year or so.
You're misunderstanding what I said. I like the Raspberry Pi and this new Beagle device. Really, they're great, and I can see a gazzillion uses for them where they are just perfect, some of which I plan to use them for myself.
All I am saying with regard to SATA and GigaE is that when the time comes they can be included at that price point, the scope for these devices being used as more serious network / storage devices expands greatly. Yes, I know their intended use does not necessarily include some of the things I'm thinking of and that's just fine, they do what they do very well. I'm simply looking forward to when the natural evolution of these devices includes those extra features at a sub $50 price. That will most likely happen in the next 12 to 18 months.
That may be so but it does not stop it from being a very valid point, especially for a lot of slashdot users. I like my Raspberry Pi and I really like the look of this new Beagle device. If it had SATA and GigaE for around the same price, I'd love it even more.
The inclusion of SATA and GigaE would presumably drive the price up to a point they don't think would let them compete with the Raspberry Pi. That will change though, and I'm very looking forward to that time. As soon as SATA and GigaE can be included at around the same price point, these devices suddenly become a viable basis for a whole wealth of serious storage and network devices. The only reason I don't use the Raspberry Pi for anything more serious than a media server on my network is because of the limitations of its USB throughput for both storage and networking.
YOU host the damned server, and YOU control the encryption keys. ALL traffic to the device is encrypted on YOUR side. RIM cannot see into these and does NOT have access to these keys.
Uhhh, unless I'm mistaken, he didn't say otherwise. He does actually mention that the big boys bought their own BES servers, keeping sensitive emails under their own control.
I think you need to take the time to read a user's comment more carefully before jumping down their throat.
Not just for HTC phones. I'd be tempted to flash CyanogenMod on any supported phone if it's not a Nexus device (and even then there are advantages with CM, especially with older Nexus devices that were deemed not powerful enough for 4.x).
I have one of these £24 / $36 Logitech Bluetooth audio receivers connected to my hi-fi and then send audio to it from my tablet, phone or PC. The weak point of the audio feed is then either the DAC in the Logitech device (seems good to me), the analogue RCA cables (again, fine by me), or the Bluetooth A2DP profile. I'm not sure about the specifics any more, but the Bluetooth A2DP profile is more than adequate for my MP3 collection.
Oh, and I use Google Play to host my ~100GB MP3 collection so it is accessible and streamable from any device.
No terminal!? Nice to know it still has the standard repositories though. I guess once you've logged in remotely (SSH presumably?) you could apt-get install a terminal application for local use?
I had a quick look at a few of the Youtube videos of it that have popped up over last few hours so see what you mean about fake data and static images for applications. Seems there's quite a bit missing at the moment.
Who care's if some people get to make bucket loads of cash off of open source? And for whatever money the likes of Mr Shuttleworth make off it (and good on them, I say), there's a lot of money being poured back into OS projects that we get to enjoy the fruits of for free. We're all profiting from the hard work of developers in some way or other.
So, to all those with compatible hardware and willingness to test out these installs, what do you think so far?
Seeing as these images are packaged for devices that were originally running Android, how does it compare to Android in terms of responsiveness, features, ease of use, intuitiveness, eye candy, etc? Any glitches, glaring ommissions? Any really cool features?
And what's the 'Linux' side of it like? Can you pull up a terminal and do general sys admin type stuff on one of these things? Does it have well populated repositories with packages we've come to take for granted on our desktops and servers?
With that argument, you could say photocopying a book is an abstraction of routing control of atoms, simply controlling where the various atoms that ink is composed of are placed on the paper. I'm not necessarily disagreeing with you, but I don't think that argument would hold up in court.
It's not that hard to do. Current Android / iOS apps adapt on the fly to different screen orientations and can adjust their layout for different size / density devices. It just takes a slightly different approach from the outset, a bit like responsive web design - you change the way you think about the UI constraints and end up with a UI that adapts to practically any size, orientation or pixel density.
A well made Android app is able to adapt it's UI for different size / density screens too, or have completely different UI layouts for different devices. The more popular apps do this very well and it's not hard to design for. Unfortunately a lot of Android developers still design primarily for phones and leave tablet owners with the same layout. It's getting better though.
I'm mainly an Android user and developer but love the way Ubuntu for tablets manages this side by side app stuff. Same with Surface - it's the one feature that I actually like from what I have seen of Surface tablets. I don't think it will be too long before a future Android release enables a similar feature, and when it does, it should be fairly trivial for Android app developers to make use of it because the ground work has already been laid. I'd say it's in a better position to do so than iOS apps in fact, because Android developers already have to cater for an almost limitless variety of screen sizes where as the few variations in iOS devices means many iOS apps have UIs designed for just two or three variants and are not as flexible (black bars on iPhone 5 for example).
Slashdot Mirror
In the case of web apps, I'd start by asking the vendor what their commitment to using open standards is and what browsers they officially test with and support. A good answer to that question would be that they are committed to using open standards and they support the most widely used browsers. Any answer other than that should set alarm bells ringing.
You can and should do your own testing on top of that. You can even stick to IE if you don't like version numbers incrementing every other week, but the important thing (to me) is not to get locked in to the point you can't jump ship to something else later down the line.
No compatibility with your vendor locked in software maybe, but that's not the case for everyone. When evaluating software my business uses, not being stuck in a vendor locked in solution is a very high priority and I wouldn't want it any other way.
Anonymous Yellow-belly Coward, is that you?
Facebook has been profitable since 2009.
And make great coasters too. That's why they're so versatile.
So look, I will give you that eSata would be nice, but you couldn't do it for the same BOM. The connector and controller will drive the price up. So let us give up this fiction/pipedream that you could produce it for the same price. In the future, maybe, but right now? no.
If you read what I said, you'll notice I said I look forward to the time (as in, the future) when SATA and GigaE can be included at that price point. Not now, but in 12 to 18 months when it should be feasible.
But as for Gigabit Ethernet, just how much data do you think you can pump though a single core 1GHz ARM? What are you doing that 100Mbit isn't enough? Or is this just some kind of megapixel war thinking that bigger is better?
There are other devices with similar ARM processors that can handle gigabit. I don't know if the CPU in this Beagle device could do so, but again, in a year or so, a similar priced CPU would hopefully be able to. As for uses, there are many, but if you agree that SATA woud be useful then I'm sure you could understand why people may want faster than 100Mb/s network connectivity to go with it.
I think you would have a hard time proving that GigaE has enough demand to make a difference for the fast majority of [BeagleBone] users.
Yeah, I agree with this and that's why the Beagle / Pi is what it is for now. I've no complaints with that either, but future SoCs with GigaE and SATA will get down to the same price point eventually and no doubt we'll see these devices sporting that functionality in a year or so.
You're misunderstanding what I said. I like the Raspberry Pi and this new Beagle device. Really, they're great, and I can see a gazzillion uses for them where they are just perfect, some of which I plan to use them for myself.
All I am saying with regard to SATA and GigaE is that when the time comes they can be included at that price point, the scope for these devices being used as more serious network / storage devices expands greatly. Yes, I know their intended use does not necessarily include some of the things I'm thinking of and that's just fine, they do what they do very well. I'm simply looking forward to when the natural evolution of these devices includes those extra features at a sub $50 price. That will most likely happen in the next 12 to 18 months.
That may be so but it does not stop it from being a very valid point, especially for a lot of slashdot users. I like my Raspberry Pi and I really like the look of this new Beagle device. If it had SATA and GigaE for around the same price, I'd love it even more.
The inclusion of SATA and GigaE would presumably drive the price up to a point they don't think would let them compete with the Raspberry Pi. That will change though, and I'm very looking forward to that time. As soon as SATA and GigaE can be included at around the same price point, these devices suddenly become a viable basis for a whole wealth of serious storage and network devices. The only reason I don't use the Raspberry Pi for anything more serious than a media server on my network is because of the limitations of its USB throughput for both storage and networking.
Just to correct one point, the iPhone 4 has 512MB RAM.
YOU host the damned server, and YOU control the encryption keys. ALL traffic to the device is encrypted on YOUR side. RIM cannot see into these and does NOT have access to these keys.
Uhhh, unless I'm mistaken, he didn't say otherwise. He does actually mention that the big boys bought their own BES servers, keeping sensitive emails under their own control.
I think you need to take the time to read a user's comment more carefully before jumping down their throat.
Microsoft!?
If you're not already recording your life events on Facebook, I'm sure your friends are having a pretty good go at doing it for you!
Not just for HTC phones. I'd be tempted to flash CyanogenMod on any supported phone if it's not a Nexus device (and even then there are advantages with CM, especially with older Nexus devices that were deemed not powerful enough for 4.x).
Exactly.
I have one of these £24 / $36 Logitech Bluetooth audio receivers connected to my hi-fi and then send audio to it from my tablet, phone or PC. The weak point of the audio feed is then either the DAC in the Logitech device (seems good to me), the analogue RCA cables (again, fine by me), or the Bluetooth A2DP profile. I'm not sure about the specifics any more, but the Bluetooth A2DP profile is more than adequate for my MP3 collection.
Oh, and I use Google Play to host my ~100GB MP3 collection so it is accessible and streamable from any device.
No terminal!? Nice to know it still has the standard repositories though. I guess once you've logged in remotely (SSH presumably?) you could apt-get install a terminal application for local use?
I had a quick look at a few of the Youtube videos of it that have popped up over last few hours so see what you mean about fake data and static images for applications. Seems there's quite a bit missing at the moment.
*cares, not care's.
Edit buttons are much needed, Slashdot!
Who care's if some people get to make bucket loads of cash off of open source? And for whatever money the likes of Mr Shuttleworth make off it (and good on them, I say), there's a lot of money being poured back into OS projects that we get to enjoy the fruits of for free. We're all profiting from the hard work of developers in some way or other.
So, to all those with compatible hardware and willingness to test out these installs, what do you think so far?
Seeing as these images are packaged for devices that were originally running Android, how does it compare to Android in terms of responsiveness, features, ease of use, intuitiveness, eye candy, etc? Any glitches, glaring ommissions? Any really cool features?
And what's the 'Linux' side of it like? Can you pull up a terminal and do general sys admin type stuff on one of these things? Does it have well populated repositories with packages we've come to take for granted on our desktops and servers?
With that argument, you could say photocopying a book is an abstraction of routing control of atoms, simply controlling where the various atoms that ink is composed of are placed on the paper. I'm not necessarily disagreeing with you, but I don't think that argument would hold up in court.
Will it run Linux? ;)
Ethernet cables are great for desktop PCs, not quite so nice for laptops, and utterly useless for smartphones and tablets.
It's not that hard to do. Current Android / iOS apps adapt on the fly to different screen orientations and can adjust their layout for different size / density devices. It just takes a slightly different approach from the outset, a bit like responsive web design - you change the way you think about the UI constraints and end up with a UI that adapts to practically any size, orientation or pixel density.
A well made Android app is able to adapt it's UI for different size / density screens too, or have completely different UI layouts for different devices. The more popular apps do this very well and it's not hard to design for. Unfortunately a lot of Android developers still design primarily for phones and leave tablet owners with the same layout. It's getting better though.
I'm mainly an Android user and developer but love the way Ubuntu for tablets manages this side by side app stuff. Same with Surface - it's the one feature that I actually like from what I have seen of Surface tablets. I don't think it will be too long before a future Android release enables a similar feature, and when it does, it should be fairly trivial for Android app developers to make use of it because the ground work has already been laid. I'd say it's in a better position to do so than iOS apps in fact, because Android developers already have to cater for an almost limitless variety of screen sizes where as the few variations in iOS devices means many iOS apps have UIs designed for just two or three variants and are not as flexible (black bars on iPhone 5 for example).
I look at myself in the mirror and see a device that needs an anti-virus system from the outset.
Be sensible, use a condom.