I'm sure I am preaching to the crowd here, but the crash should be considered in light of the following facts:
- SpaceX customers still pay for the entire rocket, there is no discount applied yet
- All other competing rockets do not have this capability and burn up on re-entry
- Every landing attempt provides new and unique data that can be used for continuous improvement
- The primary mission (what they are being paid for) was still accomplished
This is going to get downvoted to oblivion, but here it goes.
Normal people do not care about software updates. They care even less about security updates. They are on their contracts and happy to pick up a new phone every 2 years or so, and there is little elapsed time before their phone's current OS will go out of fashion.
Nerds do care about this stuff (myself included). This is the specific reason I buy the Nexus line. I have had non-Nexus devices before, and gotten bored (rather than frustrated) over lack of OS update, so I've flashed custom ROMs.
I read that Lollipop will include webview as part of the Google Play Services framework, which is Google's cloud-based framework that they have been moving more and more Android services to.
Unlike app store updates and normal Android system updates, Google Play Services works as a silent push update, so phone providers and manufacturers cannot block the update. I'd hazard a guess and say this may have something to do it.
NASA is providing incentives - http://en.wikipedia.org/wiki/Commercial_Orbital_Transportation_Services http://en.wikipedia.org/wiki/Commercial_Crew_Development
Understandably these are to meet NASA's requirements (which makes since, since they would be the main customer for the services anyway), so they don't just want to dole it out without a decision process.
There's also stuff like the Lunar X prize, but none of this is in the magnitudes you are talking about (good luck getting that through congress).
Sorry -- slightly unhelpful post in that I don't have a link, but according to some interviews I've seen with Elon Musk much of it is to do with modern engineering. One of the examples he gave (which was during a totally non-sciency talk show) was about how they processed and bent a particular type of metal used in the Falcon.
Believe the purpose of landing it in the ocean was to actually test the deployment of the legs on the rocket (this is the first model where they've included the legs). So basically just launching it, extending the legs out and then testing if the first stage lands in the ocean properly with the legs deployed.
Also perhaps already mentioned in this thread but since they upgraded Falcon to 9 to v1.1 they have continued to offer the old v1.0 payload to customers, reserving the additional payload 1.1 is capable of for testing reusable components.
Have had the charging port wear out twice on my Galaxy Nexus. Though I'd boil that down to bad hardware design and certainly wouldn't be reflected in my Nexus 5.
In relation to your 'I'd like to see him try' comment - Elon Musk named the Dragon spacecraft after "puff the magic dragon".. because of all of his critics who said his projects couldn't succeed.. http://www.space.com/15799-spacex-dragon-capsule-fun-facts.html
Things Google have done recently to combat fragmentation:
- Announced the release of the Android PDK, a preview-esque version of the new OS available to manufacturers before the official release hits source
- Begun de-coupling official Google apps from the OS and therefore from the update cycle (e.g. Google keyboard, IIRC Gmail and Maps, etc)
- From a 'smoke and mirror' perspective, kept the Android codenames the same across Jellybean (4.1 and 4.2)
- Most recently, "updated" Android completely without actually updating it via pushing updates to core apps and services like Play Store, Music player, sync APIs, etc.
- Adding to above: Held off on releasing a numbered Android update to let the natural cycle for replacing handsets to continue (so people with Android 2.1 phones hit the end of their contracts and buy 4.2 phones) .. and certainly much more. I'm thinking the #1 point on the PDK will be significant as we have yet to see the real effect of this. Previously the source code for new Android versions would be released to both the public and manufacturers at the same time, so you'd have teams like Cyanogenmod quickly port and do their own QA on releases using stock Android, while manufacturers had to update their custom UI's against the new version, go through their own rigorous QA processes, go through telco QA processes and timeframes, etc. The end result was updates being released by community teams (excluding Nexus devices) long before manufacturers did, leading to much discontent.
Here is the "official" Mars One answer to bone issues (site seems to be down now so copy and paste from Google Cache):
Prolonged weightlessness causes osteoporosis, which can be reduced by exercise and medicine. Research onboard the International Space Station has led to even better and more effective training programs being drawn up, and new machines being made specifically for astronauts. Conjointly, there have been major leaps forward in medications capable of partially preventing declining calcium levels.
Recent study about 14 ISS astronauts, who were 4-6 month in space, showed a maximum bone loss of 1.5% / month in the most vulnerable (from bone loss point of view) region - the hip. Therefore the bone loss after arriving on Mars, after a 7 month flight, would be in the worst case scenario 10.5%.
When they arrive on a planet with 62% less gravity, they would have 100% more bone density compared to humans under earth gravity.
It may not be exactly what Gartner envisioned, but there's the RepRap project which aims to be able to fully self replicate. At least check it could print 50% of it's own parts, and they are working on being able to print electric circuitry next - http://www.reprapcentral.com/vmchk.html
It sounds like this modification of the SDK might be another move toward Google defending against this Aluyin OS-style modification of Android. While Android is commonly cited as being "fragmented" due to the %'s of handsets that have older versions of Android on them (see the Development Dashboard); what these links talk about is a very serious, more dangerous style of fragmentation. Currently all Android apps are forward compatible with future versions and most are backward compatible (unless the develop chooses to use a new API and not include any graceful degradation in their app for older versions). But Google's flavor of Android is also sideways-compatible with the likes of Amazon such that if you write an app intended for the play store and later decide to distribute it to an Amazon-flavored device (via their app store or other various means), you can do this.
The implications of allowing such activities to continue are that Android could turn into a true wild-west of operating systems. From a technical standpoint, a budding Chinese developer modifies some core Android source code which work with the apps being developed by his company, but suddenly break every other app developed for their flavor of the Android OS -- and then suddenly developers for that hypothetical OS can no longer pick up their app and take it to Google's (/Amazon's) flavor of Android without resorting to hacks and workarounds. Suddenly that Android Development dashboard needs to represent that data in more than 2 dimensions - and Google's got a world of new problems to deal with.
See this Architecture Diagram for some further context. Basically the various Android OEM's and custom ROM developers such as Cyanogenmod should only really be modifying the blue bits and maybe some of the green (I'm sure ROM developers would argue on the red bits, but in a perfect world..). Seems like Google is trying to stop the messing with of the yellow "Android runtime" section.
We agree that the Aliyun OS is not part of the Android ecosystem and you're under no requirement to be compatible.
However, the fact is, Aliyun uses the Android runtime, framework and tools. And your app store contains Android apps (including pirated Google apps). So there's really no disputing that Aliyun is based on the Android platform and takes advantage of all the hard work that's gone into that platform by the OHA.
So if you want to benefit from the Android ecosystem, then make the choice to be compatible. [It's] easy, free, and we'll even help you out. But if you don't want to be compatible, then don't expect help from OHA members that are all working to support and build a unified Android ecosystem.
Get yourself involved in some Corporate Performance Management stuff (specifically OLAP). This is the perfect intersection of IT and Business/Finance. Think Oracle Hyperion, IBM Cognos TM1, etc. Guys I work with (not me) are currently putting this stuff in at our clients - even the guys without the technical know-how (e.g. they still have finance/technical backgrounds but don't actually build it) have a role in navigating/deciphering and translating whatever bunch of Excel models and disparate systems into Functional Requirements, which get built into Multidimensional structures by the technical guys.
I'd start by looking for companies that do this type of stuff - the role name could be anything from Solution Architect to Consultant. Good luck!
1. It would have to be cheap ($100-$150)
2. The screen should be touch.
3. Might the dock supplier need to be include their own Android launcher? Can't see the various different launchers and configurations all fitting perfectly. This would be a problem for people who want to take their phone home and use it but prefer their launcher of choice.
4. Google will have to get into gear for QuickOffice pretty quickly/merge it with Google Docs/pull together all the main bits of functionality missing from each program, make the blur between Google Drive and Google Docs less confusing and improve the overall user experience.
5. Docking/undocking: seamless, no funny business specific to certain handsets.
Perhaps Symantec are flagging it as malware because it is using permissions that the app clearly does not need, and it is just some rookie developer that has permission code copied in from some other site?
Slashdot Mirror
I'm sure I am preaching to the crowd here, but the crash should be considered in light of the following facts:
- SpaceX customers still pay for the entire rocket, there is no discount applied yet
- All other competing rockets do not have this capability and burn up on re-entry
- Every landing attempt provides new and unique data that can be used for continuous improvement
- The primary mission (what they are being paid for) was still accomplished
.. while they're at it. Worst key combo ever. Hit it all the time. Don't try this at home.
This is going to get downvoted to oblivion, but here it goes.
Normal people do not care about software updates. They care even less about security updates. They are on their contracts and happy to pick up a new phone every 2 years or so, and there is little elapsed time before their phone's current OS will go out of fashion.
Nerds do care about this stuff (myself included). This is the specific reason I buy the Nexus line. I have had non-Nexus devices before, and gotten bored (rather than frustrated) over lack of OS update, so I've flashed custom ROMs.
I read that Lollipop will include webview as part of the Google Play Services framework, which is Google's cloud-based framework that they have been moving more and more Android services to.
Unlike app store updates and normal Android system updates, Google Play Services works as a silent push update, so phone providers and manufacturers cannot block the update. I'd hazard a guess and say this may have something to do it.
Source: http://developer.telerik.com/f...
NASA is providing incentives -
http://en.wikipedia.org/wiki/Commercial_Orbital_Transportation_Services
http://en.wikipedia.org/wiki/Commercial_Crew_Development
Understandably these are to meet NASA's requirements (which makes since, since they would be the main customer for the services anyway), so they don't just want to dole it out without a decision process.
There's also stuff like the Lunar X prize, but none of this is in the magnitudes you are talking about (good luck getting that through congress).
Sorry -- slightly unhelpful post in that I don't have a link, but according to some interviews I've seen with Elon Musk much of it is to do with modern engineering. One of the examples he gave (which was during a totally non-sciency talk show) was about how they processed and bent a particular type of metal used in the Falcon.
Believe the purpose of landing it in the ocean was to actually test the deployment of the legs on the rocket (this is the first model where they've included the legs). So basically just launching it, extending the legs out and then testing if the first stage lands in the ocean properly with the legs deployed.
Also perhaps already mentioned in this thread but since they upgraded Falcon to 9 to v1.1 they have continued to offer the old v1.0 payload to customers, reserving the additional payload 1.1 is capable of for testing reusable components.
http://www.nasaspaceflight.com/2014/01/orbitals-antares-loft-cygnus-orb-1-mission/
Have had the charging port wear out twice on my Galaxy Nexus. Though I'd boil that down to bad hardware design and certainly wouldn't be reflected in my Nexus 5.
I believe this was the error I was having. Solution: unplug my USB mouse before installing. Welcome to 1997.
In relation to your 'I'd like to see him try' comment - Elon Musk named the Dragon spacecraft after "puff the magic dragon".. because of all of his critics who said his projects couldn't succeed.. http://www.space.com/15799-spacex-dragon-capsule-fun-facts.html
Your answer to "fragmentation" is here
Things Google have done recently to combat fragmentation:
.. and certainly much more. I'm thinking the #1 point on the PDK will be significant as we have yet to see the real effect of this. Previously the source code for new Android versions would be released to both the public and manufacturers at the same time, so you'd have teams like Cyanogenmod quickly port and do their own QA on releases using stock Android, while manufacturers had to update their custom UI's against the new version, go through their own rigorous QA processes, go through telco QA processes and timeframes, etc. The end result was updates being released by community teams (excluding Nexus devices) long before manufacturers did, leading to much discontent.
- Announced the release of the Android PDK, a preview-esque version of the new OS available to manufacturers before the official release hits source
- Begun de-coupling official Google apps from the OS and therefore from the update cycle (e.g. Google keyboard, IIRC Gmail and Maps, etc)
- From a 'smoke and mirror' perspective, kept the Android codenames the same across Jellybean (4.1 and 4.2)
- Most recently, "updated" Android completely without actually updating it via pushing updates to core apps and services like Play Store, Music player, sync APIs, etc.
- Adding to above: Held off on releasing a numbered Android update to let the natural cycle for replacing handsets to continue (so people with Android 2.1 phones hit the end of their contracts and buy 4.2 phones)
No coffee in the alternate universe, universe full of very angry people. Coincidence?
Here is the "official" Mars One answer to bone issues (site seems to be down now so copy and paste from Google Cache):
Prolonged weightlessness causes osteoporosis, which can be reduced by exercise and medicine. Research onboard the International Space Station has led to even better and more effective training programs being drawn up, and new machines being made specifically for astronauts. Conjointly, there have been major leaps forward in medications capable of partially preventing declining calcium levels.
Recent study about 14 ISS astronauts, who were 4-6 month in space, showed a maximum bone loss of 1.5% / month in the most vulnerable (from bone loss point of view) region - the hip. Therefore the bone loss after arriving on Mars, after a 7 month flight, would be in the worst case scenario 10.5%.
When they arrive on a planet with 62% less gravity, they would have 100% more bone density compared to humans under earth gravity.
Google Cache link: http://webcache.googleusercontent.com/search?q=cache:YS4BxMBdYy4J:mars-one.com/en/faq-en/19-faq-health/193-will-the-astronauts-develop-osteoporosis+&cd=1&hl=en&ct=clnk&gl=au
Touches on the tendency for systems to be inherently more complex as time goes on http://www.ted.com/talks/david_christian_big_history.html
It may not be exactly what Gartner envisioned, but there's the RepRap project which aims to be able to fully self replicate. At least check it could print 50% of it's own parts, and they are working on being able to print electric circuitry next - http://www.reprapcentral.com/vmchk.html
Andy Rubin (Co-founder of Android before Google bought it, and current VP of Mobile) posted this a few months ago in relation to Aluyin OS. https://plus.google.com/112599748506977857728/posts/hRcCi5xgayg (which links to the official Android blog: http://officialandroid.blogspot.com.au/2012/09/the-benefits-importance-of-compatibility.html).
It sounds like this modification of the SDK might be another move toward Google defending against this Aluyin OS-style modification of Android. While Android is commonly cited as being "fragmented" due to the %'s of handsets that have older versions of Android on them (see the Development Dashboard); what these links talk about is a very serious, more dangerous style of fragmentation. Currently all Android apps are forward compatible with future versions and most are backward compatible (unless the develop chooses to use a new API and not include any graceful degradation in their app for older versions). But Google's flavor of Android is also sideways-compatible with the likes of Amazon such that if you write an app intended for the play store and later decide to distribute it to an Amazon-flavored device (via their app store or other various means), you can do this.
The implications of allowing such activities to continue are that Android could turn into a true wild-west of operating systems. From a technical standpoint, a budding Chinese developer modifies some core Android source code which work with the apps being developed by his company, but suddenly break every other app developed for their flavor of the Android OS -- and then suddenly developers for that hypothetical OS can no longer pick up their app and take it to Google's (/Amazon's) flavor of Android without resorting to hacks and workarounds. Suddenly that Android Development dashboard needs to represent that data in more than 2 dimensions - and Google's got a world of new problems to deal with.
See this Architecture Diagram for some further context. Basically the various Android OEM's and custom ROM developers such as Cyanogenmod should only really be modifying the blue bits and maybe some of the green (I'm sure ROM developers would argue on the red bits, but in a perfect world..). Seems like Google is trying to stop the messing with of the yellow "Android runtime" section.
Really, Android "copied" Apple's field of icons? I was using Nokia SmartPhones in 2006 which used the same style. Apple must have a time machine?
We agree that the Aliyun OS is not part of the Android ecosystem and you're under no requirement to be compatible.
However, the fact is, Aliyun uses the Android runtime, framework and tools. And your app store contains Android apps (including pirated Google apps). So there's really no disputing that Aliyun is based on the Android platform and takes advantage of all the hard work that's gone into that platform by the OHA.
So if you want to benefit from the Android ecosystem, then make the choice to be compatible. [It's] easy, free, and we'll even help you out. But if you don't want to be compatible, then don't expect help from OHA members that are all working to support and build a unified Android ecosystem.
Get yourself involved in some Corporate Performance Management stuff (specifically OLAP). This is the perfect intersection of IT and Business/Finance. Think Oracle Hyperion, IBM Cognos TM1, etc. Guys I work with (not me) are currently putting this stuff in at our clients - even the guys without the technical know-how (e.g. they still have finance/technical backgrounds but don't actually build it) have a role in navigating/deciphering and translating whatever bunch of Excel models and disparate systems into Functional Requirements, which get built into Multidimensional structures by the technical guys. I'd start by looking for companies that do this type of stuff - the role name could be anything from Solution Architect to Consultant. Good luck!
1. It would have to be cheap ($100-$150)
2. The screen should be touch.
3. Might the dock supplier need to be include their own Android launcher? Can't see the various different launchers and configurations all fitting perfectly. This would be a problem for people who want to take their phone home and use it but prefer their launcher of choice.
4. Google will have to get into gear for QuickOffice pretty quickly/merge it with Google Docs/pull together all the main bits of functionality missing from each program, make the blur between Google Drive and Google Docs less confusing and improve the overall user experience.
5. Docking/undocking: seamless, no funny business specific to certain handsets.
http://yro.slashdot.org/story/12/05/27/1917213/patent-troll-now-armed-with-thousands-of-nortel-patents?utm_source=feedburnerGoogle+International&utm_medium=feed&utm_campaign=Feed%3A+Slashdot%2Fslashdot+(Slashdot)&utm_content=Google+International
FYI Valve have dropped the "Defense of the Ancients" moniker and now more generically refer to it as Dota.
Perhaps Symantec are flagging it as malware because it is using permissions that the app clearly does not need, and it is just some rookie developer that has permission code copied in from some other site?