TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

AllSystemsGo: Varlink Now [video]

3 点作者 vyskocilm8 个月前

2 条评论

ptx8 个月前
So the advantage is supposedly that it&#x27;s extremely simple (just NUL-terminated JSON over a stream socket!) except that, when you look at the spec, it&#x27;s actually not that simple, so they have only implemented a subset, and then they have also extended it with more features, so in the end it&#x27;s not simple and not really even Varlink?<p>And it&#x27;s now 40% slower at serialization and it can&#x27;t embed binary data, but that&#x27;s OK because now &quot;web native folks&quot; can be OS infrastructure developers without learning a new format? Except the interface definition format, which is not JSON, but for some reason the wire format has to be.<p>And all the D-Bus stuff, with all the problems enumerated in the presentation, will still be kept around, so we&#x27;ll have D-Bus + systemd&#x27;s &quot;quite different&quot; D-Bus variant + Varlink + systemd&#x27;s Varlink variant that &quot;does not bother with&quot; the spec but has &quot;additions&quot;, all at the same time.<p>It doesn&#x27;t sound &quot;extremely simple&quot; to me.
vyskocilm8 个月前
Why bother with Varlink IPC, and why now?<p>The Varlink IPC has been around for a while, but recently we started using it heavily in systemd. In this talk I&#x27;d like to explain what Varlink IPC is, and why we are now adopting it so heavily. And I also want to explain why I think that Varlink is a good candidate as IPC of choice for any Linux software, both low-level and higher-level. We&#x27;ll compare it with D-Bus in particular, and highlight where it shines (and where it doesn&#x27;t shine so much).