Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Wangle – an asynchronous C++ networking and RPC library

code.facebook.com

Post reply on HN
Print view View original

1–10 of 78 posts

Re: Wangle – an asynchronous C++ networking and RPC library

#6

Post by tptacek »

brandeis wrote: post #5
swah wrote: post #4

Earlier quoted context omitted.

Me too - and I don't even know C++.

Go is a toxic language, I wouldn't necessarily use C++, but jumping on the go bandwagon is going to get you burned.

Articulating concerns with Go is a legitimate (if, for this particular thread, unproductive) way to use HN. Writing comments like "Go is a toxic language" is not; it's morally indistinguishable from trolling.

The comment rooting this thread, suggesting the use of Go instead of C++, was also unproductive. I'm glad to be done with the C++ part of my career, but still happy to read about ambitious new libraries built in it. That upthread Go comment is the kind of tangent-driving chaff that made Slashdot unreadable. But this comment is even worse.

Re: Wangle – an asynchronous C++ networking and RPC library

#8

Post by thepumpkin1979 »

I just tried to compile folly in OSX and it fails to compile with homebrew. https://github.com/facebook/folly/issues/400

Also, Once I manage to compile folly and then wangle, what kind of database drivers can I use in conjunction with this? Would I shoot myself in the foot if I use this with libpq under CPUThreadPoolExecutor?

Same with Rust and dlang, I'm not sure how to apply the freedom to have pluggable executor into something useful in real life, I think this is the main reason Golang is killing it and it keeps getting better.

For now I have my money on Go but can't wait for http://www.ponylang.org/ to become stable.

Edit: Issue reported has been closed, I can now proceed to install wangle https://github.com/facebook/folly/issues/400

Edit 2: Found another issue, this time installing wangle https://github.com/facebook/wangle/issues/37

Re: Wangle – an asynchronous C++ networking and RPC library

#9

Post by pcwalton »

thepumpkin1979 wrote: post #8

I just tried to compile folly in OSX and it fails to compile with homebrew. https://github.com/facebook/folly/issues/400 Also, Once I manage to compile folly and then wangle, what kind of database drivers can I use in conjunction with this? Would I shoot myself in the foot if I use this with libpq under CPUThreadPoolExecutor? Same with Rust and dlang, I'm not sure how to apply the freedom to have pluggable executor i…

Go uses synchronous I/O backed with an M:N implementation. Rust and D use synchronous I/O backed with a 1:1 implementation. Semantically, there is no difference between the two. The difference is in the implementation, and 1:1 threading is not as slow as you think on Linux.

Re: Wangle – an asynchronous C++ networking and RPC library

#10

Post by tptacek »

pcwalton wrote: post #9
thepumpkin1979 wrote: post #8

I just tried to compile folly in OSX and it fails to compile with homebrew. https://github.com/facebook/folly/issues/400 Also, Once I manage to compile folly and then wangle, what kind of database drivers can I use in conjunction with this? Would I shoot myself in the foot if I use this with libpq under CPUThreadPoolExecutor? Same with Rust and dlang, I'm not sure how to apply the freedom to have pluggable executor i…

Go uses synchronous I/O backed with an M:N implementation. Rust and D use synchronous I/O backed with a 1:1 implementation. Semantically, there is no difference between the two. The difference is in the implementation, and 1:1 threading is not as slow as you think on Linux.

Why are we talking about Go, Rust, and D on a thread about a new C++ library? I mean, I know the answer, but I wish we weren't.

I ordinarily wouldn't care, but I usually feel like I have something to learn from ambitious networking libraries even when they're written in languages I prefer not to use.

Post reply on HN