Actually, I think Android strikes an excellent middle ground between the iPhone (native only, a handful of models) and Windows Mobile 7 (Silverlight only, a plethora of models.)
For most apps (even some games) the Java toolkit is more than adequate, and functions very well across devices with minimal tweaking. If you need performance, but still want your app to work on a variety of phones, you need to do more legwork.
Apple doesn't actually have a solution to this problem, they're just protected because they only make a handful of devices.
Of course, when people talk about Android fragmentation, they don't know it, but they're really talking about the NDK. If you stick to Java your program is fairly easy to keep working across versions. If you use the NDK, it's graphics programming in the late '90s again with a ton of different GPUs and odd CPU quirks to deal with.
It's clear that they are going about it in completely the wrong manner though. WinMo 7 should have IE9 running on it. Currently, it has a weird IE6-7 hybrid POS. That's completely worthless, since the browser is the backbone of the system.
Windows CE isn't a joke. The joke is that anyone could use IE7 as a primary browser (on a smartphone no less.)
Windows Mobile will absolutely fail unless IE9 magically jumps into the ballpark of the modern browsers, and also magically works on mobile (why aren't they developing for WinCE and desktop simultaneously?)
The browser is the make-or-break feature, and since Microsoft has forbade native development on WinMo, I can't see them matching it. The mobile web is built for Webkit. They need to include Webkit.
Don't worry, if the government isn't given control it will stay where it is right now - with a handful of major telecommunications companies, all of whom want to get as much money as possible without doing any work, and if possible degrade service for increased money.
Most operating systems divorce the GUI from the bare-bones server stuff needed to run the OS. It drastically reduces complexity, which is always good from a security and speed standpoint. Interacting with the sysadmin is a very small part of the server's duties, so it should be a very small part of the server's code.
You should give a shit because these are students at a premiere finance college, and you got to see some data about what their tax returns looked like.
Don't most universities have a blanket provision that they may monitor any and all traffic over their network? I have to imagine that would cover them in this situation, though they would probably be in trouble if they were doing large-scale monitoring.
That said, the law actually requires schools to do monitoring of piracy.
The government's primary problems in this area are an excess of bureaucracy holding back stable software development. A very good first step is removing contractors from the equation, since that's an enormous layer of bureaucracy. We need to be funding real power-plays, not keeping the system as is.
"Government" has a terrible track record the same way "corporations" or "people" have a terrible track record. It only gets better if you look for improvements.
Have you used Android? I'd love to have it on a netbook. I'm currently in the market for one, and I'm debating between Android and UNR, and really Android seems to be winning out, though I would have to make sure I have root and can run Emacs.
That people are quite content to buy a device without Flash support. Now hurry up and build me a Android Netbook for $200. There's no reason for the delay.
The universe regresses infinitely towards smaller and smaller particles. Behind atoms we find electrons, behind electrons we find quarks. Probably we will find some issues within 246 more doubles. But who can say?
I'm not an iPhone developer, but I am a developer, but as I understand it you cannot write an iPhone app without using Apple's APIs. As such, the "openness" of C,C++, and Objective C is irrelevant because the meat of your code is going to involve API calls that will not work anywhere else.
Slashdot Mirror
Actually, I think Android strikes an excellent middle ground between the iPhone (native only, a handful of models) and Windows Mobile 7 (Silverlight only, a plethora of models.)
For most apps (even some games) the Java toolkit is more than adequate, and functions very well across devices with minimal tweaking. If you need performance, but still want your app to work on a variety of phones, you need to do more legwork.
Apple doesn't actually have a solution to this problem, they're just protected because they only make a handful of devices.
AOL was built on top of the Internet.
You can run C code with the NDK.
Of course, when people talk about Android fragmentation, they don't know it, but they're really talking about the NDK. If you stick to Java your program is fairly easy to keep working across versions. If you use the NDK, it's graphics programming in the late '90s again with a ton of different GPUs and odd CPU quirks to deal with.
The Pandora hardware is closed once you get to the level of individual chips, though it's not that big a deal for someone trying to build one.
With the nodes that insert a backdoor into the unix login program colored red.
It's clear that they are going about it in completely the wrong manner though. WinMo 7 should have IE9 running on it. Currently, it has a weird IE6-7 hybrid POS. That's completely worthless, since the browser is the backbone of the system.
Windows CE isn't a joke. The joke is that anyone could use IE7 as a primary browser (on a smartphone no less.)
Windows Mobile will absolutely fail unless IE9 magically jumps into the ballpark of the modern browsers, and also magically works on mobile (why aren't they developing for WinCE and desktop simultaneously?)
The browser is the make-or-break feature, and since Microsoft has forbade native development on WinMo, I can't see them matching it. The mobile web is built for Webkit. They need to include Webkit.
Don't worry, if the government isn't given control it will stay where it is right now - with a handful of major telecommunications companies, all of whom want to get as much money as possible without doing any work, and if possible degrade service for increased money.
Most operating systems divorce the GUI from the bare-bones server stuff needed to run the OS. It drastically reduces complexity, which is always good from a security and speed standpoint. Interacting with the sysadmin is a very small part of the server's duties, so it should be a very small part of the server's code.
You should give a shit because these are students at a premiere finance college, and you got to see some data about what their tax returns looked like.
Don't most universities have a blanket provision that they may monitor any and all traffic over their network? I have to imagine that would cover them in this situation, though they would probably be in trouble if they were doing large-scale monitoring.
That said, the law actually requires schools to do monitoring of piracy.
"Most servers" are increasingly virtualized. So those resources would be better used by another VM if the current isn't using them.
Removing it doesn't hurt. This is not an overzealous sysadmin problem, this is Microsoft sucking at modular design.
The government's primary problems in this area are an excess of bureaucracy holding back stable software development. A very good first step is removing contractors from the equation, since that's an enormous layer of bureaucracy. We need to be funding real power-plays, not keeping the system as is.
"Government" has a terrible track record the same way "corporations" or "people" have a terrible track record. It only gets better if you look for improvements.
Have you used Android? I'd love to have it on a netbook. I'm currently in the market for one, and I'm debating between Android and UNR, and really Android seems to be winning out, though I would have to make sure I have root and can run Emacs.
That people are quite content to buy a device without Flash support. Now hurry up and build me a Android Netbook for $200. There's no reason for the delay.
So essentially Microsoft is 10 years behind the curve? Why hasn't MS had forums? Why aren't they exploring crowdsourcing and open bug trackers?
No, Oracle is just trying to put it behind a paywall so you don't know what you're getting into until it's too late and you already own the hardware.
They're as small as we can get with present technology. Nothing is "truly elementary" in physics. It fits the model.
The universe regresses infinitely towards smaller and smaller particles. Behind atoms we find electrons, behind electrons we find quarks. Probably we will find some issues within 246 more doubles. But who can say?
There's plenty of money to be saving.
I'm not an iPhone developer, but I am a developer, but as I understand it you cannot write an iPhone app without using Apple's APIs. As such, the "openness" of C,C++, and Objective C is irrelevant because the meat of your code is going to involve API calls that will not work anywhere else.
False.
From the infamous section 3.3.1:
You cannot code in Objective C, C, or C++ unless you are using Apple's proprietary APIs.
Apple's "solution" doesn't scale. A mainstream vendor has to offer support to a variety of handsets.
Make it easier to understand and there will be less incentive to keep it concise.