The American system dictates and shapes that "successful" politicians and executives don't go to school, esp to learn math.
Probably explains why they continuously defund public education over military spending.
except it's actually lasseize-faire monopoly/duopoly subsidized by the FCC. By allowing different regions of the world to exist on different frequencies, they're effectively region-locking the hardware by default.
No hardware manufacturer has any incentive to provide any more support than the minimal required by regulation and necessity. Therefore, the USA is still a black-hole for any of the released devices because the frequencies are one-offs for anybody else in the world. Effective competition therefore cannot exist in such an environment.
Allowing this situation to continue into LTE is continuing the subsidizing of device lock-out monopolies.
DMCA:
http://www.wired.com/threatlevel/2010/07/feds-ok-iphone-jailbreaking/
Magnuson-Moss Warranty Act:
http://en.wikipedia.org/wiki/Magnuson-Moss_Warranty_Act
specifically:
The federal minimum standards for full warranties are waived if the warrantor can show that the problem associated with a warranted consumer product was caused by damage while in the possession of the consumer, or by unreasonable use, including a failure to provide reasonable and necessary maintenance.
He should have let the economy totally fail as quickly and as early as possible. When somebody "dies"/fails, people will irrationally martyr and brandy that for years and years after, and then get motivated to actually do something about it. USA isn't a rational country, so saving it from itself was the worse thing that could've been done. You can't fix things until the country DEEPLY hangs itself first, period.
It's just like the Y2K bug. Soften the impact and then people/history will say you were lying how big of a deal it was.
High-flying intellectual solutions is above the USA's public's ability to understand and act upon.
Just like no real Christians are Republicans.
Then you should be programming in inline C++ templates. It gives you all the advantages of a near-metal-C-like programming with the harness/automation/coverage of an object-oriented language.
This is why WTL is superior over MFC in speed and size for the same API, as well as Boost, and why I write everything I can in meta-template programming and optimize the syntax to generate optimal assembly.
I've done a fixed class as so (and OpenGL/ES wrappers) and it runs optimally across x86, ARM, MIPS; exactly as I would have hand-coded it; and I get all the automatic optimization from being at the level where an optimizer also exists.
They are outed, and so get fixed even faster.
Good luck with the iOS/Wimpy7s bugs that are never announced/found due to this type of peer-review, and so there's no priority to fix them.
Most likely OO in MSWindows isn't compiled with a recent version of MSVC or such that deals efficiently with C++ code. MSVC is not exactly a premier compiler nor does it ever try to be. Also OO probably uses dlls that aren't being used by the rest of the OS so there's a lot of loading and linker resolution lag involved.
On the other hand in Linux, generally any version of gcc > 4.x has really good C++ code generation (such as -fvisibility=hidden), gcc > 4.x is pretty old, and most of the
MS isn't about market-leading innovation. It's all about market-trailing lock-in.. ha ha ha ha.
Seems the only way they can sell Silverlight now is to push it as the framework for Wimpy7s.
I find my Fridays filled with new Cartoon Network content now, which has just as good SciFi storylines and many more series.
Starting with Batman Brave and the Bold, then the last good SyFy show Sanctuary, on to Ben 10: Ultimate Alien, Sym-Bionic Titan, and finally Generator Rex.
Since it's all TiVo, there's still plenty of time to get out, or just catch up on something else.
Don't forget Qt begging on Twitter for examples of mobile Qt apps.
Summary is Nokia/Qt is Beta SP. It doesn't matter it's better tech if the majority doesn't buy into it.
Plugin-rebuttal.
Wow, programming strategies based on a strawman (re Taco Bell) argument. Has "win" written all over it.
MeeGo will simply fail because of the arrogance of the Qt developers.
Technical reasons:
o one can NOT ask them on blogs, Jira, nor Twitter why Qt has such an uncompetitive and huge footprint in memory and storage for embedded, besides normal desktop
o they don't care their software rendering path (new in 4.x and influenced by AGG) is also bloated in memory/storage and hurts them in the long-run for OGLES acceleration
o they have 3-4 renderer paths inside Qt which all sit there taking RSS in the
o pointing out footprint issues AFTER using their qconfig and lots of work to already optimize/slash footprint, but devs will say you're an idiot and use qconfig.
o one can NOT file a bugs in their Jira that Qt Creator takes 2x more memory than the MSVC equivalent (for even Qt code itself) without getting it shut down as invalid
o if you submitted patches to switch their naive optimizations to tune toward more footprint-savings (because -O2 creates uselessly-bloated libs that aren't any benchmarked faster on mobile) they will "take it under consideration" and then ignore it
o if you submitted patches into their Jira and are not a primary partner like Nvidia, they will nitpick the patch over tabbing and spacing (because it also fixes previous violations of their Style standards), ignore it the patch, and let it die on the vine
Qt is simply not tuned for mobiles. Their internal forking of it as "Mobility" subversions helps themselves even less.
You're slamming it wrong?
The difference between reality and unreality is that reality has so little to recommend it. -- Allan Sherman
