/* to-date I have never met a "Software Engineer" who could…

That's hilarious because C is literally the easiest thing to use for hardware... IMHO

hahaha yeah things get overcomplicated fast.
Give me ladder logic or function block diagrams any day of the week.

agreed but they all depend on the boost libs and c++ templates for job security

https://github.com/ReactiveX/RxCpp Rx for C++ is what I use if I have the choice now, because it's all the same combinators, available in any language. If it has to be optimized later, ok, it's easy to contain optimizations inside the monads.

Using a library like this allows one to compose all those things that one might have depended on from 3rd parties. No point. It makes C++ high level abstractions work as fast as low level. In fact Rx in C++ is probably the most powerful implementation.

I'm more proficient in C#, however, it's always been the plan to port to C++ 14. Once the code is in the form I want, it will be very simple to port to C++ 14 or Javascript or whatever Rx implementation.

C++ 11 and above move semantics and lambas and all that goodness, allows lambda expressions with safe pointers that won't leak memory and won't overflow, and 0 perf hit.

https://www.youtube.com/watch?v=QkvCzShHyVU&feature=youtu.be From the RxCpp samples, a real time Twitter analysis app.

if you're defending C++ you're wrong

cpp w/ intelligent use of https://en.m.wikipedia.org/wiki/X_Macro running strict c89 vs c++'s latest whatever wrapped w/ a Turing complete template language... come on

if you're using c++ at all as a primary language then you are completely cut off from actually optimizing C https://twetch.app/t/8d1f79ab62386e27eb29755bc288d180897794115da4432defbdfbad4ee954d7

kDB is for db's of any size. especially big ones. 1TB and up. very fast. very powerful.

most kx customers are from 10TB to 1PB.

each k process maps up to 128TB so an online PB database requires 8 k processes.

each hdb process can serve a million queries per second or query a billion records per second.

each rdb process can process 100MB per second (one million transactions per second).

any C++ optimization is relatively slow compared to bleeding edge C optimizations

if you look at his C code from the 80s when he wrote "Magic Money" the C is beautiful... the C++ for the original client was a means of masking identity

*90s

*this* is said w/ respect to be clear... I simply want to be clear as to why I "fucking hate that language" : isn't personal

:-) I'm not defending C++ over C, and you'll be pleased to know: "The Reactive Extensions for Native (RxCpp) is a library for composing asynchronous and event-based programs using observable sequences and LINQ-style query operators in both C and C++.

Header only C library, gets you the combinators you'd have in Haskell or whatever. Fun times.

https://channel9.msdn.com/Shows/C9-GoingNative/GoingNative-9-LINQ-for-C-Native-Rx-RxC-Meet-Aaron-Lahman

https://github.com/auxon/RxC

wild

Ditto, I hate Perl, but I don't hate it in the hands of someone like Damian Conway: "temporally quaquaversal virtual nanomachine programming in multiple topologically connected quantum-relativistic parallel timespaces" https://youtu.be/HzTjPx4NIiM

Here's the only other 2 versions on YouTube that I've found:

https://youtu.be/ZpInOI4o2LY
https://youtu.be/ORjyXcLDd9M

I think the original is the most extensive version.