Hello, I’m Francesc

Machine Learning on Source Code #MLonCode

'112', '97', '99', '107', '97', '103', '101', '32', '109', '97', '105', '110', '10', '10', '105', '109', '112', '111', '114', '116', '32', '40', '10', '9', '34', '102', '109', '116', '34', '10', '41', '10', '10', '102', '117', '110', '99', '32', '109', '97', '105', '110', '40', '41', '32', '123', '10', '9', '102', '109', '116', '46', '80', '114', '105', '110', '116', '108', '110', '40', '34', '72', '101', '108', '108', '111', '44', '32', '112', '108', '97', '121', '103', '114', '111', '117', '110', '100', '34', '41', '10', '125', '10' package main import “fmt” func main() { fmt.Println(“Hello, Chicago”) } What is Source Code

package package IDENT main ; import import STRING "fmt" ; func func IDENT main ( ) package main import “fmt” func main() { fmt.Println(“Hello, Chicago”) } What is Source Code { IDENT fmt . IDENT Println ( STRING "Hello, Chicago" ) ; } ;

package main import “fmt” func main() { fmt.Println(“Hello, Chicago”) } What is Source Code

No content

… a self-hosted server for universal source code parsing, turning code files into Universal Abstract Syntax Trees

No content

No content

No content

Parsing Go in Go is easy Parsing Java in Java is easy Parsing Go in Java is doable … I guess Parsing Java in Go is interesting … Parsing C++ in Go is why are you like this? Parsing X in Y

N parsers in 1 language is way harder than N parsers in M languages

No content

No content

● Good UX ○ Intuitive commands, flags, args ... ○ Reasonable defaults ● Frictionless installation ○ As few dependencies as possible ○ One line to run is good ○ No lines to run is even better DevRel: reducing time to “wow”!

docker run >>> apt-get + pip + brew + ....

Bblfsh container docker run foo container foo

No content

Docker in Docker! Using Docker-in-Docker for your CI or testing environment? Think twice jpetazzo.github.io/2015/09/03/do-not-use-docker-in-docker-for-ci/

Docker in Docker! However, contrary to popular belief, Docker-in-Docker is not 100% made of sparkles, ponies, and unicorns

Actually … docker run \ --privileged -d \ docker:stable-dind Later on ... hub.docker.com/r/library/docker/

Docker in Docker! jpetazzo.github.io/2015/09/03/do-not-use-docker-in-docker-for-ci/ Just map /var/run/docker.sock !

container Docker CLI /var/run/docker.sock

container docker run foo /var/run/docker.sock container foo

libcontainer

No content

No content

Managing drivers (parsers)

Scaling ● Pluggable strategy ● Default behavior: ○ 1 container per request ○ Extra time for reuse ● Not implemented yet ● Upgrade is for now Remove + Installation bblfshctl driver \ install --update \ foo Upgrading

Docker in Docker Docker Socket - Hard to use, previously - Much easier now - Lots of features we don’t use - Requires Docker to be used no matter what libcontainer - Fewer features - Fewer dependencies - Runs on Linux without Docker

References - bblf.sh / dashboard.bblf.sh - sourced.tech - github.com/bblfsh - @francesc @sourcedtech

Thanks!