@krzyzanowskim Im sincerely confused. You tell us that @compnerd claims that Swift on Windows is further than on Linux, but you won’t give any kind of backup on your claim on that? Why? 🤔
@ctietze That you cannot easily embed PHP as a library and integrate it as a scripting language. Similar to what you do w/ JSCore.
Pretty much any scripting language has that but PHP.
@ctietze I've proactively tried to integrate PHP into Swift about 2 years ago, didn't get it to work. And I've done a lot of bridges before, Python, SpiderMonkey, JNI, yes, even Guile! 🙈
One thing I don’t get: what’s the downside of Apple allowing macOS to run in a VM on iPad? It doesn’t take anything away from those who don’t want to use it. You just ignore the feature and keep using your iPad as-is.
Apple doesn’t even need to build it themselves, just allow the tech they already have to run and be allowed on the App Store, that way someone like Parallels can come along and provide it (which would also allow Linux, Windows, etc)
@pilky@lapcatsoftware Having two operating systems on such hardware is certainly not optimal. E.g. you'd have to sync all your iCloud stuff twice. UX would be inconsistent.
Why even run macOS in a VM, just run macOS directly on the hardware and have it run iOS apps, which - as a matter of fact - it already does.
@finestructure@pilky@lapcatsoftware But that would be an artificial limitation that wouldn't have to exist. I can sign into iCloud in a VMware macOS VM though (running on macOS). Same works in iOS simulators on macOS.
@finestructure@pilky@lapcatsoftware Maybe it was dropped later? But I definitely have this running w/ sth like macOS 10.12(?) which I use for ScanSnap scanning.
30 hours into #Everspace2 and it's great fun. It's not the most compelling story in the world but the graphics and the mechanics are great. An excellent space shooter, and native to the Mac to boot.
I'll be damned if Rockfish Games aren't looking into or even already working on Everspace for the Vision Pro. Feels like a no brainer. Surely Apple must be talking to them about it?
@davidbures Could it be that you are beyond a 10 item limit? Maybe put them in Groups.
I think the limit is gone for View's now, but maybe not for those.
Inspired by @Migueldeicaza , I was thinking, again, about what would be required to support a full IDE experience on an iPad. And the propects are grim.
LSP is just fundamentally incompatible with iOS. And even with spec changes (which I have roughly outlined) that could be hard justify, it would still require enormous work from each server implementation to support.
@ctietze@mattiem I think theoretically that could work, you would need to get some Posix kernel/OS running within Wasm. Which is just another computer w/ a different arch?
It just doesn't make a lot of sense, IMO 🙂
@mattiem@Migueldeicaza I would put that the other way around: "iOS is just fundamentally incompatible with LSP" (or other advanced software 🙃
The question is why things would have to run locally, I was always wondering whether things like Xcode Cloud are preps for exactly that.
I'm not sure whether LSP is strictly necessary for something Xcode like. I'd think Swift stuff could just stay in-process. Maybe in a dedicated thread.
VSCode style advanced support for "any language" is a little different.
@krzyzanowskim It is not impossible, e.g. one option mentioned is Wasm. Though of course the basic idea of that being necessary is wild ;-)
Maybe we get at least XPC, that would benefit forking off stuff that doesn't expect clean shutdown (I assume the Swift compiler is that way?).
@krzyzanowskim Also the most funny thing is: Why would you ever want to do this to you? We spend wayyyyy too much time discussing that, no iOS powered device is suitable for serious coding in the first place (AvP, maybe?).
Folks who squash their #git merges, I’m curious why you are making that trade-off. I’m guessing the pro argument is a cleaner merge graph?
The big argument against it for me is that you lose granularity for git bisect. I've often been able to narrow down breakage (sometimes long past the merge) due to individual commits in the merge. If I'd merged in a giant blob all I'd have had to go by is that giant blob. (1/2)
@finestructure@fabianfett It is still a tooling issue, I don't see why you'd ever want to throw away history.
The fixit commits are hidden exactly the same way in the collapsed mode and you could also just hide them if you wanted to, and the tool allows for that.
@schwa@jackbrewster I think people actually did think a lot about this. And actually (not) used iPads for a long time to understand the issue.
iOS is a shrunk down OSX built specifically for very weak hardware. Scaling that up again is kinda funny (and didn't work).
In a fit of madness I've agreed to give an internal talk about advanced Swift at my company. Has anybody got any favorite Swift tricks they'd like to share?
@cocoafrog@ctietze@nicklockwood For this you can also use sequence, like for item in sequence(item) { $0.parent } { ... }.
But I also like the where, though I don't actually use it that often.
