Earlier quoted context omitted.
Do you realize governments can appropriate any technology, closed or open, for whatever purpose they see fit, and you're entitled to just "reasonable compensation"?
Can you expound a little more on this please. Let's say I write something, how, exactly can they appropriate the technology?
Real Men Use Android: Special Forces Favor Google Phone
11–20 of 52 posts
Re: Real Men Use Android: Special Forces Favor Google Phone
#12I still have a problem with using a VM on a phone and having GC on a phone. (I also have a problem with Objective C's function call overhead.)
This isn't hard realtime systems. Nobody is going to die because it takes a few seconds extra for them to download updates (the human brain takes a lot longer to process it anyway).
And JIT compiled java can be faster than native code, even in situations where you would not expect it (such as signal handling code).
Re: Real Men Use Android: Special Forces Favor Google Phone
#13Re: Real Men Use Android: Special Forces Favor Google Phone
#14I still have a problem with using a VM on a phone and having GC on a phone. (I also have a problem with Objective C's function call overhead.)
Macho. But a phone is exactly where you want a VM. In fact, I would love to be able to push vm images for my phone from my desktop machine. Wake up, plug phone, push image. Security upgrades, new GPS data, my downloaded podcasts, news, emails, etc. I want to be able to come home with a new handset, plug it, and have my "phone" back.
Pretty sure he meant Dalvik.
Re: Real Men Use Android: Special Forces Favor Google Phone
#15I still have a problem with using a VM on a phone and having GC on a phone. (I also have a problem with Objective C's function call overhead.)
Why, if the resulting products are performant and capable?
Re: Real Men Use Android: Special Forces Favor Google Phone
#16One problem with releasing your code as open source is it can get used in ways that you don't approve of, eg weapon systems by the military or crapware by the carriers.
It's up for debate if it's a bug or a feature but yes, that's an issue that anyone releasing code needs to consider.
Re: Real Men Use Android: Special Forces Favor Google Phone
#17Earlier quoted context omitted.
Why? They don't distribute it outside of their organization.
What if they shared it with a contractor?
Then they would have to share it with the contractor under the terms of the GPL. The contractor could then release it further. More likely though, the contractor would be brought in to work on the project and the military would argue that it wasn't distributing the code.
Re: Real Men Use Android: Special Forces Favor Google Phone
#18Re: Real Men Use Android: Special Forces Favor Google Phone
#19Earlier quoted context omitted.
Macho. But a phone is exactly where you want a VM. In fact, I would love to be able to push vm images for my phone from my desktop machine. Wake up, plug phone, push image. Security upgrades, new GPS data, my downloaded podcasts, news, emails, etc. I want to be able to come home with a new handset, plug it, and have my "phone" back.
Pretty sure he meant Dalvik.
Dalvik is not the only VM on a phone, and Android is not the only phone with a GC, nor is it coded primarily in Objective-C natively.
Pretty sure he was speaking 'in general'.
Re: Real Men Use Android: Special Forces Favor Google Phone
#20One problem with releasing your code as open source is it can get used in ways that you don't approve of, eg weapon systems by the military or crapware by the carriers.
One other thing people forget to consider when creating intellectual property of closed source or open source is that copyright does not last forever.
Every piece of intellectual property you create will eventually belong to the public domain, albeit after 75-100+ years.