Fixing the process

We weren't happy with Python unix processes interface. So we tried to fix it, make it more obvious to suit with the "Explicit is better than implicit" zen principle.

Transcript

1. Process Kit Python processes made obvious
2. Hi! Halo! Ola! I’m @oleiade I’m a software hater And I work at @botify
3. I like obviousness
4. And I like to fix things
5. On a typical day trying to fix things
6. #Unix is a masterpiece (Even though it chooses it’s friends…)
7. #Python is awesome (As long as you know what to expect from it…)
8. However…
9. we found python processes interface was neither awesome nor obvious
10. So we started digging into it. And gradually recoded it.
11. “Those who do not understand UNIX are condemned to reinvent it, poorly.” Henry Spencer
12. what’s the output of this?
13. It will, sometimes, raise an AssertionError
14. #Unix signals are asynchronous (don’t you forget…)
15. However…
16. terminate sends SIGTERM to the process
17. Therefore…
18. you have NO insurance when the process is actually stopped
19. Schrodinger’s cat is watching you
20. Explicit is better than implicit
21. Pkit processes are patient
22. Blocks until process really stopped
23. Pkit processes are really patient
24. Blocks until process signals handlers are overriden
25. Pkit processes are cleaned
26. Once a process is stopped, it’s execution context is collected
27. Pkit processes are reusable
28. Processes are reusable shells. Execute all the things into it.
29. They are restartable
30. Rexecute a task. Again, and again, and… Right, you’ve got it.
31. Pkit processes code is plain
32. No dust hidden under the carpet. Most of the things are public. Most of the things are easily overridable.
33. Pkit processes expose callbacks
34. You can set a callbacks to be ran at process startup or exit
35. This is the end
36. Process-kit is still work in progress
37. It is evolving fast
38. It was built with good intentions
39. Go ahead, Fork it, Break it, Make it awesome github.com/botify-labs/process-kit
40. Questions?