Interesting talk. I just discovered vcpkg this week, I really love it. I'm really glad people are willing to maintain all those packages because I sure wouldn't want to do that job.
That was some god tier presenting skills. The speaker didn't have a monotone voice, and the way they explained their points was very interesting. and quite informative. Nice job. Very well done.
Agree with not having header checks, I've always found it unneccessary overhead to build times. And plus, the build is gonna fail anyway of the headers aren't there. Never saw the benefit of doing an early check.
I like the talk, but I would love to see a list of positive dos rather than negative don'ts. Seemed like the entire presentation was not about best practices but only things not to do.
Downvoted because i couldn't understand a lot of his rules and his problems and proposed solutions. Please write a document explaining in more details what you mean with your guidelines.
Obviously you don't maintain packages yourself. I do, and every slide had me nodding, thinking about how much time I've wasted fighting it when some library didn't play nice.
Well, then @Henry you are not the target audience at all. I'm a programmer and this talk was for me not for you and he was way to fast on many things. My experience level? Like every serious C++ programmer i build my own build system - on top of make (about 25 years ago) and cmake/msbuild (8 years ago) and i "maintain" my dependencies myself because even the 700 packages of vcpkg don't contain the things i need (pdfium, webkit, android NDK). But he is using some typical maintainer jargon that i don't get. Or like partial support maybe the idea is so broken braindead that my ability to understand the weird brain that did that before the next slide comes in. He should have done a 1h talk instead of 30min.
This talk was easy to understand, and I agreed with pretty much everything. (I also watched it live.) I'm sorry, but it's unclear to me what's supposedly unclear about this talk.
26:10 It's interesting that Sqlite3 is in the public domain. Especially because that's really hard (or rather time consuming) to do in come countries. For example in Germany you can only put something into the public domain if you die and the wait until the Copyright has run out (70 years, yep, in most countries it's that long these days).
