What's everyone working on this week (2/2019)?


New week, new Rust! What are you folks up to?


Decide a proper syntax for CeX 0.3.0-alpha and release 0.3.0.

Then make progress in the enum_exchange pre-RFC


Implement streaming json parser and define sort order for json


I was working on audio support for Tetra, but a few oddities with Rodio are making it tricky for me to get the API I want. I’m a little tempted to just bind to OpenAL (via Alto?), since that definitely does everything I want, but adding another C dependency wouldn’t be ideal…

I’ve been procrastinating on that by adding custom shaders (which just got released in 0.2.5), which has been fun. Next thing I want to take a look at is the rendering performance - it’s currently quite heavily CPU-bound by the calculation of the transform matrix, which is a pain.


Getting basic integration between rust-content-security-policy and servo working.


Mastering Rust by developing a fun project: todo list manager for terminal . The project is in its early stage, though it is usable


Optimize v_escape in several cases of the function with avx.


Working on my Rust binding for TVM runtime so that one can deploy deep learning models with Rust :slight_smile:


I have been working on seekcrate, my first Rust program (hence the quality of the code).

It’s a toy program to see if one could use the result of the Search Engines to search for crates. Fact is that we will never beat Search Engines for contextual search, so it was worth a try. The results are amazing, the only problem is that I currently use scraping, which is against Google’s ToU I think… I tried their API, creating an account and stuff, but the results are really really disappointing. If anyone has experience with Search Engine APIs in general and if there are strategies to improve the results, I’d be open for a chat !

If you want to try, please feel free I’m open for feedbacks.

My next mission are:

  • implement the same thing for DuckDuckGo
  • find a better way to correlate GitHub repo address and actual crate name
  • achieving the same results through APIs


Rewriting most of the build.rs for the project Rutie. The cflags on Linux is weird with Rust. The system’s installed libruby takes priority over any linker search path arguments so creating a symlink to it in target/<PROFILE>/deps is required for everything to work smoothly. There’s a fair bit more involved to it but I’m making pretty good headway after much work.

Update: Finished the rewrite of the build process. Opened an issue on rust-lang/rust #57550 on Rust linker -L cflags behaving differently between Mac and Linux.


I’m working in a small library to handler http objects to use after in my framework blocker message Malaga.



Getting oxidizeconf.com news out. We have a venue and a date and now the fun part (CFP and stuff).


If it would be cheaper surely I would attend it :pensive: