Some of these with the letterpress printing or embossed images have a lovely physical and 3d quality
527 karma · joined January 24, 2010
The vfx business was and continues to be a "challenging field to work in", but man what an incredible experience it was working there.
A friend has journals a few years old and on the right 2/3rds of the pages the writing is nearly gone (theory being maybe that side got warmer, but not certain)
Tidepool is also trying to take the loop project and get a version of it FDA approved.
Both of the open source projects require you to do the work and actively take control of your setup (a cgm plus pump plus phone). They have really nice support communities. I would never go back to not using Loop.
https://www.unrealengine.com/en-US/blog/unreal-engine-5-is-n...
This page has interesting info. https://www.tms.org/pubs/journals/JOM/9809/Verhoeven-9809.ht...
It seems likely 3 factors were important in creating "real" Damascus steel. The key one being the mixture of elements in the raw ore that specifically came from the mines in a specific region of southern India, and once that ore ran out the "secret was lost". There's also the knowledge of the forging process - namely the temperatures, heat treatment processes used, and what organics (aka carbon) got mixed in.
"“Like somehow we’re hurting some employees? We’re not,” Catmull said. “While I have responsibility for the payroll, I have responsibility for the long term also,” Catmull said. “I don’t apologize for this."
Along with automatic synthesis of all the operators, c++ 20 also clarified rules about overload-matching and automatic construction of objects for purposes of comparison, so you don’t have to write the friend methods to for example compare int to your type if you have trivial int-taking constructor for your type. Also if your == operator or != is more efficient than a full lexigrapgical comparison the compiler will now do the right thing
http://boost.2283326.n4.nabble.com/CMake-Announcement-from-B...
It appears further discussions are underway, but I don't know what that means in terms of how quickly they will switch. https://groups.google.com/forum/#!topic/boost-steering/5ifzu...
In terms of bjam vs. cmake... I get why the boost library has needed a custom build tool chain (if you're curious just look at the complexity in headers in trying to work around various template bugs in different compiler versions, or the many many many ways to request naming of the generated libraries). I should have been less snarky in my first post. If boost does migrate to cmake I predict it will be quite a gnarly set of cmake logic.
A group/language/team decides "that's it, I hate build tool X, we're going to solve this problem", and they go build their thing, but they care about different details and make some things easy, handle some things automatically, and leave other things as "just don't care" with the resulting tool ends being just like all the previous ones.
I'd be willing to wager lots of money that in future years there will be many more build systems, and they too will perfectly match their predecessors.
Will the SpaceX system use frequencies that allow decent reception and transmission (to the sats) if you're physically in a city? If you're indoors?