On Wednesday, 26 September 2012 at 22:23:00 UTC, Nick Sabalausky
wrote:
On Wed, 26 Sep 2012 10:37:10 -0700
"H. S. Teoh" <hst...@quickfur.ath.cx> wrote:
wide images get clipped with no way to unclip them when using
the
mobile stylesheet (probably the same bug you describe above),
etc..
And Apple has the audacity of forcefully banning all other
browsers
from the app store, for the simple reason that they are
superior
browsers, and oh no, we simply can't allow customers to have a
superior experience!
I thought Chrome was available for iOS?
But if what you say is true, then that's interesting to compare
to
"evil M$":
Microsoft: Installs their browser by default. Allows any other
browser
to be installed and set as default. People are pissed. Gates is
demonized. DOJ sues.
Apple: Installs their browser by default. Bans other browsers
entirely. Everybody's happy and praises Jobs as a great
designer and
savvy businessman. No lawsuit.
You are forbidden to use other rendering engines. So what
browsers for iOS do, is to have their own network stack, but the
rendering has to go via UIWebView.
Safari has special rights, being the only application allowed to
generate native code via JIT.
For me this makes it rather pointless to install any other
browser.
Many young geeks only know Apple from Mac OS X onwards, but the
new secretive Apple is actually the old Apple.
Apple used to have it own standards for everything, NuBus,
AppleTalk, QuickDraw 3D, QT, etc. APIs were a mix of C and Pascal
code, without any proper POSIX support.
Apple only became a bit more friendly to open source, after the
NeXTStep guys got on board. Specially, because they needed a
quick way out of two failed OS projects.
Now that Apple hardware sells like hot pancakes in many
countries, they are back to their old self.
--
Paulo
