No you are wrong. Some planes have autoland systems and these systems actually have to be used on a regular basis by law. They're not as good as human pilots but they do exist believe it or not.
Airlines have Traffic Collision Avoidance System (TCAS) with audible alerts to traffic that isn't played just over the headset. They would have heard any alerts if there was a problem.
I learned the basics of multithreading at my community college programming course in year 3. We had to write parallel sorting algorithms. I think any CS Bachelor's level degree that doesn't talk about threading is pretty worthless since this is going to be very important to know.
I pay out the ass for data(Rogers Canada) whether I use it or not, so I usually stay on 3G and use what I pay for instead of using wifi. Yes 3G is a little slower than wifi but I don't get anything off my bill if I don't use the network so I'm going to be using the network instead of wifi.
A majority of the people who died in the 1918 flu did not die from the flu. They died from secondary pneumonia which was bacterial. Today we have such things as antibiotics which work for 99% of pneumonia cases. If we had antibiotics back then, it's arguable that the death toll would not have been any worse than it is with the flu now.
AT&T seems to dictate whether or not some apps are on the store. Skype could have made 2 versions of the app, one for AT&T, one for the rest of the world but for some reason they didn't. Blocking 3G Skype on AT&T meant no iPhone can use Skype over 3G except when jail broken. Same can be said about the tethering app that was out for about a day and then got pulled.
I don't know where you buy these super awesome CF bulbs but all the ones I get that are cheap don't last much longer than an incandescent. They go in a few months of normal use.
Because Apple doesn't dig that deep most of the time into what the app actually uses. If they are running strings on the binary and looking for PhoneGap then they obviously don't want people using it for whatever their reason is. They don't examine every bite of your app though because that would take way too much time.
The reason they don't expose a lot of the APIs is because they're not finished. The internal APIs change quite a bit and once an API is published, they are under a lot of obligation to support it. Once the APIs are flushed out and supportable, they are usually moved to public APIs. Of course they try and restrict linking to some APIs that are used to control the phone hardware because IMO an app should generally not have any reason to mess with the phone's modem or anything that low.
Their problem is not with frameworks. A framework is just a library of code. Their problem was with people using PhoneGap to create programs in HTML and javascript. They want you to use the native GUI libraries to keep the look fairly consistent. While this is good in some ways, it's not good in other ways, but I can understand both sides.
Programming Objective-C is not difficult. If you can program in any other language you can program in Objective-C. The hardest part about it is learning which frameworks and APIs are required to write your app.
Actually, this is what the agreement says since I just copied it right from the document:
"No interpreted code may be downloaded or used in an Application except for code
that is interpreted and run by Apple's Documented APIs and built-in interpreter(s)."
It says you can use the built in interpreters such as the javascript interpreter in Safari. It does not say you can include any other interpreters in your program. Sometimes these programs get by the review process but it does not mean that they really allow it.
Except the majority of people don't know what tethering is and don't care enough to switch to any Android phone. I don't know if you've seen any commercials for these Android phones marketing to the general consumer but they make no mention of a Google OS running it. It says xyz phone "with Google".
Yes, obviously the OS X kernel already manages the threads. The thing that GCD manages is creating the threads based on current system work loads and the tasks that you give it. If you give it 1000 tasks on a 4 core machine and the FLASH plugin is hogging 100% of one core(as it does a lot), GCD may start 3 threads and when you quit the web browser, it will likely start another thread.
In general with most multithreaded programs, you probably start 1 thread per core because you can reasonably assume that this will perform pretty well if there's not much else going on. GCD is running at the OS level so it knows whether there is load on one core and if the other cores are free. Thus it will not start too many threads which will cause more context switching and degrade performance.
Maybe you should RTFC yourself. The links are right there on the page and unless you're a complete idiot you can clearly see it.
And since it seems you're so damned lazy to click links, the first "Introduction to Blocks and Grand Central Dispatch" says
"The central insight of GCD is shifting the responsibility for managing threads and their execution from applications to the operating system. As a result, programmers can write less code to deal with concurrent operations in their applications, and the system can perform more efficiently on single-processor machines, large multiprocessor servers, and everything in between. Without a pervasive approach such as GCD, even the best-written application cannot deliver the best possible performance, because it doesnâ(TM)t have full insight into everything else happening in the system."
If you can't figure out what that means then GTFO this site.
Actually, I found this kind of strange, but on Snow Leopard, all application executable code is compressed and stored in a resource fork. The reason it's not left in the data fork is because it apparently would confuse Leopard to have a compressed data fork in the app. So now to Leopard, all Snow Leopard apps look like 0 byte files.
See here http://dl.getdropbox.com/u/118359/ars/snow-leopard-indexed.html
Microsoft has said Outlook for Mac will be completely new, and use the Cocoa frameworks allowing it to be 64 bit. Entourage is written in Carbon and is quite the piece of crap because it's extremely slow, uses a monolithic database like Outlook which self corrupts sometimes.
Slashdot Mirror
No you are wrong. Some planes have autoland systems and these systems actually have to be used on a regular basis by law. They're not as good as human pilots but they do exist believe it or not.
Airlines have Traffic Collision Avoidance System (TCAS) with audible alerts to traffic that isn't played just over the headset. They would have heard any alerts if there was a problem.
I learned the basics of multithreading at my community college programming course in year 3. We had to write parallel sorting algorithms. I think any CS Bachelor's level degree that doesn't talk about threading is pretty worthless since this is going to be very important to know.
Uh, it's the bank charging wire transfer fees not Apple. Not all banks do it but a lot do.
I pay out the ass for data(Rogers Canada) whether I use it or not, so I usually stay on 3G and use what I pay for instead of using wifi. Yes 3G is a little slower than wifi but I don't get anything off my bill if I don't use the network so I'm going to be using the network instead of wifi.
A majority of the people who died in the 1918 flu did not die from the flu. They died from secondary pneumonia which was bacterial. Today we have such things as antibiotics which work for 99% of pneumonia cases. If we had antibiotics back then, it's arguable that the death toll would not have been any worse than it is with the flu now.
shitthatis long
AT&T seems to dictate whether or not some apps are on the store. Skype could have made 2 versions of the app, one for AT&T, one for the rest of the world but for some reason they didn't. Blocking 3G Skype on AT&T meant no iPhone can use Skype over 3G except when jail broken. Same can be said about the tethering app that was out for about a day and then got pulled.
The obvious solution is miniature solar cells at the end of the optical fiber
Yeah, fucking Apple, I can't even play MP3s on this iPod thing. Oh wait, yes I can
Yeah, they'd probably try and install Norton Antivirus for Mac. No one wants that crap.
I don't know where you buy these super awesome CF bulbs but all the ones I get that are cheap don't last much longer than an incandescent. They go in a few months of normal use.
http://db.tidbits.com/article/10509
Because Apple doesn't dig that deep most of the time into what the app actually uses. If they are running strings on the binary and looking for PhoneGap then they obviously don't want people using it for whatever their reason is. They don't examine every bite of your app though because that would take way too much time.
The reason they don't expose a lot of the APIs is because they're not finished. The internal APIs change quite a bit and once an API is published, they are under a lot of obligation to support it. Once the APIs are flushed out and supportable, they are usually moved to public APIs. Of course they try and restrict linking to some APIs that are used to control the phone hardware because IMO an app should generally not have any reason to mess with the phone's modem or anything that low.
Their problem is not with frameworks. A framework is just a library of code. Their problem was with people using PhoneGap to create programs in HTML and javascript. They want you to use the native GUI libraries to keep the look fairly consistent. While this is good in some ways, it's not good in other ways, but I can understand both sides.
Programming Objective-C is not difficult. If you can program in any other language you can program in Objective-C. The hardest part about it is learning which frameworks and APIs are required to write your app.
Actually, this is what the agreement says since I just copied it right from the document:
"No interpreted code may be downloaded or used in an Application except for code that is interpreted and run by Apple's Documented APIs and built-in interpreter(s)."
It says you can use the built in interpreters such as the javascript interpreter in Safari. It does not say you can include any other interpreters in your program. Sometimes these programs get by the review process but it does not mean that they really allow it.
Except the majority of people don't know what tethering is and don't care enough to switch to any Android phone. I don't know if you've seen any commercials for these Android phones marketing to the general consumer but they make no mention of a Google OS running it. It says xyz phone "with Google".
Yes, obviously the OS X kernel already manages the threads. The thing that GCD manages is creating the threads based on current system work loads and the tasks that you give it. If you give it 1000 tasks on a 4 core machine and the FLASH plugin is hogging 100% of one core(as it does a lot), GCD may start 3 threads and when you quit the web browser, it will likely start another thread.
In general with most multithreaded programs, you probably start 1 thread per core because you can reasonably assume that this will perform pretty well if there's not much else going on. GCD is running at the OS level so it knows whether there is load on one core and if the other cores are free. Thus it will not start too many threads which will cause more context switching and degrade performance.
Maybe you should RTFC yourself. The links are right there on the page and unless you're a complete idiot you can clearly see it.
And since it seems you're so damned lazy to click links, the first "Introduction to Blocks and Grand Central Dispatch" says
"The central insight of GCD is shifting the responsibility for managing threads and their execution from applications to the operating system. As a result, programmers can write less code to deal with concurrent operations in their applications, and the system can perform more efficiently on single-processor machines, large multiprocessor servers, and everything in between. Without a pervasive approach such as GCD, even the best-written application cannot deliver the best possible performance, because it doesnâ(TM)t have full insight into everything else happening in the system."
If you can't figure out what that means then GTFO this site.
"We recognize that libdispatch is a new technology and you likely have many questions. Here are some documentation resources for getting started:
Introducing Blocks and Grand Central Dispatch
Concurrency Programming Guide
Grand Central Dispatch (GCD) Reference"
Does it look like I copied it dumbass?
Actually, I found this kind of strange, but on Snow Leopard, all application executable code is compressed and stored in a resource fork. The reason it's not left in the data fork is because it apparently would confuse Leopard to have a compressed data fork in the app. So now to Leopard, all Snow Leopard apps look like 0 byte files.
See here
http://dl.getdropbox.com/u/118359/ars/snow-leopard-indexed.html
Microsoft has said Outlook for Mac will be completely new, and use the Cocoa frameworks allowing it to be 64 bit. Entourage is written in Carbon and is quite the piece of crap because it's extremely slow, uses a monolithic database like Outlook which self corrupts sometimes.