What exactly don't you consider real about iOS 7's multitasking?
Can apps run in the background? Yes, although you are supposed to do so sparingly.
Some other requirement of which I'm unaware?
iPhones aren't likely to have 4GB any time soon because of cost and battery use. But iPads might.
It seems like some of the problem here is that Javascript is the Lingua Franca, and also that it has to use the web pages DOM. If the system were being designed from scratch, it seems unlikely this would be the choice.
Also, I have to assume that this project would have to also clone the various Core Foundation and Core Graphics and Core Text APIs as well, as very few real applications would use only the Objective-C wrappers for everything (I would think).
Well, that is surprisingly good then. I had a P4 3GHz running Linux which was costing me $12 a month in electricity at around 110W several years ago, and spinning its fans constantly.
I used to work near the Alewife T station which is at the extreme West end of Cambridge and it took about 37 minutes door to door if I avoided rush hour. It would be much longer if you were going to the MIT or Harvard areas. Another developer I knew back then took the train all the way from Exeter, NH but that was insane to me at 1.5 hrs each way.
Just to put some numbers on this, I live in Nashua, and our property tax rate is $21.49/$1000 of accessed value, a nearby MA town, Westford, for example has a rate of $16.10, so I'm paying around $1000 a year more in property tax then if I had the same accessed value house in Westford. Which is a lot, but a lot less than I was paying in MA income tax for the privileged of driving all the way to Cambridge every day.
I pay my property taxes every six months and they are pretty high but in the ballpark of nearby MA cities. It's not as if MA doesn't have property taxes in addition to high income and sales taxes.
Actually, when the TA union was voted in, it was with the promise that current TAs wouldn't have to pay union dues, while future TAs would have to pay dues. So the future TAs didn't get much choice in the matter.
As I understand it, after the State of Wisconsin banned automatic payroll deductions for public unions, the TAs at the Univ. of Wisconsin showed their appreciation for the union by pretty much uniformly not paying the now voluntary fees. They voted with their feet.
When I was a grad student, the union was responsible for forcing my department, Chemistry, to pay me less than they otherwise would out of the theory that TAs should be paid uniformly, no matter how worthless their undergraduate degree happened to be. Oh, and that TAs shouldn't get senior pay status without taking union approved 'diversity' training.
And we had health insurance before the union was certified.
The advantage for Apple was that the GPL was making them choose between integrating not only the compiler but also the syntax parser into Xcode and virally making Xcode GPL as well or continue having a substandard experience of calling gcc as a command line tool.
Xcode is much much better since ditching gcc as Apple now has the ability to modularize components and call methods directly. The code completion and static analysis are first rate, and they'd have gotten neither of those from gcc, not to mention taking full control over the direction of Objective-C with things like blocks, ARC and more types of literals.
One of the nice things about an onscreen keyboard is that they can be customized for the task at hand, thus the spreadsheet keyboard in Numbers for iPad. Now imagine a keyboard with C O H S P + - 1 2 3 4 5 6 and a subscript superscript lock button.
Even if Amazon could 'afford' it, they wouldn't. Amazon doesn't need Apple's service to make people realize you can buy e-books from Amazon. They've spent a lot of years getting people up to speed. A startup, on the other hand, selling (for instance) car service manuals on iPhone would find it worthwhile to pay Apple the 30% because otherwise nobody would have a clue that you had to go to such and such a website.
I'm guessing that most of the usage would be streaming encoded Dolby Digital which is typically 5.1. For instance, if I'm watching a recent movie on Netflix, it will likely have a Dolby Digital track. It's true that the original TOSLink (S/PIDF) spec only allowed for stereo PCM, but a hack was added a long time ago to allow DTS and Dolby Digital. Now, you can't get Dolby Master Audio or DTS HD over TOSLink, but that isn't a big deal when it comes to streaming video services, and will go a long way towards keeping an older receiver that doesn't have HDMI viable.
You could spend some money on an HDMI switch with TOSLink optical output to keep your receiver viable for a bit longer. I've bought one several years ago, and it's currently feeding my Logitech desktop surround system.
You print out a recovery number when you set it up. To change your password you need 2 of 3 things: the current password, a trusted device, or a recovery number. You are supposed to print it out, and hide it somewhere safe.
To the extent it's true that ordinary citizens commit felonies without intent daily, the fact that this guy had something to pin on him is not remarkable. Any of us could be arrested nominally for violating some law when the underlying motivation is to suppress speech the government doesn't like.
I find much of this somewhat debatable, but the one that I found most ill informed was the complaint about containers being immutable by default. You should really spend some time studying the ideas behind functional programming and functional programming languages (which Objective-C is not). Immutable containers mean fewer side affects, I can pass along an NSArray of NSStrings and I know that I can't accidently mutate them behind the scenes; a whole large class of possible hard to debug problems just goes away, and making concurrent code more reliable. Having containers be mutable by default is one of the greatest blunders in the design of such other frameworks as.Net, and I find it hard to believe any experienced programmer would believe otherwise. In the cases where you do need a mutable container, like when your are initially constructing one, just do it and then make an immutable copy using the copy method.
Because if you took your 24 inch monitor and made it 3840x2400 in the same size, the menus and buttons would be ridiculously small. What has to be done is that the onscreen elements have to be kept a constant physical size while making all the content and text have more detail. The need for the hardware is waiting for the major OS vendors to come up with a viable plan; I don't know what the situation is on Windows, but most Mac apps wouldn't be ready for Apple to set the onscreen resolution to 200% unless Apple uses the iOS trick of doubling the resolution and not telling the legacy apps the actual screen resolution.
Having spent the weekend having an impromptu Mythbusters marathon, I've learned that once bullets start to tumble their terminal velocity is between 60 and 100 mph which will really really hurt if it hit you on the head but is not going to penetrate and kill you. However, if it keeps on its ballistic trajectory (i.e. not straight up) they can kill at quite a distance just like the poster said. These are not mutually exclusive positions. At the most it means you can't kill yourself by shooting up in the air.
Slashdot Mirror
What exactly don't you consider real about iOS 7's multitasking? Can apps run in the background? Yes, although you are supposed to do so sparingly. Some other requirement of which I'm unaware? iPhones aren't likely to have 4GB any time soon because of cost and battery use. But iPads might.
Since it was just a proof of concept and was on the store for a few moments.
It seems like some of the problem here is that Javascript is the Lingua Franca, and also that it has to use the web pages DOM. If the system were being designed from scratch, it seems unlikely this would be the choice.
Also, I have to assume that this project would have to also clone the various Core Foundation and Core Graphics and Core Text APIs as well, as very few real applications would use only the Objective-C wrappers for everything (I would think).
My impression is that the company had some expensive labor contracts and bankruptcy was its answer to voiding them.
Well, that is surprisingly good then. I had a P4 3GHz running Linux which was costing me $12 a month in electricity at around 110W several years ago, and spinning its fans constantly.
You might want to do yourself a favor and attach a Kill-A-Watt to that P4 for a month and see what that cheap old hardware is costing you.
I used to work near the Alewife T station which is at the extreme West end of Cambridge and it took about 37 minutes door to door if I avoided rush hour. It would be much longer if you were going to the MIT or Harvard areas. Another developer I knew back then took the train all the way from Exeter, NH but that was insane to me at 1.5 hrs each way.
Just to put some numbers on this, I live in Nashua, and our property tax rate is $21.49/$1000 of accessed value, a nearby MA town, Westford, for example has a rate of $16.10, so I'm paying around $1000 a year more in property tax then if I had the same accessed value house in Westford. Which is a lot, but a lot less than I was paying in MA income tax for the privileged of driving all the way to Cambridge every day.
I pay my property taxes every six months and they are pretty high but in the ballpark of nearby MA cities. It's not as if MA doesn't have property taxes in addition to high income and sales taxes.
I used to work in MA and it was a wonderful day when I saw 0 under state income tax on my first NH pay stub.
Actually, when the TA union was voted in, it was with the promise that current TAs wouldn't have to pay union dues, while future TAs would have to pay dues. So the future TAs didn't get much choice in the matter. As I understand it, after the State of Wisconsin banned automatic payroll deductions for public unions, the TAs at the Univ. of Wisconsin showed their appreciation for the union by pretty much uniformly not paying the now voluntary fees. They voted with their feet.
When I was a grad student, the union was responsible for forcing my department, Chemistry, to pay me less than they otherwise would out of the theory that TAs should be paid uniformly, no matter how worthless their undergraduate degree happened to be. Oh, and that TAs shouldn't get senior pay status without taking union approved 'diversity' training. And we had health insurance before the union was certified.
Have you ever tried to set up the toolchain to compile FireFox? It's been a couple years, but it was ridiculously hard.
The advantage for Apple was that the GPL was making them choose between integrating not only the compiler but also the syntax parser into Xcode and virally making Xcode GPL as well or continue having a substandard experience of calling gcc as a command line tool. Xcode is much much better since ditching gcc as Apple now has the ability to modularize components and call methods directly. The code completion and static analysis are first rate, and they'd have gotten neither of those from gcc, not to mention taking full control over the direction of Objective-C with things like blocks, ARC and more types of literals.
One of the nice things about an onscreen keyboard is that they can be customized for the task at hand, thus the spreadsheet keyboard in Numbers for iPad. Now imagine a keyboard with C O H S P + - 1 2 3 4 5 6 and a subscript superscript lock button.
Even if Amazon could 'afford' it, they wouldn't. Amazon doesn't need Apple's service to make people realize you can buy e-books from Amazon. They've spent a lot of years getting people up to speed. A startup, on the other hand, selling (for instance) car service manuals on iPhone would find it worthwhile to pay Apple the 30% because otherwise nobody would have a clue that you had to go to such and such a website.
I'm guessing that most of the usage would be streaming encoded Dolby Digital which is typically 5.1. For instance, if I'm watching a recent movie on Netflix, it will likely have a Dolby Digital track. It's true that the original TOSLink (S/PIDF) spec only allowed for stereo PCM, but a hack was added a long time ago to allow DTS and Dolby Digital. Now, you can't get Dolby Master Audio or DTS HD over TOSLink, but that isn't a big deal when it comes to streaming video services, and will go a long way towards keeping an older receiver that doesn't have HDMI viable.
You could spend some money on an HDMI switch with TOSLink optical output to keep your receiver viable for a bit longer. I've bought one several years ago, and it's currently feeding my Logitech desktop surround system.
You print out a recovery number when you set it up. To change your password you need 2 of 3 things: the current password, a trusted device, or a recovery number. You are supposed to print it out, and hide it somewhere safe.
You do not understand the words the budget is not subject to filibuster.
To the extent it's true that ordinary citizens commit felonies without intent daily, the fact that this guy had something to pin on him is not remarkable. Any of us could be arrested nominally for violating some law when the underlying motivation is to suppress speech the government doesn't like.
I find much of this somewhat debatable, but the one that I found most ill informed was the complaint about containers being immutable by default. You should really spend some time studying the ideas behind functional programming and functional programming languages (which Objective-C is not). Immutable containers mean fewer side affects, I can pass along an NSArray of NSStrings and I know that I can't accidently mutate them behind the scenes; a whole large class of possible hard to debug problems just goes away, and making concurrent code more reliable. Having containers be mutable by default is one of the greatest blunders in the design of such other frameworks as .Net, and I find it hard to believe any experienced programmer would believe otherwise. In the cases where you do need a mutable container, like when your are initially constructing one, just do it and then make an immutable copy using the copy method.
Because if you took your 24 inch monitor and made it 3840x2400 in the same size, the menus and buttons would be ridiculously small. What has to be done is that the onscreen elements have to be kept a constant physical size while making all the content and text have more detail. The need for the hardware is waiting for the major OS vendors to come up with a viable plan; I don't know what the situation is on Windows, but most Mac apps wouldn't be ready for Apple to set the onscreen resolution to 200% unless Apple uses the iOS trick of doubling the resolution and not telling the legacy apps the actual screen resolution.
Having spent the weekend having an impromptu Mythbusters marathon, I've learned that once bullets start to tumble their terminal velocity is between 60 and 100 mph which will really really hurt if it hit you on the head but is not going to penetrate and kill you. However, if it keeps on its ballistic trajectory (i.e. not straight up) they can kill at quite a distance just like the poster said. These are not mutually exclusive positions. At the most it means you can't kill yourself by shooting up in the air.