Some thoughts on the Rust Library Team and its mission: http://aturon.github.io/blog/2018/01/16/libs-mission/ …
Not sure if this post is being discussed somewhere, but the comment about -sys crates resonated with me. There's currently this weird repetition of work on core crates shared by servo and other projects such as piston.
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Main example is freetype and fontconfig-sys crates. I had to jump through hoops to get this these working correctly for Alacritty.
-
Piston has nice high-level FreeType bindings, but I had to couple it with servo's freetype-sys for some reason. I'll can go into details some other time. I forget the exact issue.
-
As part of Alacritty, I've developed high-level fontconfig API in Rust, but have been unable to publish it due to this weird redundancy of sys crates.
-
The point I'm getting at is there's definitely missing sys crates, but there's also redundancy of existing sys crates which makes room for a lot of confusion
End of conversation
New conversation -
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.