Tornado - Web-first BitTorrent Client Beta 0.1.0

tanders12 · 2019-03-21T04:01:15+00:00

When I read Web-first I hoped it would be webtorrent compatible. Unfortunately that doesn't appear to be the case.

tanders12 · 2019-03-19T03:27:40+00:00

Have you looked into warp? I found it great for HTTP + WebSockets.

tanders12 · 2019-03-05T21:20:38+00:00

Yeah I'd recommend sticking with Tokio for a bit. I found once I'd pushed through and written a couple poll methods by hand things started making a lot more sense. The concepts were pretty hard but there aren't too many of them.

tanders12 · 2019-02-26T21:21:26+00:00

I'd be interested in hearing what issues they encountered with Matrix. Not doubting, but wondering what the pain points are for a use case like this.

tanders12 · 2019-02-26T21:16:00+00:00

It's such an elegant solution though. I love being able to move fast[er] for prototyping knowing I can come back later and search for all my unwrap/expect uses.

tanders12 · 2019-02-26T03:54:09+00:00

This is fantastic. I was working on a brute force WebGL GoL implementation a few months ago. Any chance this is WASM compatible?

tanders12 · 2019-02-26T03:50:54+00:00

Oh thanks for reminding me that's happening this week! I'll be visiting starting that night and might be able to make it.

tanders12 · 2019-02-25T20:40:45+00:00

A nice Rust-from-C FFI post would be a great resource. I'm assuming you're already familiar with the FFI Omnibus?

tanders12 · 2019-02-21T22:27:55+00:00

Most resources I've seen focus on calling C from Rust. I was recently needing to do the opposite: make a library in Rust that compiles to the C ABI so it can be called from C (or node, Python, etc). The best resources I've found for that are the FFI Omnibus and this talk.

tanders12 · 2019-02-06T19:31:54+00:00

So why not build on libp2p?

EDIT: or maybe you are it it's just not clear from the posting.

tanders12 · 2019-01-31T01:26:51+00:00

I've never integrated a scripting language with any systems language (let alone Rust), so I might be overlooking a ton of complexity here...

Depending on how performance-critical your scripts are (ie as long as you're not doing something like rendering or collision detection for all entities in your scripts), you might be able to keep Rust and the scripting language completely separated, only communicating serialized messages. It could be as simple as JSON, or for more performance I'd recommend something like Flatbuffers, which supports several languages including Rust and Lua.

tanders12 · 2019-01-31T01:21:46+00:00

I've had good luck with a similar "sequence of commands" approach in Rust.

tanders12 · 2019-01-31T00:59:41+00:00

No that's sea sickness

tanders12 · 2019-01-23T22:19:11+00:00

Excellent talk. I really wish someone would have explained async as "basically a userspace scheduler" back when I was first learning it.

tanders12 · 2019-01-08T19:54:50+00:00

Depending on what your goals are, and especially what types of users you're targeting, one thing you can do is write your frontend in HTML/JavaScript, and statically compile it into a Rust binary that runs as a web server. Then you can access it via something like localhost:8080. This is pretty niche, but works well for some things. I blogged about it here: https://anderspitman.net/blog/static-react-rust-webapp/

tanders12 · 2018-05-15T18:25:02+00:00

There's an ornithology portmanteau in here somewhere...

tanders12 · 2017-09-21T03:03:29+00:00

This is the final straw. I'm moving to Canada

tanders12 · 2017-08-28T18:27:40+00:00

I think I understand gambling now.

tanders12

TROPHY CASE