News for hackers. Stuff that matters.
Re:We’ll stop selling our Code Editor app for iOS soon by saagarjha on Tuesday May 11, 2021 @07:10AM (#27116594)
> The biggest technical hurdle is the inability to run external processes on iOS and iPadOS.

> Apps on iOS and iPadOS must use Apple’s Javascript interpreter, JavaScriptCore.

Both of these really suck because they are policy, not technical, decisions. Even setting aside the arguments of whether JIT code is a security concern (it is not unless your security model is one where codesigning exists to prevent the addition of new native code) that you cannot spawn a new process, nor can you ship another JavaScript interpreter, is really unfortunate.

Allowing apps to spawn new processes is easy (I mean, just inherit sandboxing rules and resource limits…) and allows for a lot of new usecases, like robust crash reporting, web servers, privilege separation, and more. That Apple allows this on macOS and even uses it for its own apps on iOS just shows how useful this can be and how little it affects the security model of iOS.

Likewise, not allowing other JavaScript interpreters is just…annoying. Regardless of your opinions of JavaScriptCore, this is an unfair limitation on an already slanted playing field. Coupled with the fact that the JavaScriptCore interpreter (which the framework uses for anything you run in-process) is literally designed for low resource consumption instead of than performance makes this even more infuriating.

Re:We’ll stop selling our Code Editor app for iOS soon by Valodim on Tuesday May 11, 2021 @11:29AM (#27119280)
> Likewise, not allowing other JavaScript interpreters is just…annoying. Regardless of your opinions of JavaScriptCore, this is an unfair limitation on an already slanted playing field.

Reading the actual policies reveals that other interpreters are in fact allowed, but they may only be used for code that is part of the app bundle.

The actual limitation is that apps must be self-contained, and only javascriptcore and webkit may be used to run code from an external source (e.g. downloaded or user input).

See app store review guidelines, section 2.5.2: https://developer.apple.com/app-store/review/guidelines/#sof...

Re:We’ll stop selling our Code Editor app for iOS soon by miohtama on Tuesday May 11, 2021 @11:35AM (#27119379)
Apple tries to rely on static analysis. But it does not work and the engineering premise for it to work is shaky. This was discussed in Epic vs. Apple recently

https://arstechnica.com/gadgets/2021/05/apple-brass-discusse...

Re:We’ll stop selling our Code Editor app for iOS soon by threeseed on Tuesday May 11, 2021 @04:36PM (#27123186)
Objective-C supports dynamic dispatch i.e. call methods using a string at runtime.

So it's impossible to have static analysis work in all cases.

Re:We’ll stop selling our Code Editor app for iOS soon by UncleMeat on Wednesday May 12, 2021 @04:18PM (#27134654)
In all cases, sure. But static analysis people have been resolving virtual function calls effectively for decades.
Re:We’ll stop selling our Code Editor app for iOS soon by saagarjha on Tuesday May 11, 2021 @03:12PM (#27122224)
Apple uses some dynamic analysis as well, but of course this is limited to what they can see during review.
Re:We’ll stop selling our Code Editor app for iOS soon by tinus_hn on Tuesday May 11, 2021 @02:28PM (#27121668)
No, the actual limitation is that you can’t implement a JIT compiler. You can’t create executable memory blocks unless you have a special entitlement only Apples Javascript engine has.

Even using that engine your app must be self contained, you can’t download extra code, no matter the language.

As your link says:

> Apps should be self-contained in their bundles, and may not read or write data outside the designated container area, nor may they download, install, or execute code which introduces or changes features or functionality of the app, including other apps.

Re:We’ll stop selling our Code Editor app for iOS soon by iudqnolq on Wednesday May 12, 2021 @02:37PM (#27133627)
> Even using that engine your app must be self contained, you can’t download extra code, no matter the language.

That rule is honored more in the breach though

Re:We’ll stop selling our Code Editor app for iOS soon by JonathonW on Tuesday May 11, 2021 @01:33PM (#27120933)
With the big caveat that only JavaScriptCore can JIT, so third-party interpreters will always be performance-constrained. Not a big deal for languages like Python or Lua that are always interpreted, but things like .NET on iOS (Xamarin) have to be ahead-of-time compiled for decent performance, and it's a complete non-starter for third-party JavaScript interpreters.
Re:We’ll stop selling our Code Editor app for iOS soon by atq2119 on Tuesday May 11, 2021 @04:42PM (#27123253)
Neither Python nor Lua are always interpreted.

(Both languages have fairly well-known and reasonably widely used alternative implementations that include JIT.)

Re:We’ll stop selling our Code Editor app for iOS soon by dunham on Tuesday May 11, 2021 @07:43PM (#27125015)
JavaScriptCore can’t JIT when run in process, the entitlement isn’t there on your app, so the kernel won’t let it. I think that’s part of the reason for WKWebView (which runs the browser in a separate process and proxies it).
Re:We’ll stop selling our Code Editor app for iOS soon by w0utert on Tuesday May 11, 2021 @07:32AM (#27116763)
>> The biggest technical hurdle is the inability to run external processes on iOS and iPadOS. >> Apps on iOS and iPadOS must use Apple’s Javascript interpreter, JavaScriptCore.

> Both of these really suck because they are policy, not technical, decisions.

They are policy decisions that kind of make sense for a device like a tablet or phone though. Even though you could technically allow installing a complete development toolchain on an iPad, I can't imagine what the process would look like in practice. Download and install a complete *nix userland through the app store? Plus a compiler toolchain and each and every tool used in the build phase for your product? Who is going to maintain and distribute all these parts if the whole ecosystem is designed around the idea that apps are sandboxed and distributed through a curated app store? Imagine the customer support burden if you are the maintainer of some app that depends on external tools that can be used in a zillion different build/deploy configurations.

You could of course argue that the iOS ecosystem should not be based around a curated app store and sandboxed applications, but that would make it a MacBook...

Maybe we should put the whole idea of having one device that does everything to rest and accept that there are advantages to have a split between 'real computers' and tablets/phones. That's just my opionion though...

Edit: ah great, an immediate -3 because apparently people here think it is absolutely required to downvote straight away because they disagree with some opinion that is not their own.

Goodbye Hacker News, after ~10 years I'm finally done with the comment sections here and will deactivate my account and ask for it to be deleted

Re:We’ll stop selling our Code Editor app for iOS soon by kmeisthax on Tuesday May 11, 2021 @12:17PM (#27119970)
Apple advertises their own iPads as computers now, they certainly don't want their customers to look at iPads and think, "that's great, now I'm going to buy a real computer instead". They want their customers to buy an iPad. The only real way for iPadOS to go is "up", as in, absorbing more "real computer" features.

Also, what you're describing already exists, it's called iSH. It runs an x86 emulator with a copy of Alpine Linux inside. Somehow, they even convinced App Review to allow it (yes, Apple did threaten to remove it at one point, they backed down). You can use this penalty box to run pretty much any developer tool you like, you can mount file providers inside of the VM, etc. The only limitation is that it's x86 emulation is incomplete, I can't get it to run cargo so I can't compile Rust programs on it yet.

Re:We’ll stop selling our Code Editor app for iOS soon by alsetmusic on Tuesday May 11, 2021 @04:24PM (#27123029)
> they certainly don't want their customers to look at iPads and think, "that's great, now I'm going to buy a real computer instead". They want their customers to buy an iPad.

They want their customers to buy both. Apple has nothing to gain by killing off the Mac via the iPad.

Re:We’ll stop selling our Code Editor app for iOS soon by culturestate on Tuesday May 11, 2021 @08:43PM (#27125375)
> Apple has nothing to gain by killing off the Mac via the iPad.

If tablets are going to replace laptops for consumers in the long term, Apple would prefer that those tablets be iPads. If that shift means the iPad eats the Mac, so be it.

This already worked for them once - the iPhone cannibalized the (then-very profitable) iPod business with Apple’s explicit support, and now the company’s worth a trillion dollars.

Re:We’ll stop selling our Code Editor app for iOS soon by imwillofficial on Thursday May 13, 2021 @01:26AM (#27138724)
They clearly want ipad to replace macs for consumption, not coding.
Re:We’ll stop selling our Code Editor app for iOS soon by culturestate on Thursday May 13, 2021 @02:47AM (#27139169)
> They clearly want ipad to replace macs for consumption, not coding

I don't know what they want, but they're clearly preparing for a future where iPads are the default for consumption and creation.

There are multiple physical keyboard options, the Pencil is consistently refreshed, iPadOS has mouse/trackpad support now, and there's even an official - if very limited - iPad IDE[1] for learning Swift.

1. https://www.apple.com/sg/swift/playgrounds/

Re:We’ll stop selling our Code Editor app for iOS soon by imwillofficial on Thursday May 13, 2021 @10:46AM (#27142646)
Swift playgrounds does not change their “app console” philosophy as can be seen from their documents shown in their legal battle with Epic (I’m on mobile so I don’t have the link handy)
Re:We’ll stop selling our Code Editor app for iOS soon by culturestate on Thursday May 13, 2021 @10:57AM (#27142793)
If we’ve learned anything from Apple’s history, it’s that what they say today has little bearing on what they’ll do tomorrow.
Re:We’ll stop selling our Code Editor app for iOS soon by imwillofficial on Saturday May 15, 2021 @12:02AM (#27162240)
The truest comment I've ever read. Honestly I hope you're right! How cool would that be?
Re:We’ll stop selling our Code Editor app for iOS soon by dwaite on Wednesday May 12, 2021 @01:49AM (#27127047)
The line is that the adding additional functionality requires an informed user's explicit and understood consent. This is a blurry line of policy which is not able to be limited via technology. The developers of tools like iSH and Pythonista have to tread carefully.
Re:We’ll stop selling our Code Editor app for iOS soon by ulfw on Tuesday May 11, 2021 @09:41PM (#27125732)
Apple advertises their own iPads as computers now, they certainly don't want their customers to look at iPads and think, "that's great, now I'm going to buy a real computer instead".

Just because most of us on HACKERnews write code doesn't mean your average 'computer user' does. iPads work very well as computer replacements for the majority of people who just want to browse the web/do shopping/use their favourite video and other media viewer etc etc.

It's an everyday computer for the masses. Not a developer's workstation.

Re:We’ll stop selling our Code Editor app for iOS soon by donbrae on Tuesday May 11, 2021 @04:37PM (#27123197)
Wow, you can actually use iSH to install PHP, run `php -S localhost:8080` and view index.php or whatever in Safari. I had no idea this was possible on iOS. Thanks!
Re:We’ll stop selling our Code Editor app for iOS soon by dev_tty01 on Tuesday May 11, 2021 @05:36PM (#27123822)
Yeah, iSH is cool, but x86? Seems odd that they didn't run an ARM version of linux in a container or VM.
Re:We’ll stop selling our Code Editor app for iOS soon by kmeisthax on Wednesday May 12, 2021 @09:38AM (#27130173)
The iSH author had more experience with x86 than ARM.

I would not be surprised if iPadOS 15 ships with virtualization support, since the M1 has ARM EL2. If that is the case and Apple allows iSH to use it, then it probably would make sense to add ARM support to iSH for extra performance.

Re:We’ll stop selling our Code Editor app for iOS soon by dwaite on Wednesday May 12, 2021 @01:53AM (#27127067)
You cannot download and execute arbitrary files, so had to have something interpreted.

They could pick something easier to emulate perhaps, but x86 has benefits from a compatibility standpoint.

Maybe one day there would be a benefit of targetting WASM with a natively implemented syscall api?

Re:We’ll stop selling our Code Editor app for iOS soon by saagarjha on Thursday May 13, 2021 @02:59AM (#27139221)
We looked into it; the problem is that this makes system calls unbearably slow because they require IPC.
Re:We’ll stop selling our Code Editor app for iOS soon by saagarjha on Tuesday May 11, 2021 @06:02PM (#27124122)
There isn’t any support for this in iOS.
Re:We’ll stop selling our Code Editor app for iOS soon by emsy on Tuesday May 11, 2021 @01:09PM (#27120611)
I downvoted you for several reasons: while I do agree with the basic idea (an iPad shouldn’t be a MacBook with touch), I think the way you argue for it lacks nuance and doesn’t hold up. First of all, there is no reason why you can’t have both, *nix tools and a central App Store. Most people don’t use nix tools? Don’t install them. This would also work with sandboxing, e.g. I wouldn’t care if every app brings their own compilers even if it wastes memory. But even that is too much in apple’s eyes. The reason I need a MacBook that has the same processor as an iPad to develop for the iPad is completely arbitrary. Also, ideally I would like to not have to carry around multiple devices but more importantly, don’t buy them because it costs money (for some reason this argument rarely comes up, but money matters, especially in developing regions). Lastly, having devices that serve multiple purposes is a good thing for the environment. It’s also the way forward for the last 2 decades. When was the last time you had a separate MP3 player, a camera a calculator and a GPS device with you? Why shouldn’t my iPad be capable of enabling actual productive work?
Re:We’ll stop selling our Code Editor app for iOS soon by imwillofficial on Thursday May 13, 2021 @01:29AM (#27138741)
"Should" in an ethical sense often conflicts with "does" in a business sense.
Re:We’ll stop selling our Code Editor app for iOS soon by echelon on Tuesday May 11, 2021 @01:17PM (#27120715)
> Even though you could technically allow installing a complete development toolchain on an iPad, I can't imagine what the process would look like in practice.

Like every other computer ever.

> Imagine the customer support burden if you are the maintainer of some app that depends on external tools that can be used in a zillion different build/deploy configurations.

Microsoft and Google seem to work just fine. People seem to be able to ship when they have the tools to do so.

> They are policy decisions that kind of make sense for a device like a tablet or phone though.

They are strategic decision under the guise of policy decisions. Apple is "protecting you from dangerous apps" (read: dangerous apps = competition for Apple).

Apple is anti-competitive.

Re:We’ll stop selling our Code Editor app for iOS soon by freeone3000 on Tuesday May 11, 2021 @01:15PM (#27120690)
It's got 8GB of RAM and 3GHz processor. It runs Photoshop, for God's sake. An iPad is a small computer with touch.
Re:We’ll stop selling our Code Editor app for iOS soon by musicale on Tuesday May 11, 2021 @08:05PM (#27125142)
An iPad Pro and a MacBook Air have the same core hardware - even the same M1 CPU. Add a keyboard and they look really similar except that the iPad has a touchscreen!

But there are lots of hybrid tablets and touchscreen laptops. What makes the iPad an amazing device for me is its outstanding software library (e.g. Procreate) and the Apple Pencil.

I could certainly imagine Apple bringing its Pro apps - notably Final Cut, Logic, and XCode - to the iPad. But I can't imagine Apple opening up iOS any time soon any more than I would imagine Nintendo opening up the Switch.

Re:We’ll stop selling our Code Editor app for iOS soon by Siira on Tuesday May 11, 2021 @07:39AM (#27116823)
With this level of reasoning, SMS also makes sense for phones, and banning messenger apps is no big deal.

People have different needs, and a minority is always pushing the edges, and this pushing needs to happen so that the mainstream can pick and choose from the newly explored territory.

Re:We’ll stop selling our Code Editor app for iOS soon by hinkley on Tuesday May 11, 2021 @11:13AM (#27119055)
I was looking at some old notes the other day and remembering that I had made a plan for going the other direction, of slaving other devices to my IDE for faster round tripping of UI development.

That’s a very heterogenous example, but at some point we will be discussing personal clouds, where people have a little cluster of commodity/older ARM hardware that they balance a bunch of services across.

For example, you can download the server part of Don’t Starve Together as a separate app that you can then leave running even if you log off. That should be the standard for coop games, and probably for multiplayer games in general.

We are also overdue for a rethink of CI/CD pipelines, and I don’t mean As A Service.

Re:We’ll stop selling our Code Editor app for iOS soon by Valkhyr on Tuesday May 11, 2021 @08:00PM (#27125115)
> You could of course argue that the iOS ecosystem should not be based around a curated app store and sandboxed applications, but that would make it a MacBook...

Exactly what I would argue, and the only thing that would bring me back to iOS at this point.

> Maybe we should put the whole idea of having one device that does everything to rest and accept that there are advantages to have a split between 'real computers' and tablets/phones.

Google "convergence Pinephone", and imagine how powerful that would be with an iPhone running convergent macOS. And how much more powerful having macOS (with a mobile-optimized GUI) on the phone would make it on the go.

Re:We’ll stop selling our Code Editor app for iOS soon by simias on Tuesday May 11, 2021 @02:28PM (#27121664)
I understand your frustration with downvotes but it's not too bad in general in my experience. It's Apple discussions in particular that are hopeless, you have the rabid fanboys one one side and the rabbit haters on the other. I gave up on commenting on these stories, you can try to make a constructive comment only to be immediately grayed out.
Re:We’ll stop selling our Code Editor app for iOS soon by musicale on Tuesday May 11, 2021 @07:25PM (#27124888)
Downvoting seems to turn any opinionated discussion into a stupid game/power struggle between upvotes and downvotes. As if you somehow "win" whenever someone with a different perspective is downvoted to grey.

It's bad on HN, and it's much worse on other sites.

Re:We’ll stop selling our Code Editor app for iOS soon by imwillofficial on Thursday May 13, 2021 @01:34AM (#27138776)
Ive found this as well. Offering input from a highly specialized experience set (US IC community) being downvoted because I share the reality of some things that conflict with how people think things should be.
Re:We’ll stop selling our Code Editor app for iOS soon by jeroenhd on Tuesday May 11, 2021 @11:26AM (#27119248)
> They are policy decisions that kind of make sense for a device like a tablet or phone though. Even though you could technically allow installing a complete development toolchain on an iPad, I can't imagine what the process would look like in practice. Download and install a complete *nix userland through the app store? Plus a compiler toolchain and each and every tool used in the build phase for your product? Who is going to maintain and distribute all these parts if the whole ecosystem is designed around the idea that apps are sandboxed and distributed through a curated app store? Imagine the customer support burden if you are the maintainer of some app that depends on external tools that can be used in a zillion different build/deploy configurations.

I've got Termux running on my phone, complete with vim plugins, language server support, several compilers and all kinds of other tools. Combined with a bluetooth keyboard, it can be very useful in a pinch. It'll stop working on Android 11 because of "security concerns", but either thankfully or sadly, my phone has no stable Android 11 release yet. Everything is running inside a sandbox, I don't even have root access, and the binaries are distributed through a normal Linux package manager. With the right software you can even run a normal GUI on it through VNC or Spice, although that's something I haven't explored yet.

No need for other app developers to have any relation with Termux, that's what the sandbox is for. On Android, you can theoretically implement a system for sharing binaries and virtual files quite easily if Termux would support it, but I haven't seen such need myself.

These tools are maintained by volunteers and the Termux developer, and can be extended by adding repositories made by other people. So "who is going to maintain and distribute all these parts" comes down to the same question as "who is maintaining and distributing all of these Debian packages": the developers who want to make the ecosystem and apps function.

Most users won't use their phone or tablet like this, but I honestly don't see why they shouldn't be allowed to if they wish to. Apple is selling a complete keyboard and display stand for iPads, so these devices are clearly being targeted for productive use. Yet Apple refuses to allow developers to be productive on these devices, because they don't want competition for their crappy mobile browser engine.

As far as hardware is concerned, the touch screen, keyboard and OS are pretty much the only serious differences between the iPad and the Macbook Air. If you prefer a two-in-one tablet/laptop combo (which quite a lot of people do), the iPad is the closest Apple product to fit the description, if it would allow users more software freedom.

I do see the advantage of the curated app store, but I don't see the advantage of banning customers from not using said app store for the end user. You don't _have_ to install any apps from outside the app store, you just get the option to do so if you wish. I don't know any non-technical people who have installed apps from outside the Play Store, so it's not like allowing any lifted restrictions will make the ecosystem collapse.

I have a hard time understanding why you would want a company to tell you what you can and cannot use a device for. Their suggestions are always welcome, but why would you be in favour of their restrictions?

Re:We’ll stop selling our Code Editor app for iOS soon by musicale on Tuesday May 11, 2021 @07:35PM (#27124960)
> I have a hard time understanding why you would want a company to tell you what you can and cannot use a device for. Their suggestions are always welcome, but why would you be in favour of their restrictions?

1. I'm in favor of locked-down devices for certain classes of users, because it reduces the technical support burden, one that I might otherwise be saddled with!

2. I'm willing to put up with walled gardens that have high-quality software, such as certain iPhone games and music apps, or first-party Nintendo games on the Switch. DRM is irritating, but I can live with it if it doesn't get in my way too much.

3. I'm in favor of several of Apple's developer restrictions that are aligned with my priorities of privacy, security, and battery life, so I'm willing to put up with the others that support Apple's business interests. Sideloading obviously makes such restrictions less enforceable.

Re:We’ll stop selling our Code Editor app for iOS soon by jeroenhd on Wednesday May 12, 2021 @05:47AM (#27128482)
I see. I don't think that all of these restrictions are really necessary to achieve the goals we both share for smartphones, but I can understand the rationale better now.

I actually agree with most of those reasons as long as there's a developer mode setting somewhere deep down to turn them off. I've only seen hidden settings being accessed on a large scale once, which was during the Pokemon Go hype, to allow GPS spoofing through the developer options; something that can't be easily done anymore.

With an off switch, normal users are protected and given a nice ecosystem while anyone else can benefit from the freedom of using their device the way they want to. This solves the technical support burden and the software quality issue, because to reach that audience, you still need to go through some form of accepted app store. If you prefer Apple's judgement for whatever reason, you just stick to their store and ignore the existence of any other app out there.

I have to disagree with you on the developer restrictions, though, and I think that's where my lack of understanding your mindset came from. The mandatory 15/30% cut and arbitrary rules (such as the ban on most parental control apps the moment Apple brings out a competitor) make it impossible for me to tolerate the other minor annoyances that come with Apple's decisions. Of course, Google has been going the same route, sadly.

Google has been applying many of the same protections, except for many of the privacy ones, and their platform doesn't suffer a side-loading problem at all. This indicates that the ecosystem would be fine if Apple would loosen up a bit, sticking to their privacy guns but allowing developers to still compete with whatever project they've come up with next.

Neither Google nor Apple have my best interests at heart, but in the case of Google I can at least work around their stupidity. I'll gladly lose access to some "exclusive" content if that's what it takes to install open source apps onto my phone.

Re:We’ll stop selling our Code Editor app for iOS soon by dgellow on Tuesday May 11, 2021 @09:15AM (#27117672)
Ironically, your comment was in positive when I read it...
Re:We’ll stop selling our Code Editor app for iOS soon by forrestthewoods on Tuesday May 11, 2021 @11:20AM (#27119139)
> will deactivate my account and ask for it to be deleted

I don’t think accounts can be deleted? I tried once and was told no. :(

Re:We’ll stop selling our Code Editor app for iOS soon by colejohnson66 on Tuesday May 11, 2021 @01:11PM (#27120630)
I think they can, but they just refuse to. I’ve seen (a few times) some comments with the username and text as “[deleted]”. But I’m not @dang, so I can’t say for sure.
Re:We’ll stop selling our Code Editor app for iOS soon by em-bee on Tuesday May 11, 2021 @08:24AM (#27117211)
yes, downvoting hurts, and sometimes it's not fair, i got to feel that too. but it has been said repeatedly that downvoting is reasonable to voice disagreements. replying would be better, but not everyone can put their thoughts into words.

try to think about it as a strong disagreement.

(EDIT: i wonder who downvoted this comment now ;-)

Re:We’ll stop selling our Code Editor app for iOS soon by tannhaeuser on Tuesday May 11, 2021 @11:15AM (#27119083)
I haven't downvoted you, but voicing disagreement via downvoting isn't reasonable, since it tends to have dissenting opinions not be heard at all. When we're here to have a discussion after all, aren't we?
Re:We’ll stop selling our Code Editor app for iOS soon by greggman3 on Tuesday May 11, 2021 @12:41PM (#27120288)
I agree with you but HN does not. HN specifically says downvoting for disagreeing is a valid and even encouraged used of downvoting on HN. I've been informed of this by Dang when complaining about downvoting before.

https://news.ycombinator.com/item?id=16131314

I wish I could downvote downvoting

Re:We’ll stop selling our Code Editor app for iOS soon by em-bee on Tuesday May 11, 2021 @01:28PM (#27120857)
well, yes, i used to think like that too, but i changed my mind. even when i received downvotes. they don't say much, but they did tell me that there are people who disagree with me. it is a weak signal, but it is a signal, and so it's not useless nor unreasonable.

personally, i only downvote if i feel someone says something unreasonable or worse. but not if it is a good argument, even one that i disagree with. in those cases i even counterupvote other downvotes.

as for the downvote on my comment, that was more a rethorical question. i was actually just laughing at that, given the subject of the message. and the subsequent upvotes show that a lot of people agree with the comment.

(edit: it gets funnier. by now my above comment received at least 8 upvotes and 4 downvotes (or up to 4 people changed their mind))

Re:We’ll stop selling our Code Editor app for iOS soon by adler0901 on Tuesday May 11, 2021 @11:35AM (#27119373)
Why is there voting at all? It's so childish.
Re:We’ll stop selling our Code Editor app for iOS soon by guggle on Tuesday May 11, 2021 @12:56PM (#27120451)
Upvoting that.
Re:We’ll stop selling our Code Editor app for iOS soon by Hoasi on Tuesday May 11, 2021 @01:17PM (#27120717)
> replying would be better, but not everyone can put their thoughts into words.

Exactly, downvoting as a way to disagree is the easy way, it’s childish, puerile, and ridiculous. But let’s put things into perspective. A comment is just an opinion in a sea of random opinions. Opinions, for the most part, are not even personal, people tend to borrow them. To think through something and come up with an original opinion takes a lot of work. A downvote is just an easy dismissal, in a sea of easy dismissals. That’s not a proper way to communicate.

Downvoting is imperfect, but that said, I understand how people can find it useful as a curating system. I never downvote comments I disagree with because it doesn’t accomplish anything. It also takes too much energy.

Re:We’ll stop selling our Code Editor app for iOS soon by simion314 on Tuesday May 11, 2021 @07:56AM (#27116980)
As long as Apple makes money from allowing people to buy "Pro" apps like IDEs, REPL , other creation apps then you wrong, otherwise Apple should reject this apps as not allowed because the device is not capable for Pro creator usage.
Re:We’ll stop selling our Code Editor app for iOS soon by 2OEH8eoCRo0 on Tuesday May 11, 2021 @11:13AM (#27119058)
That sounds like the exact thing that Microsoft was slapped with in the 90s. Microsoft used operating system functionality for their browser that 3rd parties did not have access to. Microsoft was forced to open this stuff up.

Apple regularly leverages operating system calls that 3rd parties do not have access to.

Re:We’ll stop selling our Code Editor app for iOS soon by chipotle_coyote on Tuesday May 11, 2021 @02:08PM (#27121411)
I'm not sure it's the same thing. It's an arbitrary and somewhat dubious limitation, but it's less like "IE gets to hook into the OS at a lower level than Netscape Navigator can" than if the problem has been "Netscape Navigator can run on Windows but has to use IE's rendering engine."

I think a lot of iOS's limitations come from a philosophical stance Apple took at the start of the (iOS) App Store -- iPhones and iPads should be treated like consoles, not general purpose computing platforms. Despite them marketing the iPad Pro as if it's a full-bore computer replacement -- and to be fair, there are a lot of use cases where it really can be (e.g., office worker, photographer, writer[1], even video/audio editor -- on an OS level, they've stubbornly stuck with the "Mac = computer, iPad = console" approach[2] and I don't think they're going to change it unless forced.

[1] With certain limitations. I can use an iPad well enough for my fiction and non-fiction, but not for my technical writing.

[2] The "Mac = computer" part of that is why I disagree with the prevailing opinion on HN about how Apple will "inevitably" lock down the Mac to the same degree they have the iPad; I think they continue to see them as fundamentally different classes of products, even as that distinction grows ever more arbitrary.

Re:We’ll stop selling our Code Editor app for iOS soon by nicoburns on Tuesday May 11, 2021 @06:05PM (#27124175)
I think there's reasonable argument to be made that smartphones are important enough that they should not ve like consoles, and should be forced to be more open. I guess a similar argument to that used to justify regulating utlities.
Re:We’ll stop selling our Code Editor app for iOS soon by dwaite on Wednesday May 12, 2021 @02:00AM (#27127109)
The problem is that there are a mix of technical and non-technical restrictions in order to keep end users from shooting themselves in the foot.

It is likely a "careful what you wish for" with regulating the platforms like utilities, because they would likely regulate much farther down - the governments would become an additional party setting app store policy to a much greater degree than we see today.

Re:We’ll stop selling our Code Editor app for iOS soon by Jtsummers on Tuesday May 11, 2021 @11:24AM (#27119210)
That's ignoring all the other things MS was up to at the time. They did a lot of embrace-extend-extinguish to reduce the effectiveness of competitors, a lot of dirty dealing with OEMs to block alternate OSes. The IE thing was just one piece of a much larger case.
Re:We’ll stop selling our Code Editor app for iOS soon by 2OEH8eoCRo0 on Tuesday May 11, 2021 @12:35PM (#27120222)
The main component of Microsoft v. US was about this:

https://en.wikipedia.org/wiki/United_States_v._Microsoft_Cor...

Part of their punishment was to open up APIs and allow 3rd parties to audit. If this wasn't the main part of the case why was this used to remedy?

Re:We’ll stop selling our Code Editor app for iOS soon by Jtsummers on Tuesday May 11, 2021 @01:53PM (#27121223)
IE was used because it was a clear demonstration of MS's abuse of their market share and monopoly position to stifle competition. If they'd integrated their office applications in a similar fashion, spending billions of dollars on development and advertising only to release it for free and forced OEMs to not install a third party office application suite with strong arm tactics, that's what we would have seen.

The browser was not special, the abuse was the issue and the browser case was solid to use as a central claim against MS.

And this bears repeating again and again:

The browser was not and is not special. It does not matter. It was the abuse that was at issue, not the browser itself. The browser was a symptom of the abuse. Again, the browser was not the issue, only a symptom of abuse of their monopoly position.

Any claims against Apple about the Safari browser on mobile being like the IE situation on Windows is the result of a shallow reading of the case.

Re:We’ll stop selling our Code Editor app for iOS soon by 2OEH8eoCRo0 on Tuesday May 11, 2021 @04:44PM (#27123276)
https://www.justice.gov/atr/us-v-microsoft-courts-findings-f...

>34. Viewed together, three main facts indicate that Microsoft enjoys monopoly power. First, Microsoft's share of the market for Intel-compatible PC operating systems is extremely large and stable. Second, Microsoft's dominant market share is protected by a high barrier to entry. Third, and largely as a result of that barrier, Microsoft's customers lack a commercially viable alternative to Windows.

Viewed together, three main facts indicate that Apple enjoys monopoly power. First, Apple's share of the market for smartphones is extremely large and stable. Second, Apple's dominant market share is protected by a high barrier to entry. Third, and largely as a result of that barrier, Apple's customers lack a commercially viable alternative to iOS.

Re:We’ll stop selling our Code Editor app for iOS soon by Jtsummers on Tuesday May 11, 2021 @04:49PM (#27123334)
How? There are many viable alternatives to everything Apple makes. There are plenty of non-Apple laptops, desktop computers, tablets (ok, this is more limited at least in terms of equivalent capability), phones, even the watch.

And Apple, unlike MS at the time, has not been conducting the same abusive policies that put competitors out of business, which is a large part of what raised the cost of entry.

Re:We’ll stop selling our Code Editor app for iOS soon by 2OEH8eoCRo0 on Tuesday May 11, 2021 @05:05PM (#27123510)
>Third, and largely as a result of that barrier, Microsoft's customers lack a commercially viable alternative to Windows.

Do Apple customers have commercially viable alternatives? Apple's current customers and, not only alternatives, viable alternatives?

I personally know many people who lament, "All my stuff is Apple, I can't leave!" Of course they could leave if forced to but it is not viable. Perhaps their other devices would stop working. Those people aren't choosing Apple products because they think they're better, they are choosing Apple products because they are a victim of Apple lock-in.

Re:We’ll stop selling our Code Editor app for iOS soon by Zak on Tuesday May 11, 2021 @05:18PM (#27123647)
I remember when Microsoft had its dominant position with Windows[0] in the late 1990s; sentiments along the lines of "this sucks, but we're stuck with it" were common. I do not hear that sentiment from Apple users often today. Even when they have complaints, they typically like the hardware and/or software better than alternatives to which they have been exposed.

In case that seems like something a fanboy would write, I should clarify that I am not an Apple user, nor do I have any desire to buy Apple products (though I do hope somebody else manages to build a fast, cool-running ARM laptop soon).

[0] Windows still has a very high market share for desktop operating systems, but there's much less lock-in for most users.

Re:We’ll stop selling our Code Editor app for iOS soon by nl on Tuesday May 11, 2021 @06:09PM (#27124216)
There are reasonable alternative to all of Apple's products and I'm not aware of anything except convince stopping people moving.

This sounds a bit like saying Ford has a monopoly on the Ford car market - true, but not how anti-trust cases work.

Re:We’ll stop selling our Code Editor app for iOS soon by bananabreakfast on Tuesday May 11, 2021 @06:40PM (#27124501)
Where on Earth are you getting that Apple's market share is "extremely large and stable"?

iPhones account for 17% of the smartphone market.[0] That's less than Samsung.

iOS has 27% market share against Android's 72% [1].

Apple has a monopoly on Apple products. Yes, there is a high barrier to entry to compete with Apple on making Apple products.

But they in no sense have a dominant market position, much less one to be compared with Microsoft at their height when IE had 95% market share of browsers [2]

[0] https://www.counterpointresearch.com/global-smartphone-share... [1] https://gs.statcounter.com/os-market-share/mobile/worldwide [2] https://en.wikipedia.org/wiki/Usage_share_of_web_browsers

Re:We’ll stop selling our Code Editor app for iOS soon by 2OEH8eoCRo0 on Tuesday May 11, 2021 @07:59PM (#27125113)
What is iOS market share in the US?
Re:We’ll stop selling our Code Editor app for iOS soon by saagarjha on Tuesday May 11, 2021 @10:48PM (#27126056)
Over 50%.
Re:We’ll stop selling our Code Editor app for iOS soon by nl on Tuesday May 11, 2021 @06:06PM (#27124181)
The iOS ~50% smartphone market share is dramatically different to the 90%+ market share Windows had.

Redefining the market as "the iOS smartphone market" is what Epic seems to be trying to do. I'm skeptical about this being a workable approach in an anti-trust case.

Re:We’ll stop selling our Code Editor app for iOS soon by spoonjim on Tuesday May 11, 2021 @04:27PM (#27123081)
How is it not similarly abusive to ban non-approved software from being installed without paying a 30% protection fee?
Re:We’ll stop selling our Code Editor app for iOS soon by anaerobicover on Tuesday May 11, 2021 @03:01PM (#27122077)
In similar way that Al Capone was indicted for tax evasion, not for the many other crimes he was understood to commit. The prosecution stands on what it can be able to proved in court, with a judge sharply listening to each detail.
Re:We’ll stop selling our Code Editor app for iOS soon by mhh__ on Tuesday May 11, 2021 @12:47PM (#27120346)
That's true but consumers would definitely be empowered if Apple received a similar ruling.
Re:We’ll stop selling our Code Editor app for iOS soon by macintux on Tuesday May 11, 2021 @11:36AM (#27119394)
Plus the fact that Microsoft had a monopoly they were abusing; Apple doesn't by any reasonable metric.
Re:We’ll stop selling our Code Editor app for iOS soon by not2b on Tuesday May 11, 2021 @01:24PM (#27120798)
Here's a reasonable metric: who controls the market for iPad or iPhone applications, and how did that compare to who controlled the market for applications that ran on Windows at the peak of Microsoft's dominance? For the former, the only distribution method is via Apple's store and Apple gets a cut of every sale. For the latter, developers could sell directly to the public; Microsoft did not control this. Apple's monopoly is much stronger.

Apple apologists will blur this by taking about the smart phone market as a whole. But once someone has bought a device, they are no longer in that larger market. They need apps, and there's only one place to get them.

That only leaves the question of whether they are abusing the monopoly.

Google has a similar monopoly over Android applications, but it's not as tight, because of side-loading and fragmentation by Amazon and others. Still, it's a near-monopoly because few people bypass the Play Store.

Re:We’ll stop selling our Code Editor app for iOS soon by macintux on Tuesday May 11, 2021 @01:41PM (#27121047)
> Apple apologists will blur this by taking about the smart phone market as a whole.

Until you can find a judge willing to endorse your definition of "market", it's not just "Apple apologists" but "legal precedent".

Re:We’ll stop selling our Code Editor app for iOS soon by not2b on Tuesday May 11, 2021 @02:04PM (#27121365)
You'd have no problem finding economists to endorse my definition. As for judges, they only get to rule on cases that are brought to them, and that depends on the regulators.
Re:We’ll stop selling our Code Editor app for iOS soon by macintux on Tuesday May 11, 2021 @02:07PM (#27121397)
So, again, legal precedent is that Apple doesn’t have a monopoly.
Re:We’ll stop selling our Code Editor app for iOS soon by angus-prune on Tuesday May 11, 2021 @02:18PM (#27121520)
The legal precedent isn't that Apple doesn't have a monopoly.

There is no legal precedent on whether Apple has a monopoly. The law is entirely agnostic on whether Apple has a monopoly until it is put to a judge.

Re:We’ll stop selling our Code Editor app for iOS soon by catgary on Tuesday May 11, 2021 @05:48PM (#27123991)
Consoles have existed for decades applying similar rules to software distribution, no?
Re:We’ll stop selling our Code Editor app for iOS soon by macintux on Tuesday May 11, 2021 @02:33PM (#27121736)
There is no legal precedent I’m aware of that you can carve out one company’s products and claim that constitutes a market over which it holds a monopoly, in the presence of an alternative with comparable market share.
Re:We’ll stop selling our Code Editor app for iOS soon by lenkite on Tuesday May 11, 2021 @02:40PM (#27121827)
The Second Circuit has defined monopoly power as "the ability '

(1) to price substantially above the competitive level and

(2) to persist in doing so for a significant period without erosion by new entry or expansion.'

Apple's iOS platform matches both these conditions.

Re:We’ll stop selling our Code Editor app for iOS soon by macintux on Tuesday May 11, 2021 @02:58PM (#27122053)
Except iPhones aren’t generally more expensive than phones of similar caliber hardware. Samsung offers phones even more expensive.

Apple just doesn’t offer cheap hardware.

Does Porsche have monopoly power just because they don’t offer low-end models?

Re:We’ll stop selling our Code Editor app for iOS soon by lenkite on Tuesday May 11, 2021 @11:54PM (#27126409)
Porsche doesn't provide an app platform.
Re:We’ll stop selling our Code Editor app for iOS soon by shkkmo on Tuesday May 11, 2021 @01:50PM (#27121190)
I think we need two rules for the modern information economy to ensure competition.

I think it should be illegal to deliberately interfer with a devices owner's ability to run the software of their choice. This means that owners of iPhones, PlayStations, Switches, Tractors, Cars, etc should not have to treat the manufacturer as an adversary in their ownership of the devices.

I also think that content exclusivity contracts should be illegal and that all content creators that license content to a service should be required to offer reasonably similar licensing terms to that service's competitors.

Re:We’ll stop selling our Code Editor app for iOS soon by toast0 on Tuesday May 11, 2021 @02:36PM (#27121769)
> Here's a reasonable metric: who controls the market for iPad or iPhone applications, and how did that compare to who controlled the market for applications that ran on Windows at the peak of Microsoft's dominance?

Apple for iOs and software distributors and computer store retailers for the windows application market.

Microsoft dominated the market for operating systems for home computers, and they did a bunch of nasty stuff, including using their dominance to effectively restrict and/or prevent bundling of other operating systems with new computers, and there were shenanigans done against a handful specific products made by others, but AFAIK Microsoft did not make any attempt to dictate what applications computer stores sold. If you could convince distributors and retailers, your software could be on shelves. There were made for windows labeling programs, and those are now compulsory for drivers, but that's outside the Microsoft abuses time frame and there's not the same kind of pushback.

Google's control of Android is similar, but not nearly the same. Developers can make apks available for users and users can pretty easily install them; the experience seems to be getting consistently better, my newest phones will show a warning on opening that links to the checkbox and when you tick the box you can install the apk directly, without having to find it again. It's not quite as easy as running a setup program on windows, but it's darn close.

Sure, most developers don't provide apks, and most users don't use direct apk links when they're provided, but it's an available option vs jailbreaking an iOS device which requires a lot of fiddly steps. There's also a concern about Google enforcing some terms on downloaded apks that are also distibuted through the Play store, at least a few years ago, they didn't like non-google in app payment, even if it was only in the direct apk; and Google Play's security scanning apparatus runs against downloaded apks and sometimes shows scary messages which may be anti-competitive.

I think there's certainly a legal question about if Apple's captive market can be considered a market for anti-trust purposes. If so, there's a clear case of anti-competitiveness, IMHO. If the relevant market is applications on smartphones or tablets, I don't think Apple has enough marketshare that the anti-competitive things they do are prohibited, because IMHO, they only do things that are prohibited in combination with strong market power.

Google, on the other hand, probably has enough market power, regardless of segmentation, but they also are signficantly less restrictive.

Re:We’ll stop selling our Code Editor app for iOS soon by Jtsummers on Tuesday May 11, 2021 @11:47AM (#27119566)
Right. MS had somewhere around 97% of the desktop market for a chunk of the 90s, when the anti-trust stuff was really taking off. As an example:

They used that position to force OEMs to sell Windows only. BeOS was going to be on <vendor> desktops [0], but MS went to them and said, in short, "If you do this, you will have to pay retail price for our OS. And if you have to pay retail price, you will have to raise your hardware prices when selling Windows desktops. And if you have to do that, in this cutthroat low-margin industry, you won't be able to compete with the other OEMs."

The anti-trust case is really interesting reading (to me at least), and worth checking out. Most people only know the headlines of what was covered by it ("it's about browsers") but aren't aware of the deeper and over decade long issues that were covered by it.

Embrace, extend, extinguish: https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...

It wasn't just the browser's hooks into the OS (or the OS dependency on IE). It was the deliberate non-conformant manner that MS developed it in. It literally did things in the opposite way the standard described at times. See also their effort at implementing Java as part of their developer suite, where they were later forced to drop the J++ line because they were making an incompatible, non-standard Java.

[0] Compaq? It's in the suit, I may track it down before the edit window is closed.

Re:We’ll stop selling our Code Editor app for iOS soon by heavyset_go on Tuesday May 11, 2021 @06:06PM (#27124186)
Layman definitions of monopoly do not matter when it comes to antitrust laws[1]:

> Courts do not require a literal monopoly before applying rules for single firm conduct; that term is used as shorthand for a firm with significant and durable market power — that is, the long term ability to raise price or exclude competitors. That is how that term is used here: a "monopolist" is a firm with significant and durable market power.

Also, iOS has 60% of the mobile operating systems market in the US[2]. Apple's App Store is responsible for 100% more revenue than the Play Store[3].

Apple and Google are certainly leveraging their duopolies in both the mobile operating systems market and the mobile app distribution market in order to prevent competition in those markets and others.

[1] https://www.ftc.gov/tips-advice/competition-guidance/guide-a...

[2] https://deviceatlas.com/blog/android-v-ios-market-share

[3] https://www.businessofapps.com/data/app-revenues/

Re:We’ll stop selling our Code Editor app for iOS soon by richardwhiuk on Tuesday May 11, 2021 @06:13PM (#27124248)
And how much of it is because how Apple runs their platform?
Re:We’ll stop selling our Code Editor app for iOS soon by egeozcan on Tuesday May 11, 2021 @11:43AM (#27119497)
They are part of a duopoly and I hope Google also gets scrutinized.
Re:We’ll stop selling our Code Editor app for iOS soon by myko on Tuesday May 11, 2021 @02:41PM (#27121855)
Android isn't just Google though. Amazon ships Android devices that don't even have Google's Android store on them. Amazon also ships their own store which Android users can download and install even on Google devices - and they're not the only 3rd party store on Android.
Re:We’ll stop selling our Code Editor app for iOS soon by ipaddr on Tuesday May 11, 2021 @04:44PM (#27123278)
What % of android phones are Amazon? Less than 1%? I think they would need a bigger marketshare before you start including them as a market player.
Re:We’ll stop selling our Code Editor app for iOS soon by mywittyname on Tuesday May 11, 2021 @05:06PM (#27123516)
Phones? Probably nil. But tablets, firesticks, and kindles have to enjoy reasonable marketshare. Kindle is something like 70% of the ebook market, 85% if you include KindleUnlimited.

I believe non-Google Android phones are quite popular outside of the USA.

Re:We’ll stop selling our Code Editor app for iOS soon by nicoburns on Tuesday May 11, 2021 @06:10PM (#27124220)
Ebooks aren't really the same market as phones/tablwts though. So they're not that relevant to the discussion of a smartphone duopoly.
Re:We’ll stop selling our Code Editor app for iOS soon by myko on Tuesday May 11, 2021 @07:28PM (#27124915)
We're not talking about a smartphone duopoly though. This post is about a major iPad app. Tablets are fair game.
Re:We’ll stop selling our Code Editor app for iOS soon by macintux on Tuesday May 11, 2021 @12:21PM (#27120028)
Until/unless the two companies are caught colluding against consumers, duopolies aren't covered by antitrust law afaik.
Re:We’ll stop selling our Code Editor app for iOS soon by hparadiz on Tuesday May 11, 2021 @12:56PM (#27120449)
The Apple store is a monopoly when you consider just iOS. It is in fact 100% market share among apple devices. There is no alternative. Android doesn't replace an iPhone in many cases.
Re:We’ll stop selling our Code Editor app for iOS soon by coldtea on Tuesday May 11, 2021 @01:25PM (#27120816)
>The Apple store is a monopoly when you consider just iOS.

Every business is just a monopoly if you consider it alone, and a single 7 Eleven has 100% marker share among its store.

Re:We’ll stop selling our Code Editor app for iOS soon by shkkmo on Tuesday May 11, 2021 @02:10PM (#27121438)
The analagous situation with convenience storea is: If any convenience store chain was able to prevent other convenience store chains from operating in a geographic area, they would have a monopoly in that area. Consumers in that market segment would have no other choice unless they were willing to sell their house and move.

In your example, a consumer can easily leave 7-11 and go to a near by store at a much, much, lower cost than selling a house.

On Android, to have choices beyond the Play Store, all I need to do is change some setting and instal a 3rd party store.

On iPhone, to have choices beyond the AppStore I might be able to run some much more complicated and dangerous software, but only when Apple is behind in the cat and mouse game with jailbreakers.

The root of the question here is one we have to answer as a society. How much should consumer choice cost (relative to the price of the good/service they are choosing). Maybe 5x is reasonable, but 500x is not.

When a company deliberately does everything they can to raise those costs and thoae costs are very high (such as with Apple), I think we should absolutely call those companies to account for anti-competive and monopolostic trade practices.

Re:We’ll stop selling our Code Editor app for iOS soon by coldtea on Tuesday May 11, 2021 @02:13PM (#27121463)
>The analagous situation with convenience storea is: If any convenience store chain was able to prevent other convenience store chains from operating in a geographic area, they would have a monopoly in that area

This breaks down as there's no "physical area" preventing anything.

You can get an Android phone whether you're in Alaska or Miami or Tanzania. In fact it's easier, and most of the billions in the planet (including high income earners) do just that.

Re:We’ll stop selling our Code Editor app for iOS soon by shkkmo on Tuesday May 11, 2021 @02:19PM (#27121542)
The analogy is between the cost of moving to a new physical area and the cost of buying a new physical device.
Re:We’ll stop selling our Code Editor app for iOS soon by enos_feedler on Tuesday May 11, 2021 @05:08PM (#27123544)
Uh, it's more like the cost of switching your preferred convenience store chain vs. your phone platform. There are alternatives and you might like one more than the other, but at the end of the day both serve the same purpose (buy milk, or computer in my pocket). If this analogy breaks down it's not because Apple has a monopoly, it's because Android ecosystem has not delivered something similar enough to 7-11.
[dead]
Re:We’ll stop selling our Code Editor app for iOS soon by Jtsummers on Tuesday May 11, 2021 @01:34PM (#27120950)
And I don't have to use an Apple credit card on the iOS app store.
Re:We’ll stop selling our Code Editor app for iOS soon by hparadiz on Tuesday May 11, 2021 @01:46PM (#27121110)
Ah but you have to use the Apple app store. There is no alternative.
Re:We’ll stop selling our Code Editor app for iOS soon by Jtsummers on Tuesday May 11, 2021 @01:48PM (#27121146)
Sure there is, don't buy an Apple device. They aren't the majority or even necessary for anything. Android is a viable alternative and you can sideload applications there.

And, in stark contrast to the MS antitrust case, Apple doesn't have 97% of the market share.

[dead]
Re:We’ll stop selling our Code Editor app for iOS soon by coldtea on Tuesday May 11, 2021 @02:10PM (#27121435)
>You can't not have an iPhone for so many reasons.

This is the most entitled, "first world" problem, I've ever heard of.

Sure you can (not have one). The majority (60%+) of the population in the USA manages just fine without one. 90% in some Western European countries...

Pro tip: you don't need an Apple Watch either.

Pro tip 2: you might want to look up the definition of "need" and "lying".

Re:We’ll stop selling our Code Editor app for iOS soon by hparadiz on Tuesday May 11, 2021 @02:14PM (#27121473)
You'd be surprised what someone who runs a food truck or works in real estate "needs" to project "success".

Actual protip: get out of your tech bubble for two seconds and talk to some real business owners.

Re:We’ll stop selling our Code Editor app for iOS soon by coldtea on Tuesday May 11, 2021 @09:52PM (#27125791)
Adding true clauses (e.g. some people want an iphone to project success) doesn't necessarily make a true argument. The conclusion must also be supported by the clauses.

In this case, an argument which amounts to:

"People need to have an iPhone because some business owners feel they need it to project success, thus Apple has a monopoly on something essential"

is so random it can't be even be called wrong.

Whether some "business owners" feel they need an iPhone to "project success" doesn't mean anything, and is an absolutely moot point as to whether Apple is a monopoly, or even as to whether the iPhone is an essential good, or whatever else you had in mind.

Re:We’ll stop selling our Code Editor app for iOS soon by hraedon on Tuesday May 11, 2021 @06:29PM (#27124410)
"I need this specific platform to succeed for some reason" does not somehow make that platform a monopoly that should be subject to regulatory action.

Apple's management of their platform is not unique, is not meaningfully different from their competitors, and not meaningfully different from the management of similar stores in different industries. Even assuming they actually have built a strong enough brand that people are judged for having a competing product, I fail to see how requiring changes to the App Store solves that problem.

Re:We’ll stop selling our Code Editor app for iOS soon by nl on Tuesday May 11, 2021 @06:18PM (#27124301)
A brand requirement to establish prestige seems a weak anti-trust case.

Infact, a judge might see it as a counter argument. If prestige is the reason people buy Apple then almost by definition there must be alternatives.

Re:We’ll stop selling our Code Editor app for iOS soon by coldtea on Tuesday May 11, 2021 @02:07PM (#27121402)
Well, you don't have to use an Apple credit card in the App Store either.

That said, do you remember having to use Disney money in Disneyland for every transaction?

Re:We’ll stop selling our Code Editor app for iOS soon by toast0 on Tuesday May 11, 2021 @02:40PM (#27121831)
> That said, do you remember having to use Disney money in Disneyland for every transaction?

I remember it being a fun option to use either Disney or US dollars in the park, maybe it was required at some point, but I don't remember that.

Re:We’ll stop selling our Code Editor app for iOS soon by lancesells on Tuesday May 11, 2021 @02:07PM (#27121395)
I'm curious, do you use iOS devices?
Re:We’ll stop selling our Code Editor app for iOS soon by hparadiz on Tuesday May 11, 2021 @02:20PM (#27121547)
I own hand me downs I use for testing but they are usually in a pile on my desk and not actually in use.
Re:We’ll stop selling our Code Editor app for iOS soon by nicoburns on Tuesday May 11, 2021 @06:11PM (#27124227)
Hopefully that will soon change. Apple/google is a prime example of why it should.
Re:We’ll stop selling our Code Editor app for iOS soon by katbyte on Tuesday May 11, 2021 @06:50PM (#27124603)
The the PlayStation and Xbox and Nintendo stores are the exact same?
Re:We’ll stop selling our Code Editor app for iOS soon by smashingfiasco on Tuesday May 11, 2021 @11:06PM (#27126147)
Because Apple influenced them. They copied Apple’s model because Apple had been getting away with it, and will likely have to comply with whatever new regulations might result from this.
Re:We’ll stop selling our Code Editor app for iOS soon by katbyte on Sunday May 16, 2021 @02:53AM (#27171766)
Are you sure? I thought PlayStation store opened in 2006 and apple 2008?
Re:We’ll stop selling our Code Editor app for iOS soon by heavyset_go on Tuesday May 11, 2021 @06:15PM (#27124275)
> duopolies aren't covered by antitrust law afaik.

What exactly do you think the 'trust' in 'antitrust' means? From here[1]:

> A trust or corporate trust is a large grouping of business interests with significant market power, which may be embodied as a corporation or as a group of corporations that cooperate with one another in various ways.

[1] https://en.wikipedia.org/wiki/Trust_(business)

Re:We’ll stop selling our Code Editor app for iOS soon by macintux on Tuesday May 11, 2021 @07:03PM (#27124726)
Hence the caveat:

> Until/unless the two companies are caught colluding against consumers

Re:We’ll stop selling our Code Editor app for iOS soon by a1369209993 on Tuesday May 11, 2021 @05:45PM (#27123951)
What competition does[0] Apple have on the service of distributing iphone applications?

0: indeed, can, without stupedous efforts of reverse engineering that they actively oppose

Re:We’ll stop selling our Code Editor app for iOS soon by bosswipe on Tuesday May 11, 2021 @03:37PM (#27122500)
So if Apple had had any market share in the late 90s then Microsoft+Apple would have been allowed to put a strangle hold on the web the way that Google+Apple do to apps today. In that sense we are really lucky that Microsoft had that monopoly or the open web would not exist today.
Re:We’ll stop selling our Code Editor app for iOS soon by bosswipe on Tuesday May 11, 2021 @10:07PM (#27125867)
I''m really curious why this comment got downvoted. Wish I had gotten a reply. I don't see the error in my logic. If 90s Apple had had 50% of the desktop market Microsoft would not have been regulated. And Steve Jobs was no lover of open systems. In their hands the open web would not have survived.
Re:We’ll stop selling our Code Editor app for iOS soon by nostromo on Tuesday May 11, 2021 @07:07PM (#27124751)
You can do a lot of things as a non-monopoly that you can’t do as a monopoly.

Apple isn’t even a majority of the market, so laws on monopolies don’t readily apply here.

Re:We’ll stop selling our Code Editor app for iOS soon by easton on Tuesday May 11, 2021 @12:26PM (#27120082)
I was hoping with the announcement of the iPad Pro with the M1 chip and 16GB(!) of RAM it meant that Apple was going to give us some way of running arbitrary code inside sandboxes on the device in the next release of iPadOS. (So we could have Xcode, or at the least, Swift and Clang and a terminal). I suppose they probably would’ve told Panic though, even if under NDA since they’ve had a good relationship with Apple. Crap.
Re:We’ll stop selling our Code Editor app for iOS soon by Pulcinella on Tuesday May 11, 2021 @01:03PM (#27120529)
WWDC is in a month so we’ll see then. I will be disappointed if there isn’t at least XCode for the iPad. Swift Playgrounds already compiles Swift code on the iPad and has for years.
Re:We’ll stop selling our Code Editor app for iOS soon by lstamour on Tuesday May 11, 2021 @01:06PM (#27120561)
Just because it’s impossible for third-parties to write an IDE doesn’t mean Apple can’t. In fact, it seems more likely that Apple would ship Xcode for iOS as a way of trying out new API capabilities and then in a year or two allowing other devs to use some of the same capabilities. That said, I could imagine that if such an API existed, Visual Studio Code would be the first text editor devs would be excited for. I like Nova, it’s much faster than VS Code, but VS Code has all the extensions, and is cross-platform. I tend to use Nova for files, VS Code for folders and JetBrains IDEs for projects…
Re:We’ll stop selling our Code Editor app for iOS soon by hctaw on Tuesday May 11, 2021 @04:36PM (#27123187)
> it is not unless your security model is one where codesigning exists to prevent the addition of new native code

It is if your security model includes things like parental controls and payment processing.

Re:We’ll stop selling our Code Editor app for iOS soon by dev_tty01 on Tuesday May 11, 2021 @01:49PM (#27121171)
>Even setting aside the arguments of whether JIT code is a security concern (it is not unless your security model is one where codesigning exists to prevent the addition of new native code) ...

I'm a neophyte on security issues, but this seems like a very open ended assertion.

Doesn't JIT require rwx permission on a block of memory? Haven't there been thousands of security attacks over the years that started with some kind of buffer overflow (or similar approach) that is fundamentally enabled by rwx permission on a block of memory? Like I said, I'm just an observer in this area, so apologies if I am way off base.

>is literally designed for low resource consumption instead of than performance

I would say this is the right choice for a handheld device. At least it is for my phone.

Re:We’ll stop selling our Code Editor app for iOS soon by saagarjha on Tuesday May 11, 2021 @04:12PM (#27122911)
No, these are reasonable questions, they just miss the fact that Apple ships JavaScriptCore with a JIT. By not allowing JITs in third party apps Apple claims they are the only ones who can write a secure JIT (obviously false) and that their platform sandbox is too weak to stand up to arbitrary code execution. Plus, it’s not like normal code doesn’t have buffer overflows or other security issues. As for the tuning on the VM: perhaps in isolation. But again, the high performance JIT exists; it’s just not available to anyone else.
Re:We’ll stop selling our Code Editor app for iOS soon by dev_tty01 on Tuesday May 11, 2021 @06:29PM (#27124414)
Yes, you are right that they allow their own JIT. Their position would be that they spend a great deal of time hardening that JIT and don't trust others to take that time. Their JIT isn't perfect of course, but they control it and can fix it fast if needed. (In their opinion.) They are really saying that they aren't willing to take the time to exhaustively test other JITs. That is a frustrating choice, but I do understand the thinking.

You raise the bigger point. Is there no way for their platform sandbox to handle the concerns? That is a great question.

>Plus, it’s not like normal code doesn’t have buffer overflows or other security issues.

I think normal code on an M1 only runs in rx memory blocks [0,1], so no buffer overflow attacks. At least not without another attack to remap the blocks. This might go back to A12 processors. M1 strengthened the model.

Perhaps with these newer processors, the hardware support can harden the sandbox enough to allow more flexibility. One can hope...

[0] https://blog.svenpeter.dev/posts/m1_sprr_gxf/ [1] https://siguza.github.io/APRR/

Re:We’ll stop selling our Code Editor app for iOS soon by saagarjha on Tuesday May 11, 2021 @11:03PM (#27126131)
You’re exactly right about this being their position. The problem is that their position is not necessary grounded in fact: WebKit certainly isn’t a perfect browser engine, and arguably it might not even be the most secure one. However, it is not Apple’s job to test anything: it’s not like they are currently responsible for finding security issues in apps right now. Basically their position is:

“We work hard to make our engine secure. We don’t think anyone else should try.”

“But here’s a security issue in your engine. Can I use this other one which I think does a better job? Can I even try?

“No.”

FWIW, W^X is generally implemented by all good JITs these days because it’s a good idea. I’m sure the if given the opportunity browsers would adopt this, just like they’ve adopted sandboxing on macOS despite there being zero documentation or support for that interface. It’s just that Apple does not even allow them to do so on iOS. (Also, W^X does mot protect against all buffer overflow attacks.)

Re:We’ll stop selling our Code Editor app for iOS soon by Dylan16807 on Tuesday May 11, 2021 @07:23PM (#27124876)
JITs do not require memory to be writable and executable at the same time, which is the source of those security problems.
Re:We’ll stop selling our Code Editor app for iOS soon by saagarjha on Tuesday May 11, 2021 @11:04PM (#27126137)
JITs can be exploited even in the presence of W^X.
Re:We’ll stop selling our Code Editor app for iOS soon by Dylan16807 on Tuesday May 11, 2021 @11:26PM (#27126270)
Anything can be exploited. Normal compilers too, especially if you're running code someone else supplied. But I wouldn't say there are any especially severe vulnerabilities unique to JITing.
Re:We’ll stop selling our Code Editor app for iOS soon by paxys on Tuesday May 11, 2021 @03:28PM (#27122410)
This is also the reason why iPad Pro will never be the professional machine Apple is pushing it as, no matter how much processing power or marketing dollars they throw at it.
Re:We’ll stop selling our Code Editor app for iOS soon by katbyte on Tuesday May 11, 2021 @06:54PM (#27124645)
For a lot of users it’s more then enough, professional writers editors writers photographers and many many more do not need to “run arbitrary code” it’s a professional device for many professions, just maybe not for software development and maybe that’s ok?
Re:We’ll stop selling our Code Editor app for iOS soon by tacker2000 on Tuesday May 11, 2021 @05:50PM (#27124007)
So it is. The gilded cage will never rival the open field.
Re:We’ll stop selling our Code Editor app for iOS soon by Fomite on Tuesday May 11, 2021 @05:52PM (#27124028)
That depends on what field one is a professional in surely?
Re:We’ll stop selling our Code Editor app for iOS soon by nwienert on Tuesday May 11, 2021 @11:30AM (#27119293)
React native has Hermes, it’s own JavaScript engine. The key is it’s not a JIT though. It actually performs better in many facets than JSC which is impressive.

So you can run your own side process, and it can be its own JS engine.

Also, I’ll repeat this, but Im a fan of the JSC only limitation, at least for now. By not allowing v8, we are least have some hedge against a… hegemony. I like Apple over Google for many reasons, and would like to see Googles extremely hostile actions towards the web curtailed. I’ll take the trade off. I’d be less happy actually as a consumer if they allowed third party browser engines.

Re:We’ll stop selling our Code Editor app for iOS soon by kitsunesoba on Tuesday May 11, 2021 @12:00PM (#27119741)
> By not allowing v8, we are least have some hedge against a… hegemony. I like Apple over Google for many reasons, and would like to see Googles extremely hostile actions towards the web curtailed. I’ll take the trade off. I’d be less happy actually as a consumer if they allowed third party browser engines.

Similar deal with WebKit. At ~15% marketshare between mobile and desktop followed with Gecko at ~5%, it's the only real holdout against Chromium domination. If browser engines were opened up on iOS, you can bet anything that Google is going to go bananas with marketing Chromium-based Chrome for iOS and web devs will happily back those efforts, pushing most or all of that 15% over into Google's lap. At that point Mozilla will have an even more difficult time holding on as an increasing number of devs only develop against Chromium.

Re:We’ll stop selling our Code Editor app for iOS soon by moshmosh on Tuesday May 11, 2021 @12:48PM (#27120369)
Not only that, if Chrome gets enough marketshare on iOS Google could do things like taking away 5-20% of a huge fraction of iOS devices' battery life just by shipping a somewhat less efficient build, plus doing the same with any embedded versions they'd manage to convince everyone to use in their apps. I mean, Chrome's already less efficient than Safari, so that much of a penalty might happen regardless, but they could accidentally-on-purpose fail to optimize new features in their iOS code to harm their only competitor in the mobile OS arena.

"But developers and users wouldn't stand for that!" OK except I can take 4-6 hours off my M1 Macbook's battery life by using a couple Electron apps and favoring Chrome over Safari. Lots of people do exactly that, maybe not because they want to, but because they need those crappy programs to get work done.

Re:We’ll stop selling our Code Editor app for iOS soon by arvinsim on Tuesday May 11, 2021 @01:45PM (#27121101)
It must be alien to you that some people do like Chrome for what it offers.
Re:We’ll stop selling our Code Editor app for iOS soon by katbyte on Tuesday May 11, 2021 @06:56PM (#27124661)
And that comes at a battery life costC I’m slowly trying to move off it myself and it is hard with chrome lockin
Re:We’ll stop selling our Code Editor app for iOS soon by moshmosh on Tuesday May 11, 2021 @02:03PM (#27121356)
Why must that be the case?
Re:We’ll stop selling our Code Editor app for iOS soon by hparadiz on Tuesday May 11, 2021 @01:01PM (#27120486)
Safari breaks it's debug protocol all the time and is no longer compatible with Android so it's not even really an option for my workflow.
Re:We’ll stop selling our Code Editor app for iOS soon by moshmosh on Tuesday May 11, 2021 @01:08PM (#27120586)
Sure, I know lots of people in our field don't have much choice to avoid Chrome on the desktop, even if they want to (and they might simply prefer it anyway, despite the higher power use and its generally being heavier on system resource use)
Re:We’ll stop selling our Code Editor app for iOS soon by ArchOversight on Tuesday May 11, 2021 @12:53PM (#27120418)
I absolutely can not stand Chrome. I don't like how it doesn't tie in with native services like Keychain, I don't like how it logs me into the browser when I log into a website (Google)>

Lastly Chrome is power hungry. When I need to use Chrome for work, I go through my battery almost 2 - 3 times faster than when using Safari.

I much prefer the integrated experience I get with Safari and how it feels like it fits in with the rest of the OS over Chrome which does its best to tie me into Google services.

Re:We’ll stop selling our Code Editor app for iOS soon by munk-a on Tuesday May 11, 2021 @04:50PM (#27123337)
> I much prefer the integrated experience I get with Safari and how it feels like it fits in with the rest of the OS over Chrome which does its best to tie me into Google services.

That sentence is weird to me - you appreciate Safari for binding you into using in-house Apple built functionality but you begrudge Chrome trying to do the same with Google build functionality.

Re:We’ll stop selling our Code Editor app for iOS soon by ArchOversight on Tuesday May 11, 2021 @08:08PM (#27125165)
Yeah, I appreciate Safari for fitting in with the rest of the OS and integrating with the services it provides.

I can easily share my passwords with other apps/devices I own, and use it as a password manager. I don't want to cede that to another service.

So yes I begrudge Google for forcing me to use their services instead.

Re:We’ll stop selling our Code Editor app for iOS soon by simion314 on Tuesday May 11, 2021 @01:10PM (#27120618)
>you can bet anything that Google is going to go bananas with marketing Chromium-based Chrome for iOS

But Apple is a Pro at PR so Google PR should not work, the only issue would be if Safari is garbage or Google attempts to use some non standard APIs on their pages - but in this case Apple could give everyone a hand by using their expsensive lawyers and doing once in their life something good and go after Google.

Re:We’ll stop selling our Code Editor app for iOS soon by dmitriid on Tuesday May 11, 2021 @03:25PM (#27122363)
> Google attempts to use some non standard APIs on their pages

Google pushes their APIs and calls them standard. And then employs "developer advocates" to bash iOS and Safari.

Here's a non-exhaustive list of APIs that are "standard" even though both Safari and Firefox are against them: https://webapicontroversy.com/

Re:We’ll stop selling our Code Editor app for iOS soon by blacktriangle on Tuesday May 11, 2021 @04:11PM (#27122906)
What's sad is, the current duopoly actually has a nice division of labor. Google tossing any brain drippings of some random web dev into Chrome to experiment with, Apple plays the conservative role examining what is going on and waiting for things to go through a committee. The only place this breaks down is where the Google missionaries go around and lambast Apple for not rushing out to implement every half-assed feature that ships in Chrome.
Re:We’ll stop selling our Code Editor app for iOS soon by dmitriid on Tuesday May 11, 2021 @04:38PM (#27123209)
OMG I never thought about it this way. That's a very interesting and quite accurate description, thank you!
Re:We’ll stop selling our Code Editor app for iOS soon by arvinsim on Tuesday May 11, 2021 @01:42PM (#27121064)
> By not allowing v8, we are least have some hedge against a… hegemony. I like Apple over Google for many reasons, and would like to see Googles extremely hostile actions towards the web curtailed. I’ll take the trade off. I’d be less happy actually as a consumer if they allowed third party browser engines.

I'm sorry but I only see "I like X and I hate Y".

Worse, you want your preference to be forced on other people.

Re:We’ll stop selling our Code Editor app for iOS soon by Klonoar on Tuesday May 11, 2021 @03:16PM (#27122278)
This comment could be slapped on either side of the fanboys in this thread and it would still do nothing except be inflammatory.
Re:We’ll stop selling our Code Editor app for iOS soon by kmeisthax on Tuesday May 11, 2021 @12:20PM (#27120010)
It's sad that the only hedge we have against the browser monoculture problem is Safari of all things.
Re:We’ll stop selling our Code Editor app for iOS soon by fingerlocks on Wednesday May 12, 2021 @05:07AM (#27128267)
Upvoting you because I don’t think many people in this thread understand what kind of dangerous privilege is given to third party JIT web renderers.

On iOS, third party JIT is blocked by disabling mprotect + PROT_EXEC syscall, which allows execution of arbitrary blocks of memory.

No thank you, I don’t want rando apps to have that kind of power. Especially given the trade-off is some marginally different browser experience.

Re:We’ll stop selling our Code Editor app for iOS soon by saagarjha on Thursday May 13, 2021 @03:01AM (#27139236)
This is not a dangerous privilege, given that you can already ship pretty much arbitrary code to users…
Re:We’ll stop selling our Code Editor app for iOS soon by mhh__ on Tuesday May 11, 2021 @12:48PM (#27120372)
If you want to hedge against a hegemony why not allow an actual compiler...
Re:We’ll stop selling our Code Editor app for iOS soon by w0mbat on Tuesday May 11, 2021 @12:55PM (#27120436)
Because the hedgehog won’t share the hedge.
Re:We’ll stop selling our Code Editor app for iOS soon by jbverschoor on Tuesday May 11, 2021 @03:42PM (#27122564)
But you’re allowed to run a vm for running code. Like the “ish” shell
Re:We’ll stop selling our Code Editor app for iOS soon by inetknght on Tuesday May 11, 2021 @11:24AM (#27119207)
> setting aside the arguments of whether JIT code is a security concern (it is not unless your security model is one where codesigning exists to prevent the addition of new native code)

But, it is.

1) provide a JIT compiler

2) download code from the internet

3) provide code to JIT compiler

4) ???

5) Profit!

JIT code obfuscates the inspection of the app. It therefore is a security concern.

Re:We’ll stop selling our Code Editor app for iOS soon by SheinhardtWigCo on Tuesday May 11, 2021 @11:32AM (#27119328)
How is this significantly different from:

1) link JavaScriptCore

2) download JavaScript code from the internet

3) provide code to JSC

4) ???

5) Profit!

Re:We’ll stop selling our Code Editor app for iOS soon by eat_veggies on Tuesday May 11, 2021 @11:39AM (#27119432)
I suppose the difference is that JSC can only execute javascript (an interface which is relatively self-contained and which Apple can control) and not arbitrary machine instructions?
Re:We’ll stop selling our Code Editor app for iOS soon by egeozcan on Tuesday May 11, 2021 @11:45AM (#27119513)
But you can't provide a JS JIT as well.
Re:We’ll stop selling our Code Editor app for iOS soon by lacker on Tuesday May 11, 2021 @12:24PM (#27120058)
Apple makes sure that JavaScriptCore can safely run untrusted code, but they don't apply that same level of security to their native API.
Re:We’ll stop selling our Code Editor app for iOS soon by candiodari on Tuesday May 11, 2021 @01:55PM (#27121255)
JIT's can be made 100% secure. Inspection by humans cannot be made secure, for a lot of different reasons. So it's just the opposite.

I've run bots that executed code from the internet and while yes, I've had to learn some lessons the hard way, you can have perfectly safe JITs.

Re:We’ll stop selling our Code Editor app for iOS soon by saagarjha on Tuesday May 11, 2021 @04:20PM (#27122984)
If I was a malicious developer I’d just spray my app with ROP gadgets and run arbitrary native code, just somewhat slower.