abseil-cpp VS OpenFrameworks

Yeah, it's nice! And Abseil does it, IFF you use LLVM libc++.

https://github.com/abseil/abseil-cpp/blob/master/absl/string...

The standard adopted it as resize_and_overwrite. Which I think is a little clunky.

This may be confusing to those familiar with Google's libraries. The baseline is the Go BTree, which I personally never heard of until just now, not the C++ absl::btree_set. The benchmarks aren't directly comparable, but the C++ version also comes with good microbenchmark coverage.

https://github.com/google/btree

https://github.com/abseil/abseil-cpp/blob/master/absl/contai...

An implementation of call_once that accommodates callbacks that throw: https://github.com/abseil/abseil-cpp/blob/master/absl/base/c...

I wouldn't say it's that cryptic. It's just a few bitwise rotations/shifts/xor operations.

You can see hashing optimizations as well https://www.deepmind.com/blog/alphadev-discovers-faster-sort..., https://github.com/abseil/abseil-cpp/commit/74eee2aff683cc7d...

I was one of the members who reviewed expertly what has been done both in sorting and hashing. Overall it's more about assembly, finding missed compiler optimizations and balancing between correctness and distribution (in hashing in particular).

It was not revolutionary in a sense it hasn't found completely new approaches but converged to something incomprehensible for humans but relatively good for performance which proves the point that optimal programs are very inhuman.

Note that for instructions in sorting, removing them does not always lead to better performance, for example, instructions can run in parallel and the effect can be less profound. Benchmarks can lie and compiler could do something differently when recompiling the sort3 function which was changed. There was some evidence that the effect can come from the other side.

For hashing it was even funnier, very small strings up to 64 bit already used 3 instructions like add some constant -> multiply 64x64 -> xor upper/lower. For bigger ones the question becomes more complicated, that's why 9-16 was a better spot and it simplified from 2 multiplications to just one and a rotation. Distribution on real workloads was good, it almost passed smhasher and we decided it was good enough to try out in prod. We did not rollback as you can see from abseil :)

But even given all that, it was fascinating to watch how this system was searching and was able to find particular programs can be further simplified. Kudos to everyone involved, it's a great incremental change that can bring more results in the future.

Check out https://abseil.io. It offers absl::optional, which is a backport of std::optional.

Not exactly VJ, but could be used for it. https://openframeworks.cc

Since you have C# experience, take this time to learn more about C++ while you continue to look. While yes, it is very easy to write bad code, it's not a huge deal since you just graduated and are just hacking around. Plus there are a lot of helpers these days to make writing bad code a little less likely.A former mentor of mine gifted me "C++ Without Fear" by Brian Overland which I can recommend. It's not too expensive, I think it was $25 or something like that, likely less used. Also comes in E-book form.If you'd like a gentler introduction to C++, may I recommend openFrameworks?

Have you come across openFrameworks (https://openframeworks.cc/) or Cinder (https://libcinder.org/)?

Not sure it checks all your boxes, but check openFrameworks?

I recently heard of openFrameworks which should make it pretty easy to make your game. It handles putting together a bunch of other libraries and window management so you can focus on drawing some shapes on the screen and handling user input. Sounds like love2d but all C++.

let me know if I can help out - also checkout the forum at openframeworks.cc - the people there are very friendly and helpful - especially with people that are completely new to oF...

I mean, https://www.libcinder.org and https://openframeworks.cc have been mainstays of the creative coding industry for a long time now. A Rust take on the problem shouldn't be too surprising.