Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ygoldfeld
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
1.
▲
by
ygoldfeld
2y ago
Hi again! > I hoped you had an epiphany and found a nice solution for the raw-pointer problem without the need to change them and we could borrow that idea :) Well, almost. But alas, I am unable to perform magic in which a vaddr in proce
2.
▲
by
ygoldfeld
2y ago
We are doing it with fancy-pointers (yes, that is the actual technical term in C++ land) and allocators. It’s open-source, so it’s not like there’s any hidden magic, of course: “Just” a matter of working through it. Using manual mapping (sa
3.
▲
by
ygoldfeld
2y ago
At the risk of almost-spamming -- this post has taken off, which is sweet, and I have noticed some trends about what seems to interest readers which may not be placed as prominently up-top as would fit this audience. To wit: the API Overvie
4.
▲
by
ygoldfeld
2y ago
While I wouldn't dream of claiming Flow-IPC will fit every IPCer's priorities, nor of trying to change yours or anyone's, nor of debating about what is trivial versus hard -- it should at least be easily possible to know wh
5.
▲
by
ygoldfeld
2y ago
It lives! https://news.ycombinator.com/item?id=40028118
6.
▲
by
ygoldfeld
2y ago
Oooh, so close. We’ve got the advertisement/discovery and messaging for sure. Concretely what it would take to port it to those OS: https://github.com/Flow-IPC/ipc/issues/101 Given a couple weeks to work
7.
▲
by
ygoldfeld
2y ago
A couple - 1. The obvious one is “just” extending stuff internally working via Unix domain sockets to TCP sockets. Various internal code is written with an eye to that, including anticipating that certain operations (such as connect) that a
8.
▲
by
ygoldfeld
2y ago
Oh… Sys V SHM… not POSIX. Old-school.
9.
▲
by
ygoldfeld
2y ago
Interesting! I'd best write this down. Current notes on macOS and Windows port work: https://github.com/Flow-IPC/ipc/issues/101 (<= https://github.com/orgs/Flow-IPC/discussio
10.
▲
by
ygoldfeld
2y ago
Reply co-signed! That said, I'll add that my Manual ( https://flow-ipc.github.io/doc/flow-ipc/versions/main/genera... ) gets into the topic of safety (with a few words on how this differs from secu
11.
▲
by
ygoldfeld
2y ago
I think that (whether a native-struct versus a capnp schema-based struct = helps/how much) is a general question of what kind of serialization is best for a particular use-case. I wouldn't want to litigate that here fully. Persona
12.
▲
by
ygoldfeld
2y ago
Whoa (again), super-cool, appreciate that.
13.
▲
Show HN: Comprehensive inter-process communication (IPC) toolkit in modern C++
(github.com)
88 points
by
ygoldfeld
2y ago
|
57 comments
14.
▲
by
ygoldfeld
2y ago
1. You’re welcome! 2. I too would like to explore other developments - not that I think C++ sucks or anything (not that I don’t think it doesn’t suck sometimes!) - Rust and all. Here’s hoping 3. At points during development of this, the ol’
15.
▲
by
ygoldfeld
2y ago
(Akamai owns Linode and uses the blog on Linode.com as a developer-oriented blog. So that’s why the link is to there.)
16.
▲
by
ygoldfeld
2y ago
Whoa. I’m the lead developer on this - I got to this post totally by accident: was googling for my own Show HN post about this from a couple days ago - and it took me here without my noticing. There’s some discussion on it in Show HN, and o
17.
▲
by
ygoldfeld
2y ago
You’re welcome. But I must tell you, at work I asked how my answers are, keep me honest. So a coworker looked at this thread and was just like, “dude just get to the point, no one wants to read all that.” And then explained that in huge det
18.
▲
by
ygoldfeld
2y ago
Roger dodger. For what it is worth at this time - obviously acting on the following statement will require some level of trust - It is very much ready to use with boost.asio. (I know that, because I myself use boost.asio religiously. If it
19.
▲
by
ygoldfeld
2y ago
Versus iceoryx (the C++ version, not the Rust-oriented iceoryx2): TL;DR: So far, it looks super-sweet (as well as mature, already supporting macOS for example). However more of an investment to use than is Flow-IPC, with a central daemon an
20.
▲
by
ygoldfeld
2y ago
Appreciate your time! And, naturally, this was the question I expected to pop up once I was able to work through everything required internally here at Akamai to actually put this guy out in public. Wouldn't it be sad :-( if the same t
21.
▲
by
ygoldfeld
2y ago
Indeed, examples from every angle are probably the one deficit of the existing documentation. There are a couple, such as the perf_demo described in the blog post. I’d like to add ones showing integration with - epoll based event loop - boo
22.
▲
by
ygoldfeld
2y ago
It's so hard to communicate this stuff in writing! There are several angles of potential interest; I wish I could simply chat in-person with anyone curious, you know? Of course that is impossible. (I'll do my best here at HN and t