News for hackers. Stuff that matters.
Re:Firefox’s Fight for the Future of the Web by chappi42 on Sunday November 17, 2019 @06:16AM (#21557446)
The article once more reiterates the fact that Apple doesn't allow other browser engines. You cannot even fight, there is no future ;-) on iOS.
Re:Firefox’s Fight for the Future of the Web by ken on Sunday November 17, 2019 @11:39AM (#21558647)
That's a convenient excuse on iOS, but Firefox is doing poorly on macOS, too, where no such restriction exists. According to the first statistics I found, Firefox is only about half as popular on the Mac as it in on Windows -- and it's still under 10% there, too.

Privacy-compromising systems aren't winning today because people seek out systems that compromise their privacy. They're winning because these companies focused on making the user interface good. Firefox will win big again when they stop talking about privacy and start making a UI that isn't lousy.

True, Apple is talking about privacy a lot these days, but they've been focusing on UX first for decades. You can't start with "here is an abstract principle that's good for you, and you should use our systems because of it". The Free Software Foundation tried that for years. It doesn't work.

Privacy is important, but it's a feature, not a product. You still need to have a great product.

Re:Firefox’s Fight for the Future of the Web by MaxBarraclough on Sunday November 17, 2019 @12:16PM (#21558822)
> Privacy is important, but it's a feature, not a product. You still need to have a great product.

Do you consider Firefox to be a less-than-great product?

I use it as my main browser, from Windows 10. No complaints. I don't experience performance issues or UI issues. Chrome and Firefox are both solid browsers, on Windows at least.

Perhaps Firefox for Mac is a weaker product, and loses to Safari 'fair and square' on quality grounds?

Re:Firefox’s Fight for the Future of the Web by alwillis on Sunday November 17, 2019 @12:44PM (#21558950)
>Perhaps Firefox for Mac is a weaker product, and loses to Safari 'fair and square' on quality grounds?

The current version of Firefox on macOS is a vast improvement over what Mozilla was shipping 6-12 months ago.

However, it still requires more RAM, doesn’t render as quickly and consumes more power than Safari, so there’s that. Also, Safari implemented anti-tracking features before Firefox did.

Re:Firefox’s Fight for the Future of the Web by ripa on Sunday November 17, 2019 @12:38PM (#21558920)
Firefox for Mac has been more or less unusable up until the most recent release where they actually started using the Core Animation libraries in macOS. Now it won’t drain all the battery in no time, and it’s actually quite snappy. I’ve tried to run Firefox so many times in the past, but eventually always go back to Safari because it’s more native, fast and unobtrusive.
Re:Firefox’s Fight for the Future of the Web by catalogia on Sunday November 17, 2019 @02:56PM (#21559711)
> Firefox for Mac has been more or less unusable up until the most recent release

This is a gross exaggeration. I've been using firefox on MacOS for 3 years and it's worked fine the entire time.

Re:Firefox’s Fight for the Future of the Web by GeekyBear on Sunday November 17, 2019 @05:57PM (#21560587)
The issue has been the power draw and heat on newer MacBooks with a Retina display.

Older Firefox versions are redrawing the entire window even if only a tiny portion of the window was changing.

With advent of high resolution windows, the amount of work needed to redraw the whole window for every frame became significant.

The last version of Firefox moved to breaking the window into large tiles and only redrawing the tiles that have changed.

This is still less optimized than Safari (which uses Core Animation to only redraw the items on the page that are changing) but it is still a large improvement over prior versions of Firefox if you have a high resolution display.

Re:Firefox’s Fight for the Future of the Web by brlewis on Monday November 18, 2019 @08:15AM (#21564014)
I've been using Firefox on a newer macbook with retina display for the past 2 years or so. I haven't experienced "more or less unusable" in that time.
Re:Firefox’s Fight for the Future of the Web by wtetzner on Sunday November 17, 2019 @04:56PM (#21560292)
I’ve been using Firefox on MacBook Pros for the last 9 years, and it’s worked fine.
Re:Firefox’s Fight for the Future of the Web by Royalaid on Sunday November 17, 2019 @01:34PM (#21559239)
I will say that the latest changes on nightly really feel like it is close enough to other browser to be a decent replacement
Re:Firefox’s Fight for the Future of the Web by ken on Sunday November 17, 2019 @01:12PM (#21559114)
Yes, Firefox on the Mac is absolutely a less-than-great product, to put it mildly. That's why I called its UI "lousy".
Re:Firefox’s Fight for the Future of the Web by alwillis on Sunday November 17, 2019 @12:38PM (#21558922)
Actually, Apple is giving privacy the product treatment: https://www.apple.com/privacy/
Re:Firefox’s Fight for the Future of the Web by throwGuardian on Sunday November 17, 2019 @12:51PM (#21558990)
Why allow competition when they can simply claim to productize.
Re:Firefox’s Fight for the Future of the Web by alwillis on Sunday November 17, 2019 @01:34PM (#21559242)
There are literally hundreds of apps on the App Store that compete with Apple’s own offerings, especially email clients, calendaring, productivity, etc.

So clearly it’s not about competition. Disney+ is being heavily promoted on the App Store, which is direct competitor to Apple’s TV+.

We’ve seen 3rd parties like Google and Facebook subvert iOS security before; if Mozilla gets low-level access, then so does Google and they can’t be trusted.

Re:Firefox’s Fight for the Future of the Web by throwGuardian on Sunday November 17, 2019 @02:25PM (#21559501)
There are literally zero browser engines allowed on iOS, other than Safari/webkit, with a purposefully depleted feature set, to force developers and users to the app store.

It is astounding that overzealous Apple employees and fan boys will employ circuitous mental gymnastics to substantiate Apple policies, instead of simply allowing an open-market to thrive on iOS. It's as if open markets where consumers are allowed to choose works against Apple

Re:Firefox’s Fight for the Future of the Web by millstone on Sunday November 17, 2019 @02:52PM (#21559672)
What is this hope for a "thriving open market?" On Android, Chrome/Chromium engine has more than 99.5% marketshare.

Consumer choice is a red herring. So for that matter is Firefox, which Google has stomped out on Android. Apple's policy is 100% aimed at preventing Google from controlling the future of iOS.

Re:Firefox’s Fight for the Future of the Web by alwillis on Sunday November 17, 2019 @03:29PM (#21559887)
Let’s not forget that Google had to pay the largest FTC fine for intentionally bypassing the security features on iOS; no wonder Apple doesn't allow low-level access to the operating system: https://www.ftc.gov/news-events/press-releases/2012/08/googl...
Re:Firefox’s Fight for the Future of the Web by brlewis on Monday November 18, 2019 @08:26AM (#21564079)
Consumer choice means that tomorrow if Android Chrome does something really unpopular, people can switch to Android Firefox. It is not a red herring.

Yes, giving users choice does mean loosening your control of your platform. I don't believe Apple thinks consumer choice would cause Google to control the future of iOS.

Re:Firefox’s Fight for the Future of the Web by alwillis on Sunday November 17, 2019 @03:24PM (#21559866)
>There are literally zero browser engines allowed on iOS, other than Safari/webkit, with a purposefully depleted feature set, to force developers and users to the app store.

Apple is clearly moving towards a more secure set of operating systems and that starts by reducing the attack surface.

On macOS, Apple is deprecating kernel extensions; the boot partition on macOS Catalina is read-only so that it can’t be modified by malicious software: https://wccftech.com/macos-catalina-runs-on-dedicated-read-o...

Even Safari on iOS doesn’t support browser extensions.

>instead of simply allowing an open-market to thrive on iOS.

The App Store paid developers $34 billion in 2018; I would say the market is thriving: https://fortune.com/2019/01/28/apple-app-store-developer-ear...

>Safari/webkit, with a purposefully depleted feature set

Just checked html5test.com from my iPhone 7 running iOS 13.2.2; Safari scores 463 and Firefox 48 mobile scored 468 out of 555 points. And this is without enabling a bunch of experimental work-in-progress features: https://imgur.com/a/Y5NHwct

So there's no meaningful difference in capability of these browsers when it comes to features.

Of course, Safari is faster, requires less RAM and consumes less power, which should count for something on a mobile device.

Re:Firefox’s Fight for the Future of the Web by throwGuardian on Sunday November 17, 2019 @04:11PM (#21560067)
This response literally proves fanboys and employees will offer circuitous logic to substantiate Apple. iOS Safari W3C non-compliance is well known, a little googling will lay out the (intentionally) missing features.

You go to lengths to defend Apple, but do not have the guts to let the consumer pick a Google/Mozilla alternative engine. What is Apple so scared of, if not a level playing field.

This is the same company that retroactively modified it's store policies to substantiate booting steam off the app store. Courage in the face of competition, not!!

Re:Firefox’s Fight for the Future of the Web by Roboprog on Sunday November 17, 2019 @05:32PM (#21560458)
I was a bit surprised to learn a year or two ago that the browser makers have pretty much divorced W3C:

https://en.m.wikipedia.org/wiki/WHATWG

Re:Firefox’s Fight for the Future of the Web by alwillis on Sunday November 17, 2019 @04:39PM (#21560209)
>iOS Safari W3C non-compliance is well known, a little googling will lay out the (intentionally) missing features.

The illogic here is a little scary: Firefox and Safari on iOS basically have the same level of web standards compliance according to html5test.com, yet one is intentionally not implementing features?

No fanboyism; just the facts.

Re:Firefox’s Fight for the Future of the Web by detaro on Sunday November 17, 2019 @04:44PM (#21560237)
It's not that surprisingly that the one making the decisions about the browser engine is blamed, not the one forced to use the browser engine instead of their own, is it?
Re:Firefox’s Fight for the Future of the Web by alwillis on Sunday November 17, 2019 @05:46PM (#21560533)
To be clear, the html5test.com numbers for Firefox are for Firefox on Android.
Re:Firefox’s Fight for the Future of the Web by brlewis on Monday November 18, 2019 @08:44AM (#21564220)
Quote:

  YOUR BROWSER SCORES
         491
  OUT OF 555 POINTS
  You are using Firefox Mobile 68.0 on Android 8.1.0
Not 468.
Re:Firefox’s Fight for the Future of the Web by alwillis on Monday November 18, 2019 @09:52AM (#21564709)
The numbers I quoted were from Firefox 48, not 68.
Re:Firefox’s Fight for the Future of the Web by TheCoelacanth on Monday November 18, 2019 @12:44PM (#21566328)
> >instead of simply allowing an open-market to thrive on iOS.

> The App Store paid developers $34 billion in 2018; I would say the market is thriving: https://fortune.com/2019/01/28/apple-app-store-developer-ear....

They said open market. Apple's closed market is thriving, but the open market doesn't exist on iOS.

Re:Firefox’s Fight for the Future of the Web by greggman2 on Sunday November 17, 2019 @04:51PM (#21560262)
browser extesions are a privacy feature. my browsing is much more private on Firefox with ublock origin then on no extension safari.

As for Safari using less power and ram on mobile there is no evidence that Firefox would uae more of either since Apple doesn't allow it to run. As far as we know if other browsers were allowed to run some might compete on power and ram.

As for security, chrome on desktop has a superior track record. The CVE list proves this, so by denying competition Apple denies users more secure browsers.

Re:Firefox’s Fight for the Future of the Web by alwillis on Sunday November 17, 2019 @06:02PM (#21560630)
> As for Safari using less power and ram on mobile there is no evidence that Firefox would uae more of either since Apple doesn't allow it to run. As far as we know if other browsers were allowed to run some might compete on power and ram.

Firefox is slower, requires more RAM and uses more power on macOS now; it’s highly unlikely that essentially the same engine running on iOS would run significantly differently.

Of the mainstream browsers on macOS, Firefox has always been the slowest.

Re:Firefox’s Fight for the Future of the Web by alwillis on Sunday November 17, 2019 @07:36PM (#21561068)
>browser extesions are a privacy feature. my browsing is much more private on Firefox with ublock origin then on no extension safari. All things being equal, you shouldn't have to rely on extensions in 2019 to protect your privacy.

The goal is to preserve privacy by default--no extensions required. The vast number of users don't install them or wouldn't know which ones to install.

Brave is secure out of the box and doesn't require extensions to protect your privacy: https://brave.com/features/

Safari also doesn't require extensions to protect your privacy: WebKit Tracking Prevention Policy—https://webkit.org/tracking-prevention-policy/

Apple first shipped Intelligent Tracking Prevention in June 2017, long before Firefox or any other browser had anything similar: https://webkit.org/blog/7675/intelligent-tracking-prevention...

Re:Firefox’s Fight for the Future of the Web by greggman2 on Sunday November 17, 2019 @10:57PM (#21561776)
I know this false based on all the ads I see in webpages in Safari that I don't see when in Firefox with UBlock Origin. Every ad I see was served by the ad company. Safari might be blocking cookies but it's not letting me block the ads which is all that's really needed to track.
Re:Firefox’s Fight for the Future of the Web by alwillis on Monday November 18, 2019 @01:20AM (#21562308)
Safari doesn’t block ads currently; that’s true.

Safari’s Intelligent Tracking Prevention stops the cross-site tracking, fingerprinting, etc. by ad companies.

The ability to block content is built-in to macOS and iOS for 3rd parties to use.

Re:Firefox’s Fight for the Future of the Web by alwillis on Sunday November 17, 2019 @07:28PM (#21561040)
Regarding performance, here’s a detailed article on benchmarks for the various Javascript engines; Firefox is the slowest: https://webkit.org/blog/8685/introducing-the-jetstream-2-ben...
Re:Firefox’s Fight for the Future of the Web by ragequitta on Sunday November 17, 2019 @12:14PM (#21558814)
I'm trying to think of a UI difference in chrome or safari that is meaningful, can't come up with one. Can you elaborate?
Re:Firefox’s Fight for the Future of the Web by ken on Sunday November 17, 2019 @02:18PM (#21559469)
You mean UI issues with Firefox, compared to Safari? Gosh, where to start?

- Standard keyboard shortcuts for text editing still don't work. That alone is a dealbreaker for me.

- The toolbar(s) don't look or work like standard toolbars. The standard toolbar editor is missing, too.

- Tabs don't look or act right, either. They're actually styled like Windows XP tabs.

- The scroll bars look good, but scrolling doesn't work the same as any other app. It hits a solid wall at either end.

- The preferences dialog is not a dialog, but a web browser tab (!), and its controls all look strange. They're not like standard OS controls or standard web controls. They're mostly just words floating on empty space, and some of them happen to be clickable. (It doesn't even have the advantage of being a webpage: the back button is enabled, but don't take me back to the last thing I was looking at here.) Some settings open a (custom, of course) dialog-in-a-tab, which is resizable, but if you resize it, the main scrollbar disappears, so you can't see the bottom of the dialog with the Cancel/OK buttons.

- It doesn't use the standard localization setting. It has its own, but half of Firefox doesn't even seem to use that, because even though my System Preferences is English, and my Firefox language preference is English, and even my Firefox content preference is English, it's showing half the UI in Japanese still. The context menu is half English and half Japanese!

- It's got a whole second menu (!) in the toolbar, with no way to hide it (see above: non-standard toolbars). The font, text alignment, highlight color, icons, and animation are all non-standard. Of course, it doesn't obey the system accessibility settings, either.

- Tree controls (e.g., in the History window) are non-standard, and standard keyboard shortcuts don't work here, either.

- It uses a (custom, of course) pop-over as an upgrade notification, which can't be dismissed by clicking outside them. Or dismissed permanently, like normal notifications.

The whole reason I use a Mac is for consistency. That's been its primary benefit since 1984. Instead of learning 10 completely different different programs, I just have to learn the common parts once. (Remember those keyboard overlays for the IBM PC we used so we didn't have to memorize which F-key meant "Save" in each different program?) In Firefox, everything is custom, and works differently than other apps. The keyboard, mouse, display, menus, windows, and controls are all weird. If I were OK with that, I'd switch back to Linux.

Re:Firefox’s Fight for the Future of the Web by saagarjha on Sunday November 17, 2019 @03:31PM (#21559899)
Yeah, it’s kind of depressing how much better it could be with just a touch of Cocoa; these shortcomings are readily apparent so it wouldn’t even take that much to improve it. I wonder if Mozilla could solve this by just hiring someone who’d focus on improving platform UI to the point where it was competitive with Chrome…
Re:Firefox’s Fight for the Future of the Web by leadingthenet on Monday November 18, 2019 @04:36AM (#21562987)
Even Chrome isn't competitive with Safari, UI-wise. It's plagued with many of the same issues as Firefox on macOS, last I checked.
Re:Firefox’s Fight for the Future of the Web by saagarjha on Monday November 18, 2019 @05:16AM (#21563148)
Well, some of them. It's not great, but it's better than where Firefox is now.
Re:Firefox’s Fight for the Future of the Web by leadingthenet on Monday November 18, 2019 @08:19AM (#21564043)
Very slightly, if at all.

The settings page is still non-standard, the same for the scrolling, keybindings don't work in the usual macOS way (CMD+Q for instance quits only if you hold, which is baffling), the app updates itself in a non-obvious way, the top-bar is laggy when in fullscreen mode, and the list can go on and on.

Re:Firefox’s Fight for the Future of the Web by yoasif_ on Sunday November 17, 2019 @08:57PM (#21561340)
> It doesn't use the standard localization setting. It has its own, but half of Firefox doesn't even seem to use that, because even though my System Preferences is English, and my Firefox language preference is English, and even my Firefox content preference is English, it's showing half the UI in Japanese still. The context menu is half English and half Japanese!

That sounds totally unexpected. Can you open a bug https://bugzilla.mozilla.org/enter_bug.cgi including the details from your about:support page?

Something sounds broken and I'd expect a fix.

Re:Firefox’s Fight for the Future of the Web by ImprovedSilence on Sunday November 17, 2019 @12:37PM (#21558913)
i have way too many tabs open at all times, and chrome makes it way way easier to see what I have open and get to the tab I want quickly.(it just shows more tabs than Firefox, this is my main complaint) The top bar uses less vertical real estate and is just much cleaner overall. I can see more if not all of the url. Chromes next tab left, next tab right, and close tab, automatically map to the keyboard shortcut I set in macOS, and I still haven’t even found the menu option for next and previous tab in Firefox. (I’m sure it’s there and I just haven’t found it yet, but if it’s not there, that’s a deal breaker for me)

I very badly want to use Firefox as my main browser, and I have it installed and give it a go every now and then, but it’s just not all the way there yet for me.

Re:Firefox’s Fight for the Future of the Web by kilburn on Sunday November 17, 2019 @12:50PM (#21558983)
The vertical space you can easily fix by opening the hamburguer menu > customize > density (bottom left) > compact. It then uses less space than chrome. You can also add/remove items from the top bar there, making your address bar larger if you want to.

The default hotkeys for next/prev tab are cmd+option+left/right arrow. I don't know how to change those...

Re:Firefox’s Fight for the Future of the Web by clairity on Sunday November 17, 2019 @01:02PM (#21559053)
i use ctrl-tab and ctrl-shift-tab for tabbing. easier 1-handed operation and closer to other "change context" shortcuts like next/prev window (cmd-~, cmd-shift-~) and select desktop/space (ctrl-1, ctrl-2, etc).
Re:Firefox’s Fight for the Future of the Web by ImprovedSilence on Sunday November 17, 2019 @01:51PM (#21559328)
yeah, I'm muscle-memoried into cmd-' and cmd-; for tabbing right and left, I like using those keys, and this is across pretty much everything I use (I suppose chrome and terminals, mostly..). It's firefox, there's probably an extension for it, but that takes work to find and feels kludgy.

good to know about the density, thanks.

Re:Firefox’s Fight for the Future of the Web by chappi42 on Sunday November 17, 2019 @04:47PM (#21560246)
In the mac settings about keyboard/shortcuts, you can define program specific shortcuts; e.g. take the exact name from the firefox menu for the 'next tab' action and give the shortcut you want.
Re:Firefox’s Fight for the Future of the Web by ImprovedSilence on Sunday November 17, 2019 @11:29PM (#21561885)
Right, so that's part of my gripe. in keyboad shortcuts, i've got global (all applications) shortcuts for select/show next/previous tab. Those dont map to firefox. Fine, but Firefox doesn't have a menu title for next tab, so setting a shortcut for a non-named function doesn't work. I've tried the documentation(https://support.mozilla.org/en-US/kb/keyboard-shortcuts-perf...), using "go one tab to the left" doesn't work. It's just way more effort to figure out than it needs to be for a browser in 2019.....
Re:Firefox’s Fight for the Future of the Web by chappi42 on Monday November 18, 2019 @10:49AM (#21565208)
I apologize, you are completely right (was not on the Mac when I answered and mixed it up with Terminal and Finder).
Re:Firefox’s Fight for the Future of the Web by SAI_Peregrinus on Sunday November 17, 2019 @04:11PM (#21560070)
Interesting, my complaint about Chrome's UI is that it doesn't support Tree Style Tabs (or an equivalent) so I can't have that many tabs open at once.
Re:Firefox’s Fight for the Future of the Web by Krasnol on Sunday November 17, 2019 @12:36PM (#21558908)
> According to the first statistics I found, Firefox is only about half as popular on the Mac as it in on Windows

Wich is not much of a surprise. If you educate your customer base to use one browser, many won't switch. See the lawsuits against Microsoft because of IE.

Re:Firefox’s Fight for the Future of the Web by ken on Sunday November 17, 2019 @02:17PM (#21559462)
But Chrome is still #1 on the Mac, too. Most Mac users do download a third-party browser and use that rather than the built-in one. Just not Firefox.
Re:Firefox’s Fight for the Future of the Web by nfriedly on Sunday November 17, 2019 @09:10AM (#21557952)
If Apple allowed Firefox on iOS - real Firefox with the rendering engine and extensions and everything, just like Android - I probably would have switched already.

As it stands, I stay on Android mostly for Firefox.

Re:Firefox’s Fight for the Future of the Web by notduncansmith on Sunday November 17, 2019 @09:32AM (#21558028)
Just curious, why does using “real Firefox” hold so much weight for you? Also, what steps have you taken to secure your device?

One reason I haven’t switched from iPhone is that I’m not confident in my ability to secure an Android, and I’d rather trust Apple than Google.

Re:Firefox’s Fight for the Future of the Web by nfriedly on Sunday November 17, 2019 @10:04AM (#21558169)
A big part of it is extensions, I have a handful of extensions that I use on a regular basis, and Firefox is the only mobile browser that actually supports extensions.

Another part of it is that I just trust Mozilla more. Both in terms of conflicts of interest, and just plain fixing bugs. For example, Safari on iPod touch has been unable to access the microphone for years, even though Safari on iPhones can.

I will concede your point about security. I think that iPhones are probably more secure than Androids. But, I feel that the security of my Android phone is sufficient for my needs.

Re:Firefox’s Fight for the Future of the Web by Zak on Sunday November 17, 2019 @01:36PM (#21559251)
Extensions don't get enough attention in this discussion. They're the main reason I prefer Firefox on Android. Anything that's missing or not to my liking, I can usually find an extension to provide or change. If something annoyed me enough and there wasn't an existing extension, I could look up the API docs and write one myself.
Re:Firefox’s Fight for the Future of the Web by Transfinity on Sunday November 17, 2019 @09:48AM (#21558086)
One big thing is that you can't change the default browser, so any time you click a link you end up on safari. In my experience (I tried iPhone for 2 weeks after my previous phone died, before returning it and switching back to Android) that makes installing a different browser effectively useless.

The rendering engine restriction is less obvious to the average user. And, frankly, if you don't trust Apple with your data then what are you doing using their network stack?

Re:Firefox’s Fight for the Future of the Web by endemic on Sunday November 17, 2019 @03:09PM (#21559784)
Extensions. On my Android phone I run LineageOS without gapps. I don’t install 3rd party applications, simply because the majority (in my experience) try to abuse your device in spite of limitations put in place by Apple/Google.
Re:Firefox’s Fight for the Future of the Web by jeena on Sunday November 17, 2019 @10:34AM (#21558337)
Sync of passwords, tabs, history, bookmarks, etc. as far as I know Firefox is the only browser which allows me to run my own sync server.
Re:Firefox’s Fight for the Future of the Web by Vinnl on Sunday November 17, 2019 @10:46AM (#21558394)
Is that not all possible with WebKit as the rendering engine? (In other words, doesn't Firefox on iOS already do all that?)
Re:Firefox’s Fight for the Future of the Web by Aaronn on Monday November 18, 2019 @12:27AM (#21562121)
Yes Firefox on iOS does already do that.
Re:Firefox’s Fight for the Future of the Web by radarsat1 on Sunday November 17, 2019 @06:48AM (#21557538)
How is it technically enforced though, I am curious. I mean, if I wrote an application that downloaded text files and rendered the text to the screen, I am sure that would be possible. If I wanted to add images to draw next to the text I am sure it is feasible. So how can one technically prohibit doing that? Implementation-wise, how is a web browser really that different from e.g. a video game?

Or is it only policy-enforced? Reviewers see something in an app that resembles a "browser" too much and take you down?

Re:Firefox’s Fight for the Future of the Web by capableweb on Sunday November 17, 2019 @06:53AM (#21557556)
My guess would be that it's policy-enforced and what Apple really has problems with is not browsers as a concept (dynamically loading and rendering data) but rather the execution engine that websites usually use (JavaScript) and seeing that as a too-large-to-review area where they want to avoid having vulnerabilities in applications published on App Store.

Or it's a anti-competitive move disguised as a "avoid vulnerabilities" but in reality they just really want to make sure iOS users keep using the one and only browser (Safari).

Re:Firefox’s Fight for the Future of the Web by marcthe12 on Sunday November 17, 2019 @07:54AM (#21557717)
Apple uses no Turing complete policy. So you also can't bundle a python or ruby interpreter in iOS. Its still anti-competitive but in a different area which is language and api. They are basically trying to push devs to use their native OS apis. PWA are also screwed up in Safari for a reason.
Re:Firefox’s Fight for the Future of the Web by Longhanks on Sunday November 17, 2019 @08:12AM (#21557776)
This is not true. There is for example the Pythonista IDE for iOS, which ships a full Python interpreter. https://omz-software.com/pythonista/
Re:Firefox’s Fight for the Future of the Web by labawi on Sunday November 17, 2019 @09:08AM (#21557947)
Is there an example of a non development/learning tool?
Re:Firefox’s Fight for the Future of the Web by vengefulduck on Sunday November 17, 2019 @01:09PM (#21559097)
If I remember correctly there’s an exception for learning and development tools.
Re:Firefox’s Fight for the Future of the Web by toxik on Sunday November 17, 2019 @08:09AM (#21557763)
That’s surely absurdly difficult to test, and provably impossible to prove the negative (i.e. my app is not Turing complete.) Is a calculator app not Turing complete? What about Google Sheets?
Re:Firefox’s Fight for the Future of the Web by danilocesar on Sunday November 17, 2019 @08:15AM (#21557787)
As long as it uses Apple's WebView, it's OK. This was the case for Firefox, they had to ditch Gecko in favor of using Apple's webview for iOS.
Re:Firefox’s Fight for the Future of the Web by dessant on Sunday November 17, 2019 @08:13AM (#21557781)
Kivy bundles Python in iOS apps, and the apps are accepted on the App Store. Do you have a link for this policy?
Re:Firefox’s Fight for the Future of the Web by saagarjha on Sunday November 17, 2019 @08:15AM (#21557789)
That likely falls under the “educational” exemption: https://developer.apple.com/app-store/review/guidelines/#sof...
Re:Firefox’s Fight for the Future of the Web by dessant on Sunday November 17, 2019 @08:18AM (#21557801)
That's unlikely, Kivy is also used for commercial apps. Bundling interpreters is allowed, but you must not use them to execute arbitrary code, unless you do it for educational purposes. Kivy doesn't load remote code, so it's not affected by this policy.
Re:Firefox’s Fight for the Future of the Web by saagarjha on Sunday November 17, 2019 @08:22AM (#21557811)
Then apps using it must ship all of their Python code in the app bundle to meet the App Store Review Guidelines.
Re:Firefox’s Fight for the Future of the Web by saagarjha on Sunday November 17, 2019 @08:08AM (#21557762)
> So you also can't bundle a python or ruby interpreter in iOS.

You can if it’s for educational purposes.

Re:Firefox’s Fight for the Future of the Web by beokop on Sunday November 17, 2019 @08:11AM (#21557771)
Pythonista is a full(-ish) offline Python IDE and has been on the App Store for years.
Re:Firefox’s Fight for the Future of the Web by JustSomeNobody on Sunday November 17, 2019 @07:06AM (#21557588)
interesting. But I can’t help but think by that logic Facebook should be too large to review.
Re:Firefox’s Fight for the Future of the Web by extropy on Sunday November 17, 2019 @07:35AM (#21557670)
Facebook does have code that dynamically compiles arbitrary input to machine code.

That's the part Apple is not allowing in third party apps.

Re:Firefox’s Fight for the Future of the Web by saagarjha on Sunday November 17, 2019 @08:09AM (#21557769)
> Facebook does have code that dynamically compiles arbitrary input to machine code.

Not outside of JavaScriptCore they don’t.

Re:Firefox’s Fight for the Future of the Web by sharpneli on Sunday November 17, 2019 @06:52AM (#21557553)
One cannot have writeable executable memory on iOS (apple can, we cannot).

Thus one cannot make a JIT compiler for js and thus pages are slow.

Game engines such as Unity use il2cpp to go from the C# stuff into C++ that can be statically compiled as running the C# as bytecode would be too slow without a jitter.

Re:Firefox’s Fight for the Future of the Web by radarsat1 on Sunday November 17, 2019 @06:56AM (#21557560)
Ah, so it is all about the javascript engine? Ok I can see how that might put up some major technical barriers, but still it should be technically feasible to have the firefox rendering engine make use of the iOS javascript engine, no? Maybe it's not worth the effort of course. I am just trying to get a feel for what the barriers are.
Re:Firefox’s Fight for the Future of the Web by sharpneli on Sunday November 17, 2019 @07:20AM (#21557622)
Not via public apis. So cannot be placed into app store.
Re:Firefox’s Fight for the Future of the Web by KonkeyDong69 on Sunday November 17, 2019 @07:34AM (#21557668)
In addition to what the other replies said, feel free to eyeball the code required to embed SpiderMonkey in Firefox at https://github.com/mozilla/gecko-dev/tree/master/dom/binding.... It's rather large and complex.
Re:Firefox’s Fight for the Future of the Web by padenot on Sunday November 17, 2019 @09:48AM (#21558090)
This is not at all the code to embed SpiderMonkey in Firefox, those are the bindings from DOM APIs to the implementation of those APIs in Firefox. Above that, calling into this layer, is another layer that transforms JS calls into C++ calls (roughly).

The interface between SpiderMonkey and the rest of Firefox is here: https://searchfox.org/mozilla-central/source/js/src/jsapi.h.

Re:Firefox’s Fight for the Future of the Web by vbezhenar on Sunday November 17, 2019 @07:22AM (#21557626)
I think that iOS JS engine is tied to WebView and it would be hard to re-use it with other rendering engine.
Re:Firefox’s Fight for the Future of the Web by saagarjha on Sunday November 17, 2019 @08:18AM (#21557802)
JavaScriptCore can be used can be used independently from the rest of WebKit, but I’d expect it to be slow.
Re:Firefox’s Fight for the Future of the Web by saagarjha on Sunday November 17, 2019 @08:17AM (#21557798)
> One cannot have writeable executable memory on iOS (apple can, we cannot).

Nitpick: you can but you cannot ship it via the App Store.

Re:Firefox’s Fight for the Future of the Web by shkkmo on Sunday November 17, 2019 @09:38AM (#21558046)
Apple as does not allow side-loading, so wouldn't a jailbreak be required?
Re:Firefox’s Fight for the Future of the Web by least on Sunday November 17, 2019 @10:45AM (#21558392)
Jailbreak, enterprise certificate, testflight, or a developer account would be required to sideload an app. You can technically sideload an app without a paid developer account, but the certificate only lasts seven days, at which point you'd have to reload the application.
Re:Firefox’s Fight for the Future of the Web by zzzcpan on Sunday November 17, 2019 @07:41AM (#21557684)
> One cannot have writeable executable memory on iOS (apple can, we cannot).

> Thus one cannot make a JIT compiler for js and thus pages are slow.

Lack of JIT doesn't slow down pages much. I believe the difference is so small that it might even be possible to be faster without JIT for most pages, especially on low power devices, it's only computation heavy pages that are going to suffer and even then it's not like you can't optimize common patterns statically ahead of time.

It doesn't mean that it's a good idea to invest into it, you are still under Apple's mercy and they clearly don't want competing browser engines.

Re:Firefox’s Fight for the Future of the Web by sharpneli on Sunday November 17, 2019 @08:17AM (#21557799)
If I have understood correctly (I’m a C++ graphics programmer. So don’t know too much about what’s flashy in the web world) V8 only jits. As in it can only produce machine code and there is not even an option to run it as an interpreter.
Re:Firefox’s Fight for the Future of the Web by saagarjha on Sunday November 17, 2019 @08:20AM (#21557806)
V8 has a high performance, JIT-less interpreter that disables TurboFan and relies exclusively on Ignition: https://v8.dev/blog/jitless
Re:Firefox’s Fight for the Future of the Web by chrisseaton on Sunday November 17, 2019 @09:15AM (#21557971)
> Lack of JIT doesn't slow down pages much.

So why do you think so many major companies invest such a huge amount of money in JS JITs? Google, Apple, Microsoft, Oracle, Mozilla all maintain JS JITs and spend what I guess is hundreds of millions of dollars a year on it.

Re:Firefox’s Fight for the Future of the Web by notacoward on Monday November 18, 2019 @08:31AM (#21564121)
A budget of $100M, with 50% devoted to salary and a median salary of $250K, would be 200 developers. I seriously doubt any of the companies you name are devoting even a quarter of that to JS JIT development. Yes, they each make significant investments, but let's not weaken the argument by indulging a penchant for hyperbole.
Re:Firefox’s Fight for the Future of the Web by chrisseaton on Monday November 18, 2019 @12:40PM (#21566289)
About 200 seems about right to me across all these companies. Have you worked on one of these teams?

> let's not weaken the argument by indulging a penchant for hyperbole

Please don’t be so dismissive and snide - there’s no need for that.

Re:Firefox’s Fight for the Future of the Web by notacoward on Monday November 18, 2019 @04:38PM (#21568384)
> About 200 seems about right to me across all these companies.

Then your initial estimate was way off, because you were suggesting multiple hundreds of millions and the average salary probably isn't that high.

> there’s no need for that

Honest argument wouldn't require such forceful correction.

Re:Firefox’s Fight for the Future of the Web by chrisseaton on Monday November 18, 2019 @05:41PM (#21568925)
I didn't say a hundred million per company.

> Honest argument wouldn't require such forceful correction.

Please try to tone it down.

Re:Firefox’s Fight for the Future of the Web by reubenmorais on Sunday November 17, 2019 @06:57AM (#21557563)
I don't know the details first hand, so take this with a grain of salt, but this is what I remember from talking to engineers who explored this possibility over the years:

You can't ship a native JIT (execute native code from the heap), I think it's enforced automatically by the App Store. So shipping your own JavaScript engine is out.

You can't download and interpret third-party code, I think this is enforced by human reviews, so shipping your own Web rendering stack is out.

You can use your own network stack with WebKit on top, which would let you offer some value to users like more advanced ad/tracker blocking.

Re:Firefox’s Fight for the Future of the Web by robin_reala on Sunday November 17, 2019 @07:27AM (#21557639)
This is exactly what Chrome on iOS did: they embedded their own networking stack, but reused WebKit and JSC.
Re:Firefox’s Fight for the Future of the Web by thekingofh on Monday November 18, 2019 @01:03PM (#21566502)
Thanks for the information. That part about disallowing third-party code interpreting is particularly painful to hear. They shut down any possibility of another browser. Could see that they do this for security reasons because a badly implemented interpreter could open up holes, but I'd imagine the sandbox is sufficient to allow at least interpreters.
Re:Firefox’s Fight for the Future of the Web by saagarjha on Sunday November 17, 2019 @08:14AM (#21557782)
Web content must be rendered through WebKit as per the App Store Review Guidelines (https://developer.apple.com/app-store/review/guidelines/). This is supposed to be enforced by App Store Review by inspection. In addition to this, there are technical reasons why your “browser” will be inferior to Apple’s web view performance-wise, mainly having to do with apps that generate code dynamically in-process needing entitlements that prevent submission to the review process.
Re:Firefox’s Fight for the Future of the Web by Yoric on Sunday November 17, 2019 @01:48PM (#21559312)
Policy-enforced.

Mozilla ported the true Firefox to iOS many, many years ago and Apple just rejected it from the store.

Re:Firefox’s Fight for the Future of the Web by krzyk on Sunday November 17, 2019 @09:18AM (#21557982)
I wonder why no antimonopolist issue was raised there by e.g. EU. Like they did for NFC in Germany - they forced all phones with NFC to be open to use by different apps, which might finally bring other pay solutions to iOS (or non NFC capable iphones to Germany).
Re:Firefox’s Fight for the Future of the Web by Despegar on Sunday November 17, 2019 @09:27AM (#21558008)
The NFC issue isn't related to antitrust. If they thought they could make an antitrust case against Apple they would. But their market share is so low in Germany, and the EU, that they just passed a law instead (specifically an amendment to an anti-money laundering law). It remains to be seen if it's even constitutional.
Re:Firefox’s Fight for the Future of the Web by Chirael on Sunday November 17, 2019 @12:27PM (#21558870)
It’s nowhere as good or fine-grained as uBlock origin, but I’m surprised no one ever seems to mention (or use?) Firefox Focus and it’s associated Safari content blocker. Seems to work really well for me on my iPad and iPhone, at least for general ad blocking.
Re:Firefox’s Fight for the Future of the Web by decasteve on Sunday November 17, 2019 @07:28AM (#21557648)
Anti-trust? Or have the lawyers for Apple (and Google) found the legalese to prevent this possibility?
Re:Firefox’s Fight for the Future of the Web by Macha on Sunday November 17, 2019 @07:55AM (#21557720)
Apple is only a monopoly if the market is iOS devices so they're quick to point out the market is all mobile devices.

Google allows sideloading, and allows competitors on the play store

Re:Firefox’s Fight for the Future of the Web by anoncake on Sunday November 17, 2019 @08:53AM (#21557908)
> they're quick to point out the market is all mobile devices.

It is not. The market is stores for Ios devices, Apple does have monopoly.

Re:Firefox’s Fight for the Future of the Web by sebazzz on Sunday November 17, 2019 @09:53AM (#21558116)
Technically I think you are free to build have other browser engines on iOS. However, JIT or other dynamically compiled code is not allowed because that's a security risk. You can't have a browser in 2019 with interpreted javascript.
Re:Firefox’s Fight for the Future of the Web by MaxBarraclough on Sunday November 17, 2019 @12:25PM (#21558861)
> I think you are free to build have other browser engines on iOS

I believe this is false, see 2.5.6 and 4.7 of https://developer.apple.com/app-store/review/guidelines/

But they do allow Opera Mini, a 'browser' for iOS where rendering is done in the cloud.

Re:Firefox’s Fight for the Future of the Web by fauigerzigerk on Sunday November 17, 2019 @09:55AM (#21558129)
But why is JavaScript JIT compilation tied to the rendering engine?
Re:Firefox’s Fight for the Future of the Web by andrewl-hn on Sunday November 17, 2019 @10:28AM (#21558318)
Yep. technically, Apple doesn't force Firefox to use WebKit. They could still use their Gecko WebRenderer and use Apple's JavaScriptCore to run page scripts. Same goes to Chrome: Blink + JSC instead of Blink + V8.

In practice in seems like both Chrome and Firefox have their renderers and JavaScript runtimes so tightly integrated that it's very hard to replace the later.

Re:Firefox’s Fight for the Future of the Web by fauigerzigerk on Sunday November 17, 2019 @10:47AM (#21558397)
Elsewhere in this debate sharpneli says that there is no public API to call into JavaScriptCore and using non-public APIs violates the App Store rules. So that would explain it.
Re:Firefox’s Fight for the Future of the Web by saagarjha on Sunday November 17, 2019 @03:14PM (#21559812)
There is API to use JavaScriptCore in your apps: https://developer.apple.com/documentation/javascriptcore. No JIT, though, so it’s slow.
Re:Firefox’s Fight for the Future of the Web by thekingofh on Sunday November 17, 2019 @11:14AM (#21558528)
I think you mean that you can have interpreted javascript, just not JIT compilers. They don't allow you to mark memory as executable. That syscall is completely disabled on their systems.
Re:Firefox’s Fight for the Future of the Web by saagarjha on Sunday November 17, 2019 @03:11PM (#21559793)
It is not, moprotect (and mach_vm_protect) work just fine if you have the appropriate entitlements or have a way of getting around its checks.
Re:Firefox’s Fight for the Future of the Web by thekingofh on Monday November 18, 2019 @12:43PM (#21566314)
I think the entitlements are not offered to apps such as firefox and those that are not Apple correct?
Re:Firefox’s Fight for the Future of the Web by saagarjha on Monday November 18, 2019 @04:06PM (#21568142)
Some of them are, but they cannot be used with apps delivered on the App Store.
Re:Firefox’s Fight for the Future of the Web by vbezhenar on Sunday November 17, 2019 @02:29PM (#21559534)
It can't be disabled because Safari and Webkit uses JIT for JavaScript. Probably it's enabled for apps signed by Apple.
Re:Firefox’s Fight for the Future of the Web by thekingofh on Monday November 18, 2019 @12:45PM (#21566332)
True it is disabled if you aren't Apple.
Re:Firefox’s Fight for the Future of the Web by iforgotpassword on Sunday November 17, 2019 @08:28AM (#21557834)
Yes, however, even as a Firefox advocate, I think in this case it's actually a good thing, since the majority of people would probably switch to Chrome then, contributing to the Blink monoculture.
Re:Firefox’s Fight for the Future of the Web by jraph on Sunday November 17, 2019 @10:25AM (#21558304)
It's not a good thing, only a bad thing with a good side effect ;-)
Re:Firefox’s Fight for the Future of the Web by mr__y on Sunday November 17, 2019 @03:17PM (#21559824)
You could run the browser on other machine and use VNC to access this from a iphone (or any other mobile device). While this is rather complicated and probably less reliable solution, the bonus points would be (almost) perfect isolation of the browser process.
Re:Firefox’s Fight for the Future of the Web by jrs95 on Sunday November 17, 2019 @10:43AM (#21558379)
It would be a lot more difficult than it sounds for Apple to allow 3rd party browsers and allow them to be good. Even on macOS now, Chrome depends on internal OS APIs which prevent it (or Electron apps) from being in the Mac App Store -- and for good reason, those things could break at any time. So in order to allow 3rd party browser engines that can compete with Safari in terms of performance etc they would need to make the APIs that are used to optimize them public.
Re:Firefox’s Fight for the Future of the Web by EvanAnderson on Sunday November 17, 2019 @11:09AM (#21558499)
If these non-public APIs are so useful it feels to me that Apple is acting in an anti-competitive manner. They're allowed to use them for their own applications but deny third-parties the right to sell in the "Store" if they use the APIs. Sounds a lot like MSFT in the 90's...
Re:Firefox’s Fight for the Future of the Web by alwillis on Sunday November 17, 2019 @01:01PM (#21559046)
As Apple has reiterated, browser engines require low-level access and for security reasons, other rendering engines aren’t allowed.

You can see from Apple’s updates that keeping up with the vulnerabilities for WebKit and iOS, etc. is already keeping them plenty busy:

https://support.apple.com/kb/HT210725 https://support.apple.com/kb/HT210721 https://support.apple.com/kb/HT210624 https://support.apple.com/kb/HT210603

Re:Firefox’s Fight for the Future of the Web by alwillis on Sunday November 17, 2019 @01:36PM (#21559249)
My point is this gets dramatically worse if every browser engine has low-level access to iOS.