Thread by @QuinnyPig

And now @Carl_F_Meadows delivers a talk that purports to be something other than @elastic getting the kicking it was begging for with their license commingling shenanigans.

Don't get me wrong; I firmly believe that @awscloud lies awake at night worried that someone else may be making money, but in this case it feels like the right move on their part.

Now @Carl_F_Meadows takes his career in his hands to explain the history of Elastic's issues with open source. One misspeak and lawyers will pounce. They've not been fed in weeks.

"Open Source ElasticSearch has no security layer." Oof. That's just egregious in 2019.

I'd take the loud criticism of ElasticSearch better if AWS's managed ElasticSearch service offering was... y'know. Good.

Now the fire alarm lights are strobing in the talk as @elastic tries frantically to stop @Carl_F_Meadows from delivering his #oscon talk.

"We'd built all of these internally anyway, so why not open source it? We build what customers want." --@Carl_F_Meadows

"Simpler billing?"
"Got it, an AI/ML service built for horse detection coming right up!"

"We don't have a lot of Windows expertise on the team, so this was driven by a community member." --@Carl_F_Meadows

I love the story, but I'm troubled by the idea of doing volunteer work for a trillion dollar company.

And that's the talk! If there are any questions, @Carl_F_Meadows will be in the Weeping Room, sponsored jointly by @elastic, @RedisLabs, and @mongodb.