[eridius]

Reading this page, it sounds very cool. It also sounds like it's heavily inspired by Swift Playgrounds, including using SpriteKit as an example.

I am a bit baffled as to why it says the Haskell code can't initiate network connections. Yeah the app is sandboxed, but sandboxed apps can easily request network access. And it seems like that's a common-enough thing to want that it should support it.

[mchakravarty]

You can request entitlements, such as network access, but you need to justify them in the App Store review process. Given that Haskell for Mac is pushing the boundaries of what is available on the Mac App Store, I wanted to err on the side of being too conservative for the launch version.

I will certainly work towards network support in coming releases.

[Tehnix]

Yeah, that one stuck to me as well. I don't know if they mean anything specific with "network connections" here, cause I see a lot of apps that talk to the outside world on the MAS.

[oisdk]

While you are allowed network-connected apps on the MAS, you have to specify the entitlement. I'd imagine that's something you'd have to justify (or at the very least you'd get more scrutiny and a longer approval time).

[eridius]

I think it just means the app didn't request the ability to make network requests. I just don't understand why not.

[QuantumRoar]

Here's a cynical comment:

Long term monetization will only work if he can ship version 2 at some point to pull in some more money from the same people who bought version 1 (and the same thing with version 3). The choice of not shipping obvious features of an IDE is in order to have better differentiation between versions.

Though, maybe there is really a good reason for that involving some of Apple's policies. I heard they teach the developers all kinds of lessons when it comes to how a program should be made... who knows...