Live data from Hacker News

Wangle – an asynchronous C++ networking and RPC library

code.facebook.com

11–20 of 78 posts

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

#11
post #3

Had to look up the meaning of wangle. "obtain (something that is desired) by persuading others to comply or by manipulating events." Does anyone know where facebook is coming up with all these words - folly/wangle?

Folly is a common word, I think. As non-native English speaker I know the meaning of folly. But I saw wangle for the first time.

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

#12
post #3

Had to look up the meaning of wangle. "obtain (something that is desired) by persuading others to comply or by manipulating events." Does anyone know where facebook is coming up with all these words - folly/wangle?

I was going to correct you and say you meant "wrangle". Turns out they can have the same meaning! Wonder if there are other examples of two words being one letter off that mean the same thing.

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

#13
post #3

Had to look up the meaning of wangle. "obtain (something that is desired) by persuading others to comply or by manipulating events." Does anyone know where facebook is coming up with all these words - folly/wangle?

"Folly" is a relatively common English word. "Wangle" is less common but I still see it from time to time.

What I find more interesting than the naming is FB's willingness to remove features from Folly as they are made redundant by Boost or std. I'm unaccustomed to such a lack of arrogance from a major player.

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

#14
post #10
post #9

Earlier quoted context omitted.

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.

For what it's worth, I try to not bring up Rust in threads about other languages; it just happens that most threads about Rust appear in threads about other languages.

I would rather talk about the implementation of async I/O too.

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

#15
post #3

Had to look up the meaning of wangle. "obtain (something that is desired) by persuading others to comply or by manipulating events." Does anyone know where facebook is coming up with all these words - folly/wangle?

Folly is a common word, I think. As non-native English speaker I know the meaning of folly. But I saw wangle for the first time.

Yup, I know folly as well (non-native speaker as well). But it doesn't make sense to name a library 'folly' does it?

What I was wondering is if this some self-deprecating humor or these words are popular phrases from some popular book/meme/play.

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

#17
post #6
post #5

Earlier quoted context omitted.

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…

Point taken. Made comment less polarizing.

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

#18
post #2

In 2016 I would write networking and RPC in go.

"networking and rpc" must be written in the languages your server and client are written in, (or something compatible).

Writing a networking library in Go does nothing for Facebook if their services are written in C++.

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

#19
post #13
post #3

Had to look up the meaning of wangle. "obtain (something that is desired) by persuading others to comply or by manipulating events." Does anyone know where facebook is coming up with all these words - folly/wangle?

"Folly" is a relatively common English word. "Wangle" is less common but I still see it from time to time. What I find more interesting than the naming is FB's willingness to remove features from Folly as they are made redundant by Boost or std. I'm unaccustomed to such a lack of arrogance from a major player.

Doesn't removing features break backward compatibility?

My favorite C++ library is Qt; they never remove public API for that reason. In Qt world, we update regularly to get the bug fixes and other features. Last thing I want to do is port my code to some other new API to update the library.

Post reply on HN