If no is no longer a viable answer, the user who insists on a different answer should be ready to be held legally responsible for every single security breach that follows. But of course the shits want their toys and none of the responsibility. They never left kindergarten.
You're incredibly incompetent with respect to installing software. Gettting Windows up and running has been a breeze since approximately the Windows 3.1 days. Perhaps the most difficult part is installing on a hard drive whose controller is not supported by the install media, and that's not something unique to Windows.
Try doing the same on a PC running a general-purpose OS. Just because you don't like to work on that level doesn't mean there's anything wrong with it. You just hate MS because you think it's cool to hate. It's not. Go away and die.
Even if a conviction is made, the mugshots should not be publicized. Incarceration in the US is about punishment. After the term has been served, there should be no further punishment.
Sex offender lists are an abomination and should be illegal. Once a prison term has been served, the public(ly available) record should be expunged.
Not so. Simply storing the century in another byte would have mitigated any y2k issues. Of course, that would only work until the year 25500, but I think we'd be OK in general.
As proof that C is perfectly appropriate for OS kernels, one simply has to look at the most common kernels. Name one that is written in a language other than C. Linux, Windows, Mach, *BSD... All in C. Even OpenBSD is in C, which one would think an odd choice considering the stated goal of OpenBSD.
If anything, one might argue that an OS kernel is the only appropriate place for C.
I believe that the GP was referring to Nil, not nil. Nil (with the uppercase N) is an object in Objective C. NULL/nil cannot, in fact, be added to standard collection classes, such as NSArray to NSDictionary (as a key), but Nil can be.
That is not true. In Windows 95 through Windows ME, there was a 64K limit because GDI was still 16 bits, and the text control used by Notepad was (and is) implemented on top of GDI. Windows NT (all the way back to 3.1) never had this limit. By the time Windows machines had gigabytes of RAM, Windows 2000 and Windows XP were the dominant versions in use.
To be fair, you're 100% wrong. I have two apps, one of which is just a better version of the other. It is a niche program, intended for Orthodox Jews. In the nearly 3 years I've been in the App Store, I've made 6 times what I've spent in subscription fees. I've made enough to pay for the iPod Touch and iPad that I would have bought anyway. In fact, I bought the iPod Touch before I had any idea I'd be writing any apps.
I am not making a living by any stretch, but as a hobby, it more than pays for itself.
You've worked in places with crappy admins. The company where I work had one of the earliest AD installations (going back to early 2000s) and hasn't had a day of downtime. Never seen malware be a problem here, and once in a while an Exchange server goes down, but it's rare and will only affect a portion of users. We've had our DB (Oracle on Linux) server go down more often than Exchange. And the SAN product from IBM used to fall over once or twice a week.
No organization of any significant size allows users to update apps from the web. Whether the app is in a distro's repo or not is mostly irrelevant, as update mechanisms exist for Windows which give basically the same functionality.
And no admin with a clue is constantly reimaging or futzing with anything. But then, I've only worked in places with competent admins and image builders.
You are an idiot. Complete, total, and probably uncorrectable.
If someone saves a $100 on one item, they have a few choices. Either they purchase some other item, they save the money or they pay off debt. If they purchase something else, the money has moved. If they save it, they have still benefited by whatever method they saved the $100. If they pay off debt, they are now free to spend the next $100 that comes in, because they owe less, or maybe nothing at all. That the receiver of that debt payment may choose to sit on it is irrelevant. It's no different, economically, than if the $100 had simply been saved.
In short, your suggestion that paying off debt is bad, economically, is completely wrong.
Basically you're saying it's better to kill 10s of thousands every single year than to maybe, if things go more horribly wrong than any engineer could imagine, kill a few hundred once in 40 years?
Your view of the world is so warped that you quite likely can see your ass without bending over.
The point of a VM is that only the VM changes to accommodate the physical architecture. The thousands of apps already available would not have to be recompiled.
I know reading is hard for you, probably because your teachers were too friendly to point out your inability, but the article answers your second question.
As an iOS developer, I can tell you that document (file) handling on iOS sucks. Unconditionally sucks. There are zero upsides to it at all. Well, no upsides that can not be mimicked some other way that doesn't leave it sucking. What Xigxag wrote is entirely correct. Files only live within the confines of a single app. With very exceptions (and all them Apple-provided), one app can not see another's files.
(It happens to be that apps can see video that is available to Apple's player, so it may be that his example is not the best choice. Still, pick any other document type (besides photos and maybe audio) and you have a valid complaint.)
Slashdot Mirror
If no is no longer a viable answer, the user who insists on a different answer should be ready to be held legally responsible for every single security breach that follows. But of course the shits want their toys and none of the responsibility. They never left kindergarten.
I think most people like you are snobs, bigots and assholes.
It's much more likely that MS is targeting programmers who would like to dabble in electronics and not the other way around.
You're incredibly incompetent with respect to installing software. Gettting Windows up and running has been a breeze since approximately the Windows 3.1 days. Perhaps the most difficult part is installing on a hard drive whose controller is not supported by the install media, and that's not something unique to Windows.
Try doing the same on a PC running a general-purpose OS. Just because you don't like to work on that level doesn't mean there's anything wrong with it. You just hate MS because you think it's cool to hate. It's not. Go away and die.
Since when can't you double-click the upper-left corner to close FF? Works fine on FF5 for me.
Even if a conviction is made, the mugshots should not be publicized. Incarceration in the US is about punishment. After the term has been served, there should be no further punishment.
Sex offender lists are an abomination and should be illegal. Once a prison term has been served, the public(ly available) record should be expunged.
It's used by services that are installed by default.
Not so. Simply storing the century in another byte would have mitigated any y2k issues. Of course, that would only work until the year 25500, but I think we'd be OK in general.
As proof that C is perfectly appropriate for OS kernels, one simply has to look at the most common kernels. Name one that is written in a language other than C. Linux, Windows, Mach, *BSD... All in C. Even OpenBSD is in C, which one would think an odd choice considering the stated goal of OpenBSD.
If anything, one might argue that an OS kernel is the only appropriate place for C.
I believe that the GP was referring to Nil, not nil. Nil (with the uppercase N) is an object in Objective C. NULL/nil cannot, in fact, be added to standard collection classes, such as NSArray to NSDictionary (as a key), but Nil can be.
That is not true. In Windows 95 through Windows ME, there was a 64K limit because GDI was still 16 bits, and the text control used by Notepad was (and is) implemented on top of GDI. Windows NT (all the way back to 3.1) never had this limit. By the time Windows machines had gigabytes of RAM, Windows 2000 and Windows XP were the dominant versions in use.
To be fair, you're 100% wrong. I have two apps, one of which is just a better version of the other. It is a niche program, intended for Orthodox Jews. In the nearly 3 years I've been in the App Store, I've made 6 times what I've spent in subscription fees. I've made enough to pay for the iPod Touch and iPad that I would have bought anyway. In fact, I bought the iPod Touch before I had any idea I'd be writing any apps.
I am not making a living by any stretch, but as a hobby, it more than pays for itself.
Yucca Mountain would be a strange location for an undersea sanctuary.
You've worked in places with crappy admins. The company where I work had one of the earliest AD installations (going back to early 2000s) and hasn't had a day of downtime. Never seen malware be a problem here, and once in a while an Exchange server goes down, but it's rare and will only affect a portion of users. We've had our DB (Oracle on Linux) server go down more often than Exchange. And the SAN product from IBM used to fall over once or twice a week.
No organization of any significant size allows users to update apps from the web. Whether the app is in a distro's repo or not is mostly irrelevant, as update mechanisms exist for Windows which give basically the same functionality.
And no admin with a clue is constantly reimaging or futzing with anything. But then, I've only worked in places with competent admins and image builders.
You are an idiot. Complete, total, and probably uncorrectable.
If someone saves a $100 on one item, they have a few choices. Either they purchase some other item, they save the money or they pay off debt. If they purchase something else, the money has moved. If they save it, they have still benefited by whatever method they saved the $100. If they pay off debt, they are now free to spend the next $100 that comes in, because they owe less, or maybe nothing at all. That the receiver of that debt payment may choose to sit on it is irrelevant. It's no different, economically, than if the $100 had simply been saved.
In short, your suggestion that paying off debt is bad, economically, is completely wrong.
The number of people that hate flash because it's proprietary would barely fill a full length school bus.
Basically you're saying it's better to kill 10s of thousands every single year than to maybe, if things go more horribly wrong than any engineer could imagine, kill a few hundred once in 40 years?
Your view of the world is so warped that you quite likely can see your ass without bending over.
Your post has no connection to its parent. In fact, I can't figure out what your point is at all, much less how it might be related.
The point of a VM is that only the VM changes to accommodate the physical architecture. The thousands of apps already available would not have to be recompiled.
There are many court decisions which demonstrate that minors are not people in the US.
I know reading is hard for you, probably because your teachers were too friendly to point out your inability, but the article answers your second question.
If by "most of the rest of the world" you mean Mac OS, VMS, or zOS (or whatever it was called back then), the answer would be no.
As an iOS developer, I can tell you that document (file) handling on iOS sucks. Unconditionally sucks. There are zero upsides to it at all. Well, no upsides that can not be mimicked some other way that doesn't leave it sucking. What Xigxag wrote is entirely correct. Files only live within the confines of a single app. With very exceptions (and all them Apple-provided), one app can not see another's files.
(It happens to be that apps can see video that is available to Apple's player, so it may be that his example is not the best choice. Still, pick any other document type (besides photos and maybe audio) and you have a valid complaint.)
iOS 5.
And yes, it sucks that it's taken this long to get it, but at least it's correctable in software.