If the costs ended there, that'd be great. But they don't.
Someone has to do the requirements gathering draft up a specification. So you need a systems analyst. Then someone needs to take that specification and turn it into a real systems design. So you need a systems architect. Then someone needs to start writing code, so you need some developers. Someone needs to test all this code, so you need some testers. Someone needs to integrate all this into the existing environment and get it up and running; so you need some systems integrators. Then integration testing must happen, so you need some more testers. And, over all of this, you need at least a project manager or two to do timelines and communicate with management. Someone has to assure the quality of this system, so you need a quality assurance guy. Someone needs to maintain the system while it's running and even during development, so you need some systems administrators. Then management gets wind that all this is way too inefficient, so they hire some "Six Sigma blackbelts" to figure ways to improve the whole process by minimizing errors. They also might hire some management consultants to bring the whole team out on a retreat and give them motivational pep talks.
And after all of that, someone comes along and says "hey, you made it do this, but it also needs to do that." Everyone groans and the timeline slips.
Lather. Rinse. Repeat.
And all you wanted to do was write some damned code!
Hey! That's a good idea! Let's just shutdown the main reasons people are using high-speed internet technologies: streaming audio and video. And shutting down BitTorrent obviously wouldn't hurt.
Right. But lots of famous people will allow almost anyone to be their 'friend' so that they can hawk their latest book, CD, movie, coffee cup or whatever.
So, for example, you could friend, say Barack Obama, and then start a group called, say 'Friends of Osama Bin Laden' or 'the Al Qaeda United Terror Front' or whatever and hilarity then ensures.
The person in the photo is one of the vb.ly's two founders, well-known sex book author Violet Blue, who, I'm told, recently had all posts referencing her removed over at boingboing by the staff over there. No one seems to know why.
100 miles is inadequate for long distance travel. It's gotta be 200 miles -- which is about the distance you can go on a tank of gas in most cars -- or you can forget about road trips. And no, an airplane is not a decent substitute.
Few people care what record companies record their artists so they aren't going to be going to 20 different sites to download music, there were no real competitors to iTunes at that time so either they would abide by the iTunes policies or have their music be pirated left and right.
Look over your logic a little more carefully. iTunes had no real competitors because record companies refused to license the vast majority of their catalogs to anyone, let alone Apple.
When Apple started iTunes, they needed to convince the record companies that their music wouldn't just be pirated all over the Web. It's not like Apple didn't actually know that it would take about 5 minutes for someone to crack their FairPlay DRM, but they needed to somehow convince the record companies to release their catalogs to them. The DRM gave them a way to do that.
It's interesting to notice M$ is suing Motorola instead of Google.
Not really. Google doesn't make phones. All they do is provide some specifications and some (open) source code. The people to sue are the people making and selling the products, not someone simply providing the tools to make and sell products.
IOW, if you designed a new engine and patented some aspect of that engine, you don't sue the designer of a competing engine that infringes patents, you sue the car companies that put that engine in their cars.
Not that I normally defend Microsoft's behavior, but they did pick the appropriate defendant in this case.
Yet, the application must have requested WRITE_EXTERNAL_STORAGE in its Manifest.xml. If Market didn't tell you about it, that's a Market issue.
All applications can READ from the external storage, which is considered public. Private data, OTOH, is required to be stored on the internal storage. This is secifically mentioned in the Developer Guide. If an app is storing private data on the external storage, then you need to tell the author that he or she is stupid. You can, of course, always remove files from the public storage by connecting mounting the SD card on a PC.
A basic Android application has no permissions associated with it, meaning it can not do anything that would adversely impact the user experience or any data on the device. To make use of protected features of the device, you must include in your AndroidManifest.xml one or more tags declaring the permissions that your application needs.
Google Chrome, Google Earth, Mozilla Web Browser. The individual OOo applications are (were?) called OpenOffice.org Writer, OpenOffice.org Calc, etc. The suite is (was?) called OpenOffice.org, which, I agree (and apparently so does The Document Foundation) that this is a bit confusing.
1. TFA is about DNS. 2. There is no "TCPv6". There is TCP over IPV4 and TCP over IPv6. They are, however, the same TCP. 3. TCP/IP is also used as a broad term for for the entire network stack. For example, DNS is an application-level protocol implemented on top of TCP and UDP over IP. But the entire thing is, loosely speaking, TCP/IP technologies.
Really? DNS is broken? So typing say, http://slashdot.org/ doesn't work for you?
No. DNS has a few security issues, but they're mostly minor. The fact that DNS works for millions of people every day without issue at least 99% of the time proves that DNS is a successful design, even if it could use some security updating.
Hmmm? I didn't imply that XCode had to be purchased. And the ownership of a Mac isn't the only prerequisite that might cost the submitter money. If the submitter would like to sell apps through the App store, he needs to pay Apple money for that -- to the tune of $99 per year. In addition, developers only get to keep 70% of revenues -- the other 30% goes to Apple. The Android Market is the same -- only 30% goes to the carriers rather than Google for paid apps; however, Android Market desn't require a $99 per year fee.
Yes. You should hedge your bets and learn both. The smartphone wars are far from over, and most smartphone content producers are releasing for, at the very least, both iOS and Android. Some also simultaneously release for Blackberry and Windows Mobile as well.
Each platform has its relative strengths and weaknesses. Writing code on Android pretty much means learning Java; similarly, writing code on iOS pretty much means learning Objective C. Neither language is likely to become obsolete very soon. The startup costs for writing code on Android are a bit lower; you don't need to buy anything to write Android apps. If you expect to write iOS apps, you need a Mac and you need XCode. On Android, you need Eclipse and the Android Eclipse SDK.
Slashdot Mirror
If the costs ended there, that'd be great. But they don't.
Someone has to do the requirements gathering draft up a specification. So you need a systems analyst. Then someone needs to take that specification and turn it into a real systems design. So you need a systems architect. Then someone needs to start writing code, so you need some developers. Someone needs to test all this code, so you need some testers. Someone needs to integrate all this into the existing environment and get it up and running; so you need some systems integrators. Then integration testing must happen, so you need some more testers. And, over all of this, you need at least a project manager or two to do timelines and communicate with management. Someone has to assure the quality of this system, so you need a quality assurance guy. Someone needs to maintain the system while it's running and even during development, so you need some systems administrators. Then management gets wind that all this is way too inefficient, so they hire some "Six Sigma blackbelts" to figure ways to improve the whole process by minimizing errors. They also might hire some management consultants to bring the whole team out on a retreat and give them motivational pep talks.
And after all of that, someone comes along and says "hey, you made it do this, but it also needs to do that." Everyone groans and the timeline slips.
Lather. Rinse. Repeat.
And all you wanted to do was write some damned code!
So, then tweets are like prayers?:
Aside from a total economic disaster, that is.
A couple of GBU-31s and an F-22 Raptor ought to fix that...
Hey! That's a good idea! Let's just shutdown the main reasons people are using high-speed internet technologies: streaming audio and video. And shutting down BitTorrent obviously wouldn't hurt.
Then we'll party like it's 1997!
The same way that bottling water from Rio Grande would not work.
Tim-MAHY!
That's why I think we need different units. Maybe someone could express the size in Libraries of Congress or Volkswagen Beetles or something.
Yep. How do you suppose a male deity, Yahweh, gave birth to Adam?
Right. But lots of famous people will allow almost anyone to be their 'friend' so that they can hawk their latest book, CD, movie, coffee cup or whatever.
So, for example, you could friend, say Barack Obama, and then start a group called, say 'Friends of Osama Bin Laden' or 'the Al Qaeda United Terror Front' or whatever and hilarity then ensures.
Not that I'm suggesting anyone should do that.
The person in the photo is one of the vb.ly's two founders, well-known sex book author Violet Blue, who, I'm told, recently had all posts referencing her removed over at boingboing by the staff over there. No one seems to know why.
100 miles is inadequate for long distance travel. It's gotta be 200 miles -- which is about the distance you can go on a tank of gas in most cars -- or you can forget about road trips. And no, an airplane is not a decent substitute.
Double that and you got a deal.
Look over your logic a little more carefully. iTunes had no real competitors because record companies refused to license the vast majority of their catalogs to anyone, let alone Apple.
When Apple started iTunes, they needed to convince the record companies that their music wouldn't just be pirated all over the Web. It's not like Apple didn't actually know that it would take about 5 minutes for someone to crack their FairPlay DRM, but they needed to somehow convince the record companies to release their catalogs to them. The DRM gave them a way to do that.
Not really. Google doesn't make phones. All they do is provide some specifications and some (open) source code. The people to sue are the people making and selling the products, not someone simply providing the tools to make and sell products.
IOW, if you designed a new engine and patented some aspect of that engine, you don't sue the designer of a competing engine that infringes patents, you sue the car companies that put that engine in their cars.
Not that I normally defend Microsoft's behavior, but they did pick the appropriate defendant in this case.
Yet, the application must have requested WRITE_EXTERNAL_STORAGE in its Manifest.xml. If Market didn't tell you about it, that's a Market issue.
All applications can READ from the external storage, which is considered public. Private data, OTOH, is required to be stored on the internal storage. This is secifically mentioned in the Developer Guide. If an app is storing private data on the external storage, then you need to tell the author that he or she is stupid. You can, of course, always remove files from the public storage by connecting mounting the SD card on a PC.
The Android Developer reference says otherwise:
Google Chrome, Google Earth, Mozilla Web Browser. The individual OOo applications are (were?) called OpenOffice.org Writer, OpenOffice.org Calc, etc. The suite is (was?) called OpenOffice.org, which, I agree (and apparently so does The Document Foundation) that this is a bit confusing.
No, but I hear Tai restaurants are shaking in their boots over some noodle dishes...
1. TFA is about DNS.
2. There is no "TCPv6". There is TCP over IPV4 and TCP over IPv6. They are, however, the same TCP.
3. TCP/IP is also used as a broad term for for the entire network stack. For example, DNS is an application-level protocol implemented on top of TCP and UDP over IP. But the entire thing is, loosely speaking, TCP/IP technologies.
What does IPv4 have to do with DNS? (hint: nothing. Modern DNS servers support IPv6)
Really? DNS is broken? So typing say, http://slashdot.org/ doesn't work for you?
No. DNS has a few security issues, but they're mostly minor. The fact that DNS works for millions of people every day without issue at least 99% of the time proves that DNS is a successful design, even if it could use some security updating.
Except that 'hslookup facebook.com', et al.. worked with no issues. RTFS.
Hmmm? I didn't imply that XCode had to be purchased. And the ownership of a Mac isn't the only prerequisite that might cost the submitter money. If the submitter would like to sell apps through the App store, he needs to pay Apple money for that -- to the tune of $99 per year. In addition, developers only get to keep 70% of revenues -- the other 30% goes to Apple. The Android Market is the same -- only 30% goes to the carriers rather than Google for paid apps; however, Android Market desn't require a $99 per year fee.
Yes. You should hedge your bets and learn both. The smartphone wars are far from over, and most smartphone content producers are releasing for, at the very least, both iOS and Android. Some also simultaneously release for Blackberry and Windows Mobile as well.
Each platform has its relative strengths and weaknesses. Writing code on Android pretty much means learning Java; similarly, writing code on iOS pretty much means learning Objective C. Neither language is likely to become obsolete very soon. The startup costs for writing code on Android are a bit lower; you don't need to buy anything to write Android apps. If you expect to write iOS apps, you need a Mac and you need XCode. On Android, you need Eclipse and the Android Eclipse SDK.
But, like I said, I wouldn't learn just one.