CppCon 2018: Juan Pedro Bolivar Puente “The Most Valuable Values”

[@loganpowell]

This guy needs to be on the Standards Committee

[@benisrood]

Too "dangerous" for the Committee. Also, he probably doesn't want to spend the enormous amount of time involved, anyway.

[@jjurksztowicz]

Great point about the assumptions about the high and low levels of system design. I think that object semantics work best when sandwiched between layers of value semantics.

[@schusselhast1788]

I would argue that the sandwich is the other way round: Value semantics sandwiched between object semantics. Because the CPU works with object semantics and the real world works with object semantics. And our programs live in between :D

[@DomainObject]

Fantastic talk!

[@MrAbrazildo]

15:00, friends didn't need to has pointers to persons, just persons. 15:14, even having pointers, unique_ptrs would better fit on friends, instead of people. The way it is, people data struct has an "extra issue", at least for human perception. This whole example was a mess, that proved no point. std::vector takes care of its objects lifetime. There was no need whatsoever for explicit pointers usage. Neither here (20:35) you proved a point against objects. 29:05, this model is bad only if, to get a model to work, it needs to handle all of these information. Which doesn't seems to be the case. If each "node" needs to know only the informations that "touches" it, this whole thing is humanely maintainable. Btw, this probably would not work with atomic values/f() programming, because someone would change its value by mistake, while objects don't allow it. If you wanted to show situation where objects are bad, used only by "fetish", you should talk about interfaces. Here is a good example: kzbin.info/www/bejne/l3yvn6eQmNVlba8 . She didn't proof a point against OO at all, but rather against interfaces. 35:40, I think it's a good idea to have a struct, since web data structs tend to grow on time, which can avoid to have tons of refactoring work to do. And it can also easily switch to class, as soon as situation becomes dangerous, when bugs arise due to changing its variable in wrong places. 47:41, literal numbers are way more dangerous then they look. I always make a global constant for each of them.

[@ankitrathore3946]

Redux architecture..

[@shalokshalom]

Yes, they do quote Elm and Redux on the website. And It's Elm, who invented this before Redux.