They don't really. They protect against certain forms of reverse engineering. They do not protect against the Chinese wall. Or at least they're not supposed to. Which is what's so insidious about software patents. Since they don't really include the code or the algorithms it's pretty much impossible to get around them legitimately.
There's that, but it's also the first time that anybody has really done anything like this as an indie developer. Perhaps if they see success that will embolden others to try and do something like this. Personally, I'm looking forward to having mine. Even if my Nexus one has much better specs. Which it should at nearly twice the price.
In this case they might. One of the things that is sure to get them on board is if there's a good chance at setting precedence. I'm not sure what the outlook on this case would be, but it could resolve the issue once and for all. Or not.
I doubt that would help, most of the poor quality that you see in Youtube videos comes from the person making the videos. They don't generally use high quality equipment hence the poor quality. It doesn't matter what codec they use, even if they were to stop re-encoding it would still look blocky on most videos.
Clearly they're not doing it right. You're supposed to extend the functionality after you implement it. It's not really interoperable if everybody else can use your data.
Yes, but a developer is presumed to know something about APIs. It seems odd to me that any good can come of development by a developer that can't even understand a simple API. From what I saw on the site, it wasn't that bad at all, most of the end user stuff was similar to *NIX and the developer section wasn't terribly taxing either.
He made a decision knowing that it was a felony to do so. He could very easily have not shipped to addresses located in the US and not had to worry at all. He chose to do so anyways and he's paying the penalty.
Whether it's right or not is neither here nor there he knew it was a crime and chose to profit from it anyways. This isn't fascist crap, violate the law of any other nation with an extradition treaty and see what happens.
He's had the benefit of the judicial system and opted to plead guilty for a reduced term. Nobody including him suggests that he didn't do it.
That has nothing to do with Google. That's how major updates are always rolled out. The problem is that too many users in one cell trying to update at the same time can cause network outages. So major updates like this are staggered to reduce the likelihood of network breakage. And secondly, this is hardly a simple update, it brings quite a few changes on board as well as a substantial performance improvement.. On top of that anybody who buys a phone with a custom UI, whether it be blur or sense, is going to have to wait while the patches are applied and tested before it's rolled out. That's one of the reasons why the iPhone and Nexus One are in the positions they are. Since the people writing the OS and making the changes are working directly with the engineers creating the hardware they only have to test once. Whereas people who have a custom UI on top of that have to wait several months for it to be finished and tested before getting it.
And likewise, just because a phone was released last week doesn't mean that it's been tested for the update, they used a version for development because it was the latest at that time and then they released it when it was finished. They'll now have to do testing on the new version before they release it. Doing anything else would be horribly irresponsible.
It's still beta, I'm able to view flash, but it doesn't seem to work quite correctly. Because it's flash I can't use my track ball to select anything in the flash and if I zoom in there's no way of moving around. On top of which I'm having some difficulty selecting small buttons. But you can turn it off and if I understand the dialog make it ask before executing. The web browser on 2.2 is significantly faster than it was under 2.1, to the point where things seem to just pop right up rather than having to wait around.
Hoops? That's just for people that aren't willing to wait for the OTA update notification. The hoops we're jumping through is so that we don't have to wait for that. Updates like this are always staggered when done OTA to avoid unnecessarily straining the network.
The JIT compiler shouldn't help at all. Given the performance needs of flash, it's almost certain that Adobe has it running natively. The only way in which the JIT will affect a native application is by clearing up resources being used by other applications.
Not really, all forms of communications we've figured out can't. But it's a bit of a stretch to say that it can't. Whatever you use is only required to be without mass. As in we assume that everything we could use to transmit information would have mass. If it hasn't got mass then it's possible for it to beat the speed of light.
In honor of this occasion, I might have to pull out my old install disks and run it in dosbox. Perhaps even on my phone. But, I won't because I doubt that either Google or HTC will pay for the warranty repairs should my phone burst into flames.
Extradition, is one possibility for some matters. Which is why it's a good idea to be mindful of what countries you're doing business with. The prince of pot will be doing 5 years in the US because he opted to send his seeds here. Nobody forced him to send them to the US. Had he restricted himself to Canada, he wouldn't be going to prison.
I take it you're thinking of South Korea, North Korea is a dictatorship where they can and do throw random people into work camps under harsh conditions to be worked more or less to death.
This seems strange to me, no Tasers, but firearms? That strikes me as a bit odd, as common sense would dictate that since firearms are for the distinct purpose of killing and destroying only and that Tasers are meant to try and avoid that, that you've got it backwards in your country.
They're not non-lethal, they're called "less than lethal" because they're not supposed to kill people when used properly. It does not mean that nobody will die, it just means that it's been designed to avoid that to the extent possible while still putting them down. Rubber bullets for instance are generally not lethal, however people have died as a result of being hit in the wrong spot. Freak accidents do happen, but they're meant for cases where the alternative would be whipping out a firearm or some other weapon that's designed to kill.
That's the thing, while I don't personally use Facebook, I'm puzzled as to what exactly justifies them putting these sorts of large changes in place without at least defaulting to private. A lot of the changes they've made wouldn't be a big deal if the default was to not share the information beyond what the previous policy had allowed. If people want to opt-in, that's their business, but opting other people in is just dickery.
I know you're joking, but the way you do that is by googling the first 5 or 6 digits of your SSN, then manually comparing the last 4. The first 5 or 6 aren't unique and can be relatively easily guessed based upon the location and date of birth. Similar searches are great for finding CC#s that might be posted online.
Some already do. If you've got one through AT&T it's fully locked down. That was my only gripe about my backflip. Motorola had their locked down phone in the Milestone. One of the main reasons why I bought my Nexus one was that it would be getting all the updates promptly up until some point in the future when it's discontinued. It's really the only phone that guarantees you that it will be getting prompt updates for things that Google thinks are important.
I'd expect most other phones to take quite a bit of time as each carrier has to customize quite a bit before releasing it for the OTA update.
No, actually it is true. A cellphone, in contrast to the traditional type, does not pipe your own voice back at you through the receiver. The consequence is that people don't know how loud it is that they're being heard on the other end. Hence the yelling. Additionally most cellphones are designed to pick up very quiet speech at a close range.
Add that all up and you get people that are shouting on the phone and unaware that they're talking too loud. In fact in many cases you don't even have to be able to hear yourself talking for it to be coming in loud and clear on the other end of the call.
h.264 is a non-issue, they've chosen to go the correct route and not include it in the distribution. The alternative would be to require people to pay for the codec which doesn't really work for a free browser. The other browsers can do it because they've either got excessively deep pockets like MS or don't care about what that'll do the the web.
But Firefox is a notable exception, owning as many eyeballs as it does, it has some clout and the other smaller distributions should be backing it up on this issue. Unless we really want to be stuck forever in the plug in hell that the web has been put through over the last decade or so.
Slashdot Mirror
They don't really. They protect against certain forms of reverse engineering. They do not protect against the Chinese wall. Or at least they're not supposed to. Which is what's so insidious about software patents. Since they don't really include the code or the algorithms it's pretty much impossible to get around them legitimately.
There's that, but it's also the first time that anybody has really done anything like this as an indie developer. Perhaps if they see success that will embolden others to try and do something like this. Personally, I'm looking forward to having mine. Even if my Nexus one has much better specs. Which it should at nearly twice the price.
In this case they might. One of the things that is sure to get them on board is if there's a good chance at setting precedence. I'm not sure what the outlook on this case would be, but it could resolve the issue once and for all. Or not.
I doubt that would help, most of the poor quality that you see in Youtube videos comes from the person making the videos. They don't generally use high quality equipment hence the poor quality. It doesn't matter what codec they use, even if they were to stop re-encoding it would still look blocky on most videos.
Clearly they're not doing it right. You're supposed to extend the functionality after you implement it. It's not really interoperable if everybody else can use your data.
Vista is the UI for that? Well, we're safe now. Or is that completely screwed? Hmm, I guess whatever we are it's totally that now.
Yes, but a developer is presumed to know something about APIs. It seems odd to me that any good can come of development by a developer that can't even understand a simple API. From what I saw on the site, it wasn't that bad at all, most of the end user stuff was similar to *NIX and the developer section wasn't terribly taxing either.
He made a decision knowing that it was a felony to do so. He could very easily have not shipped to addresses located in the US and not had to worry at all. He chose to do so anyways and he's paying the penalty.
Whether it's right or not is neither here nor there he knew it was a crime and chose to profit from it anyways. This isn't fascist crap, violate the law of any other nation with an extradition treaty and see what happens.
He's had the benefit of the judicial system and opted to plead guilty for a reduced term. Nobody including him suggests that he didn't do it.
That has nothing to do with Google. That's how major updates are always rolled out. The problem is that too many users in one cell trying to update at the same time can cause network outages. So major updates like this are staggered to reduce the likelihood of network breakage. And secondly, this is hardly a simple update, it brings quite a few changes on board as well as a substantial performance improvement.. On top of that anybody who buys a phone with a custom UI, whether it be blur or sense, is going to have to wait while the patches are applied and tested before it's rolled out. That's one of the reasons why the iPhone and Nexus One are in the positions they are. Since the people writing the OS and making the changes are working directly with the engineers creating the hardware they only have to test once. Whereas people who have a custom UI on top of that have to wait several months for it to be finished and tested before getting it.
And likewise, just because a phone was released last week doesn't mean that it's been tested for the update, they used a version for development because it was the latest at that time and then they released it when it was finished. They'll now have to do testing on the new version before they release it. Doing anything else would be horribly irresponsible.
It's still beta, I'm able to view flash, but it doesn't seem to work quite correctly. Because it's flash I can't use my track ball to select anything in the flash and if I zoom in there's no way of moving around. On top of which I'm having some difficulty selecting small buttons. But you can turn it off and if I understand the dialog make it ask before executing. The web browser on 2.2 is significantly faster than it was under 2.1, to the point where things seem to just pop right up rather than having to wait around.
Hoops? That's just for people that aren't willing to wait for the OTA update notification. The hoops we're jumping through is so that we don't have to wait for that. Updates like this are always staggered when done OTA to avoid unnecessarily straining the network.
The JIT compiler shouldn't help at all. Given the performance needs of flash, it's almost certain that Adobe has it running natively. The only way in which the JIT will affect a native application is by clearing up resources being used by other applications.
Not really, all forms of communications we've figured out can't. But it's a bit of a stretch to say that it can't. Whatever you use is only required to be without mass. As in we assume that everything we could use to transmit information would have mass. If it hasn't got mass then it's possible for it to beat the speed of light.
Fucking boom? Is that sort of like dental dam?
In honor of this occasion, I might have to pull out my old install disks and run it in dosbox. Perhaps even on my phone. But, I won't because I doubt that either Google or HTC will pay for the warranty repairs should my phone burst into flames.
Extradition, is one possibility for some matters. Which is why it's a good idea to be mindful of what countries you're doing business with. The prince of pot will be doing 5 years in the US because he opted to send his seeds here. Nobody forced him to send them to the US. Had he restricted himself to Canada, he wouldn't be going to prison.
I take it you're thinking of South Korea, North Korea is a dictatorship where they can and do throw random people into work camps under harsh conditions to be worked more or less to death.
You must not be from Texas. They've already done that to history and have made great swipes at doing it to biology as well.
This seems strange to me, no Tasers, but firearms? That strikes me as a bit odd, as common sense would dictate that since firearms are for the distinct purpose of killing and destroying only and that Tasers are meant to try and avoid that, that you've got it backwards in your country.
They're not non-lethal, they're called "less than lethal" because they're not supposed to kill people when used properly. It does not mean that nobody will die, it just means that it's been designed to avoid that to the extent possible while still putting them down. Rubber bullets for instance are generally not lethal, however people have died as a result of being hit in the wrong spot. Freak accidents do happen, but they're meant for cases where the alternative would be whipping out a firearm or some other weapon that's designed to kill.
That's the thing, while I don't personally use Facebook, I'm puzzled as to what exactly justifies them putting these sorts of large changes in place without at least defaulting to private. A lot of the changes they've made wouldn't be a big deal if the default was to not share the information beyond what the previous policy had allowed. If people want to opt-in, that's their business, but opting other people in is just dickery.
I know you're joking, but the way you do that is by googling the first 5 or 6 digits of your SSN, then manually comparing the last 4. The first 5 or 6 aren't unique and can be relatively easily guessed based upon the location and date of birth. Similar searches are great for finding CC#s that might be posted online.
Some already do. If you've got one through AT&T it's fully locked down. That was my only gripe about my backflip. Motorola had their locked down phone in the Milestone. One of the main reasons why I bought my Nexus one was that it would be getting all the updates promptly up until some point in the future when it's discontinued. It's really the only phone that guarantees you that it will be getting prompt updates for things that Google thinks are important.
I'd expect most other phones to take quite a bit of time as each carrier has to customize quite a bit before releasing it for the OTA update.
No, actually it is true. A cellphone, in contrast to the traditional type, does not pipe your own voice back at you through the receiver. The consequence is that people don't know how loud it is that they're being heard on the other end. Hence the yelling. Additionally most cellphones are designed to pick up very quiet speech at a close range.
Add that all up and you get people that are shouting on the phone and unaware that they're talking too loud. In fact in many cases you don't even have to be able to hear yourself talking for it to be coming in loud and clear on the other end of the call.
h.264 is a non-issue, they've chosen to go the correct route and not include it in the distribution. The alternative would be to require people to pay for the codec which doesn't really work for a free browser. The other browsers can do it because they've either got excessively deep pockets like MS or don't care about what that'll do the the web.
But Firefox is a notable exception, owning as many eyeballs as it does, it has some clout and the other smaller distributions should be backing it up on this issue. Unless we really want to be stuck forever in the plug in hell that the web has been put through over the last decade or so.