What would it need to break out more? There’s a vscode extension with full lsp and dap integration and even tests And my worktop (win11), the installation was way easier than rust for me It has native interop with c/++ with no ffi needed and as of the other day experimental JNI interop too
Swift can just straight-up natively call C (like, directly without FFI) so it's def worth looking into for that I'm also curious how suitable it'd be for real-time workloads nowadays with the embedded language subsets and noncopyable structs (which are both somewhat recent)
同じリンクかもしれないけど… フィードは、Twitterでいうリストやモーメントに近いが、正確には検索結果の表示である とあります。 たとえば、○○って単語が付けられてるポストだけを表示させる設定しておけば、○○が入っているポストのみ別タブで閲覧することができます。 しかも他人と共有できる…というのがフィードの強み note.com/ffi/n/n2781f...
Blueskyが楽しい。のびのびとSNSを遊んでいる。 Blueskyにはフィードというのがある。これが面白い。 フィードには、ユーザーから投稿されたpostが任意の条件にしたがって抽出されて並ぶ。旧Twitterの「リスト」に似ているし、かつてあった「モーメント」にも少し似ているが、実際のところは「検索結果の表示」だ。 「保存された検索設定にもとづく検索結果の表示」でしかないはずのフィードな...
for a genuine jump-scare, well, I'll just say this code *is* pretty thoroughly documented. (cc @lucia.red who I think is about to fall off the notifications of this reply chain)
Ario Bayu Pastikan Tak Ada Konflik Kepentingan di Penjurian FFI 2024 - https://seleb.tempo.co/read/1921342/ario-bayu-pastikan-tak-ada-konflik-kepentingan-di-penjurian-ffi-2024
Ketua Komite FFI Ario Bayu mendorong mekanisme baru dalam FFI 2024 untuk memastikan proses penjurian yang lebih objektif dan netral.
Ario Bayu Pastikan Tak Ada Konflik Kepentingan di Penjurian FFI 2024 - https://seleb.tempo.co/read/1921342/ario-bayu-pastikan-tak-ada-konflik-kepentingan-di-penjurian-ffi-2024
Ketua Komite FFI Ario Bayu mendorong mekanisme baru dalam FFI 2024 untuk memastikan proses penjurian yang lebih objektif dan netral.
FFI->dylib can work. Starting a subprocess and talking to it via stdio handles has a lot of flexibility. But for both methods, who is responsible for shipping security updates to the binaries? I can see why a lot of devices like to look like serial ports (or mass storage devices).
After we moved our client/server from being implemented in JS and C# to Rust, I tried moving our client libraries to being FFI on top of rust. This was a NIGHTMARE. Trying to balance async runtimes on top of other async runtimes, etc. Will never do that again, set us back at least a year in dev.
For configuring/running the server, we have two solutions: - "Initface Engine", which is just a CLI, but is also built as a library - "Intiface Central", which is a flutter app using flutter-rust-bridge (so basically FFI) to the engine library Both of these have worked well for us.
Great work in Sao Tome and Principe🇸🇹... We are about to sign follow up grant with FFI...
