I didn't realize Lucene used their own flavor of roaring bitmaps! Super Cool. I certainly think of search when it comes to Lucene, where as the cited material from Vikram & FeatureBase are targeting more general analytics.
I actually feel like they've gotten better in terms of story and character development with each iteration. Niko Bellic was one of my all time favorites, and I thought they did a good job balancing 3 characters in GTA V. They're all certainly... over the top, but given what you do in GTA, it makes sense.
This was my only issue with Niko. He was a great character but then the mission ends and I drive away at 100 mph and run over 5 pedestrians and he shouts "I hope you have insurance!" Sure you can play the open-world sections true to the character... But pacifism isn't what you do in GTA :P
The GTA 5 characters were designed better in that regard. Niko had the deeper/more complex story overall, but he's at odds with the gameplay.
Thanks for posting! We just adopted rebase for our docs repo, so this was a timely article for me. I do really like the clean commit history, but I also haven't experienced any of the downsides yet.
So torn on this! Thinking back on my best teachers, they had a huge impact on my development and what I thought of school. On the flip side, some teachers made me count the hours every day until I could be done with their class. It won't happen, but it would be pretty interesting to see merit increases tied to this (retention of students, requests to join/leave group, etc.).
There is definitely a lot of pressure out there for commercial DBs to adopt dual (OS + commercial) models right now. I'm seeing that more and more. I don't like the BSL concept. That is just a big trap imo.
Ya the way he responds saying a full team would be needed to uncover this sounds like he was treating "where" holistically. Every bit of information in every server, application, etc. Feels like a trained response.
The way I read this, his response saying that a full team would be needed to uncover this is not a flaw in the question - because IMHO that's exactly what was required - but rather that Facebook has not done the work required to meet their legal requirements. Yes, it's quite plausible that Facebook might need a team to do extensive work to produce the analysis and documentation about where private data is flowing - that's not a valid excuse though, Facebook simply needs to make that team and do that work, no matter if they want to or not, until they can properly answer these questions.
They need to have an exhaustive list of how they're using private data, and they need to have a process ensuring that their engineers are not adding new sources of private data or not using existing private data without the company approving and updating that list. Yes, their current processes aren't fit for that - as Meta documents quoted in TFA say "We do not have an adequate level of control and explainability over how our systems use data, and thus we can’t confidently make controlled policy changes or external commitments such as ‘we will not use X data for Y purpose,’" - so these processes must be changed.
