Don’t browsers need to abstract over multiple OS’s at once though? :)
-
-
Sure but our IPC on macOS makes us unable to do proper multiprocess and have niceties such as private GPU textures.
1 reply 0 retweets 0 likes -
Webkit works on multiple OSes and yet properly uses XPC services on macOS.
1 reply 0 retweets 0 likes -
OK, then maybe ipc-channel should work differently. But I strongly believe there should be a way to write IPC and have it work cross-platform.
1 reply 0 retweets 2 likes -
If you say “sorry, you have to write custom IPC for macOS because maybe you might want to share a texture” then Rust users are just not going to write multiprocess programs.
1 reply 1 retweet 1 like -
Current state is “sorry but to share textures you need to make them global so that all processes can read it”, that doesn’t sound good either.
1 reply 0 retweets 2 likes -
We shouldn’t give up on a cross-platform IPC abstraction just because of texture sharing, which is something that basically only browsers and window managers need to do anyway.
1 reply 0 retweets 1 like -
Sure, but Servo maybe shouldn't be using ipc-channel then.
2 replies 0 retweets 0 likes -
That being said, it's not just about texture sharing, ipc-channel IIRC works on macOS bv replacing the bootstrap Mach port and that's quite tacky in my book.
1 reply 0 retweets 0 likes -
It’s easy to bash ipc-channel, but you know, without it Servo would still have been single process. You realize that it was an uphill battle getting anyone to care about multiprocess at all.
2 replies 0 retweets 0 likes
So no, I’m not apologizing for ipc-channel.
-
-
Good, nobody asked you to apologise.
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.