I had two different iPhones over two years. I experienced dropped calls all the time. It was awful. I hated AT&T. During this time, I even moved from the East Coast to the West Coast and still had the same poor experience. I was ready to leave AT&T. I had friends on AT&T that didn't have iPhones and they said they had a good experience with AT&T. So, I decided to get a new phone. I got a Samsung Focus running Windows Phone 7. Now, my experience is really good. The network seems fast and reliable. No more dropped call issues. I can't speak for everybody. But, this is my experience. I wish I had changed phones sooner. It would've saved me tons of aggravation.
The biggest difference between Linux Kernel development and Windows OS development is that the former treats all bugs as important, while the latter tries to classify some of them us not important, even when they are known to make the system less secure. It is this difference, and not some imaginary idea that crackers only target Windows systems, that accounts for the much higher failure rate of Windows vs. Linux in the malware susceptibility domain.
This has absolutely nothing to do with the Windows kernel. AFAIK, there are zero known vulnerabilities in the Windows kernel as of today. So, I guess you are trying to compare the Linux kernel with the entire Windows operating system. How does that comparison make any sense?
Sounds like a really easy way for your standard user to administer their phone. My mom would totally get that....no wait....I think I meant the opposite of that. Yeah.
Seriously, though, how do you communicate this to your standard, non-techie user?
If Microsoft had done this, everyone would be up in arms about how awful they were. Saying you just have to reinstall your OS is completely ridiculous. And, if it only applied to machines that dual-booted Linux, the conspiracy theorists would be claiming the MS did it on purpose to prevent people from dual booting. So, seriously, where's the outrage?
You are uninformed. While it would have been possible for Apple to take this approach (others have done it successfully), they decided not to. Instead, the BSD layer runs in kernel mode. When writing kernel modules for Mac OS X, you often end up using both the Mach and BSD apis.
I don't know where you get your information, but it is incorrect. When you develop kernel drivers for Mac OS X, you program to both the Mach and FreeBSD APIs. It does not just use FreeBSD utilities.
Mac OS X uses Mach, but it also uses a FreeBSD kernel and compiles them together. This eliminates the runtime characteristics of a Microkernel. This is actually quite common.
So, even though it uses Mach, you can't call it a Microkernel.
They can't even build a desktop PC that won't cras
on
Cars that Can't Crash?
·
· Score: 1
Writing less clear code because you believe it is more efficient is the worst thing you can do for your code. It will only cause bugs in the short-term and create less manageable code in the longer-term.
Do not perform minor optimizations without first: a) Determining there is a performance problem b) Profiling your code to determine what areas should be optimized.
This does not mean that you should choose naive algortithms for the problem at hand. Choosing the proper algorithm for the problem at hand is always important.
Hand-optimized code should be reserved for those times when you have profiled your code with reasonable inputs and have shown that the lack of clarity is compensated for by the increased performance.
The example you gave is a perfect example of a hand optimization that is completely worthless with today's compilers.
The DDK (Driver Development Kit) contains a command-line verison of their C++ compiler. It also contains PREfast, which is a static code analysis tool, similar to Lint.
Usability doesn't require that you enable the system to do anything that it can't do today. All usability focuses on is making it easier / more intuitive to accomplish those same tasks.
Rather than speculating, just find out. Attach WinDbg to IE and check to see if it using the standard Winsock interface, or some other one. Be sure to make sure that all "reserved" parameters have their documented required value.
and NT- an even bigger ball of bloat, being at heart a reimplimentation of OS/2's C sources in C++- was reborn as Win2k about 4 years later.
NT is not written in C++, it is mostly C (with some assembly, obviously). It is also not a reimplementation of OS/2. As a matter of fact, it looks a helluva lot more like VMS than OS/2. Sure, the kernel and executive both handle objects, but not in the C++ sense. They are really just C structs that the kernel and executive keep track of and make sure don't leak (all get freed when an application terminates, if the app forgot to free them itself).
Slashdot Mirror
I had two different iPhones over two years. I experienced dropped calls all the time. It was awful. I hated AT&T. During this time, I even moved from the East Coast to the West Coast and still had the same poor experience. I was ready to leave AT&T. I had friends on AT&T that didn't have iPhones and they said they had a good experience with AT&T. So, I decided to get a new phone. I got a Samsung Focus running Windows Phone 7. Now, my experience is really good. The network seems fast and reliable. No more dropped call issues. I can't speak for everybody. But, this is my experience. I wish I had changed phones sooner. It would've saved me tons of aggravation.
This has absolutely nothing to do with the Windows kernel. AFAIK, there are zero known vulnerabilities in the Windows kernel as of today. So, I guess you are trying to compare the Linux kernel with the entire Windows operating system. How does that comparison make any sense?
That isn't true. I just tried it. Without the quote, the top hit is Google health. With it, it isn't Google Health.
Sounds like a really easy way for your standard user to administer their phone. My mom would totally get that....no wait....I think I meant the opposite of that. Yeah.
Seriously, though, how do you communicate this to your standard, non-techie user?
Sandboxing wouldn't help here. The app looks like your bank app. So, it just collects the information from you.
If Microsoft had done this, everyone would be up in arms about how awful they were. Saying you just have to reinstall your OS is completely ridiculous. And, if it only applied to machines that dual-booted Linux, the conspiracy theorists would be claiming the MS did it on purpose to prevent people from dual booting. So, seriously, where's the outrage?
Seriously, these are the kinds of things that embarrass me when I talk with my foreign friends.
Didn't anyone tell them that this is a dangerous day for this?
Et tu, Bill?
Check your facts. The BSD personality runs in kernel-mode, not user-mode.
You are uninformed. While it would have been possible for Apple to take this approach (others have done it successfully), they decided not to. Instead, the BSD layer runs in kernel mode. When writing kernel modules for Mac OS X, you often end up using both the Mach and BSD apis.
I don't know where you get your information, but it is incorrect. When you develop kernel drivers for Mac OS X, you program to both the Mach and FreeBSD APIs. It does not just use FreeBSD utilities.
So, even though it uses Mach, you can't call it a Microkernel.
How do they plan to do this?
Do not perform minor optimizations without first: a) Determining there is a performance problem b) Profiling your code to determine what areas should be optimized.
This does not mean that you should choose naive algortithms for the problem at hand. Choosing the proper algorithm for the problem at hand is always important.
Hand-optimized code should be reserved for those times when you have profiled your code with reasonable inputs and have shown that the lack of clarity is compensated for by the increased performance.
The example you gave is a perfect example of a hand optimization that is completely worthless with today's compilers.
There are versions of NT that run on PowerPC. I believe that is what they were referring to.
And.....what's your point?
Looks fine on OS X.
The DDK (Driver Development Kit) contains a command-line verison of their C++ compiler. It also contains PREfast, which is a static code analysis tool, similar to Lint.
Usability doesn't require that you enable the system to do anything that it can't do today. All usability focuses on is making it easier / more intuitive to accomplish those same tasks.
You had me up 'til then.
Rather than speculating, just find out. Attach WinDbg to IE and check to see if it using the standard Winsock interface, or some other one. Be sure to make sure that all "reserved" parameters have their documented required value.
Because, luckily, I have RAID 57. So, I can handle it when 90% of my drives die.
NT is not written in C++, it is mostly C (with some assembly, obviously). It is also not a reimplementation of OS/2. As a matter of fact, it looks a helluva lot more like VMS than OS/2. Sure, the kernel and executive both handle objects, but not in the C++ sense. They are really just C structs that the kernel and executive keep track of and make sure don't leak (all get freed when an application terminates, if the app forgot to free them itself).
Since when does MSNBC let their readers post articles? I think you have been reading Slashdot too long.
Let's not jump the gun.