Live data from Hacker News

Why we are suing Apple for better HTML5 support in iOS

nexedi.com

41–50 of 238 posts

Re: Why we are suing Apple for better HTML5 support in iOS

#41

Earlier quoted context omitted.

Why do they need to do that? Their platform, their rules. You don't want to play by Apple's rules then leave Apple's sandbox. This is absurd. You have no rights and no freedoms while using a vendor's software. They knew the restrictions going in. This is going to die quickly in the courts.

Do you feel the same way about Microsoft bundling Internet Explorer and trying to crush all competition in the browser market? Or do you only feel this way because it's Apple's sandbox? At least with Microsoft you _could_ install Netscape. What's your choice here? Buy an Android? I don't know you; this is a legitimate question. I don't actually know that I have an opinion on the underlying issue (I'm quite libertaria…

> Do you feel the same way about Microsoft bundling Internet Explorer and trying to crush all competition in the browser market?

Not a comparison. Windows was effectively a monopoly at the time where iOS is a strong but far from dominating force in mobile.

However if you want to make this comparison, honestly? Yes. I think the suit against Microsoft was justified simply because of how blatantly obvious their practices were designed to squeeze out other browser makers after the fact. However it's a different situation here: Safari has always been the defacto browser for iOS since the first publicly available version. There is no significant competition for Safari because there's no way to change iOS to utilize it in the same ways, and the Apple TOS for developers specifically states you cannot create apps that directly reproduce functionality of Apple's built-in applications.

Ergo, they are not decreasing the competition or being anti-market because there was no competition in the first place, and they made no secret of that.

Re: Why we are suing Apple for better HTML5 support in iOS

#42
post #10

Earlier quoted context omitted.

nobody stops you from using another ERP, they can't use another browser. They don't own the platform where the ERP runs, apple does.

Nobody is making them support the iPhone.

Back in the day, PageMaker ran only on Macs because only Macs had the underlying technology to support it. People bought Macs to run PageMaker. It was the "killer app".

If Nexedi's product was that good, they could convince people to buy Android devices.

Can a game maker sue Sony because it is extra work to port a game from XBox? Can they force Sony to support Kinect?

Re: Why we are suing Apple for better HTML5 support in iOS

#43
post #14
post #10

Earlier quoted context omitted.

Nobody is making them support the iPhone.

iPhone and Android ARE the market, not only OSes.

From the press release, I'm not sure anyone is stopping them from developing on iOS.

What they don't like is that they have to write some different code on iOS and that costs them money. IANAL but I'd be a bit surprised if "write once, run anywhere" is enshrined in French law.

Re: Why we are suing Apple for better HTML5 support in iOS

#44
post #16
post #4

Earlier quoted context omitted.

Hard to know. If a court decision forces them to allow other browser (engines) on iOS and people start moving away from Safari Apple may decide that it is in their best interest to make Safari the best web experience if they want to (re)attract those customers. See Microsoft and Edge.

Exactly. Competition drives innovation and progress.

And there is plenty of competition for the iPhone.

Re: Why we are suing Apple for better HTML5 support in iOS

#45
It's really hard to believe that Apple is holding back the 'mobile web' when it's shown time and time again that they have the best performing web platform in the market. It was true when iPhone was introduced in 2008, it was true in 2015[0] and it is still true now[1].

"In a nutshell, the fastest known Android device available today -- and there are millions of Android devices much slower than that out there -- performs 5× slower than a new iPhone 6s, and a little worse than a 2012 era iPhone 5 in Ember. How depressing."

[0]: https://meta.discourse.org/t/the-state-of-javascript-on-andr... [1]: https://twitter.com/CraftyDeano/status/779461778677895169

Re: Why we are suing Apple for better HTML5 support in iOS

#46
Looks like a pr stunt.

But, here is another point of view (perhaps it can help, i'd love to see html 5 support improve on iOS).

Internet Access is a "human right" and according to the United Nations ( https://www.article19.org/data/files/Internet_Statement_Adop... ) , they condemn countries that intentionally take away or disrupt its citizens’ internet access.

Perhaps by not allowing "basic internet access" ( html 5 is part of the web), Apple is a distrupter of a basic human right.

The platform, where we could least of all platforms, use our basic human right to browse the web is iOS. So Apple is, in it's own way, a company that blocks a basic human right. And the block it because of own financial gain ( using the app store instead of the browser earns them money)

Re: Why we are suing Apple for better HTML5 support in iOS

#47
post #22
post #4

Earlier quoted context omitted.

Hard to know. If a court decision forces them to allow other browser (engines) on iOS and people start moving away from Safari Apple may decide that it is in their best interest to make Safari the best web experience if they want to (re)attract those customers. See Microsoft and Edge.

Right, but I know Apple has argued at W3C against certain web standards and for others on the basis of security in a mobile context, power efficiency and functional alignment with touch UI behaviours. We don't know why Apple has chosen to implement some features (so far) and not others. Do you really want French courts deciding those kinds of technical decisions or taking those decisions away from mobile platform ven…

Sure, that's the point of the standards process. Apple made their argument as a full member of the W3C and other standards committees. If they weren't convincing enough and the committee choose to go another way with the standard, then it's Apple's responsibility to accept that decision. After all, if the decision had gone their way, they'd expect the other vendors to adhere to it.

Re: Why we are suing Apple for better HTML5 support in iOS

#48

It's really hard to believe that Apple is holding back the 'mobile web' when it's shown time and time again that they have the best performing web platform in the market. It was true when iPhone was introduced in 2008, it was true in 2015[0] and it is still true now[1]. "In a nutshell, the fastest known Android device available today -- and there are millions of Android devices much slower than that out there -- perf…

Perhaps they should do more about HTML 5 features ( which is holding back the mobile web) instead of js execution.

This just means they can do it, but they won't due to own personal gains

Re: Why we are suing Apple for better HTML5 support in iOS

#49

Looks like a pr stunt. But, here is another point of view (perhaps it can help, i'd love to see html 5 support improve on iOS). Internet Access is a "human right" and according to the United Nations ( https://www.article19.org/data/files/Internet_Statement_Adop... ) , they condemn countries that intentionally take away or disrupt its citizens’ internet access. Perhaps by not allowing "basic internet access" ( html 5…

I really doubt you could pass HTML5 compatibility as a "basic internet access".

Re: Why we are suing Apple for better HTML5 support in iOS

#50

It's really hard to believe that Apple is holding back the 'mobile web' when it's shown time and time again that they have the best performing web platform in the market. It was true when iPhone was introduced in 2008, it was true in 2015[0] and it is still true now[1]. "In a nutshell, the fastest known Android device available today -- and there are millions of Android devices much slower than that out there -- perf…

Perhaps they should do more about HTML 5 features ( which is holding back the mobile web) instead of js execution. This just means they can do it, but they won't due to own personal gains

Or at least allow other browsers to compete on the platform.
Post reply on HN