Going Polyglot the Easy Way

What do Clojure, Java, Scala, and Ruby all have in common? They all can run on
the JVM. Today going polyglot is easier then ever!

In this talk we're going to learn why it's important to use the best programming
language for the job and how to start doing so. By using the polyglot approach,
your projects will be more flexible to change, simpler to test, easier to deploy,
and understandable to developers with any programming background.

Simple actions you can take to increase the versatility of your programming
toolbox and finally get paid for writing code in your latest beloved language.

Transcript

1. Cześć
2. Pirahã people
3. Colours
4. History Religion
5. Numbers
6. Linguistic relativity
7. Programmers
8. Compilation errors Type systems Immutability ?
9. Going Polyglot the Easy Way
10. Disclaimer
11. Change is not easy
12. Benchmark
13. Small Show results fast Throw away code
14. Internal Issues will be reported Users will be forgiving
15. Under the radar Short-lived code A/B test your solution
16. Not mission- critical Don't do that Bottlenecks are high-risk, high-reward You might get fired
17. Examples
18. Publish Subscribe
19. RabbitMQ bindings: Java, Scala, Groovy, Clojure, Ruby, Python, .NET, PHP, Perl, C, C++, Node.js, Go, Erlang, Haskell, Objective- C, Ocaml, Common Lisp…
20. Service-oriented Architecture
21. Ruby on Rails equivalents Elixir / Phoenix Haskell / Yesod
22. Why Elixir and Phoenix? Performance Scalability Productivity
24. Why Haskell and Yesod? Performance Correctness
25. JavaScript
26. 300+ options Elm ClojureScript CoffeScript
27. Why not CoffeScript?
28. Why Elm? Types FRP - Signals Time travel
30. Why ClojureScript? Immutability Speed Functional paradigm
32. Don't be that guy
33. Be that guy
34. haikuco.de