1. The future of development
tooling
Mélanie Bats, CTO @ Obeo
Stevan Le Meur, Product Manager @ Red Hat
The example of Eclipse Che, Theia and Sirius

2. A long time ago in a galaxy far
far away...

6. {OOP}

8. “In 1995 IDE was not well received by
developers since it would fence in their
creativity”
Wikipedia

11. Tools are helping us to be more productive
and focus our time on bringing value to the
products we are building.
Unleash our complete potential...

12. A developer today:

13. A developer today:
- Works mainly on his localhost.

14. A developer today:
- Works mainly on his localhost
- Codes in only few technology sets

15. What are the trends ?

16. A new generation of IDEs
Developers love them because of :
● Lightweight
● Simplicity
● Powerful tooling
● Easy customization
● High release cadence

17. The VS code example
● <100Mb download
● Light UI
● Marketplace
● Extensions, Language
Servers
● Each month a new version

18. And other light editors
And now Atom IDE

19. Not afraid
anymore by...
browser IDE

20. Codesandbox

21. The newborn: Eclipse Theia

22. Eclipse Che

23. Che workspace
IDE RuntimesProject Files

24. Workspace Runtimes
Application stack + “Dev Mode”
IDE Tooling as microservices in sidecars
Language
IDE
Debugger
Test
App

25. Demo Sidecars

26. Workspace Runtimes
Application stack + “Dev Mode”
IDE Tooling as microservices in sidecars
Language
IDE
Debugger
Test
App

27. Dedicated workbenches

28. The well known… RCP applications

30. Don’t touch it, it’s mine!

31. Use a sledgehammer to crack a nut!

32. ONE tool dedicated to ONE task!

33. The way we develop is changing
40%
Of enterprise developers are
already using >3 languages in
development.
Using Many Languages
66%
Of enterprises are already
using containers in
development, test or
production.
Adopting Containers
Source: Cloud development Survey 2017 - Evans Data Corp

34. Being more agile with our tools
Iterate faster
Focus on value to create
Share workspace with all stakeholders
Pair programming
Live collaboration

35. Live collaboration

36. Evolution of the IDE concept?
More accessible tool
Tools integrated
Different “views” for different use cases and different users

37. IDE-agnostic tools
Tools to be opened to more “domains”, not only engineering
Tools to be available more broadly, to more platform, to more users

38. Sirius in the Web
Prototype

39. Sirius integrated in Theia
Prototype

40. Sirius integrated in Che
Prototype

41. What’s next ?

42. “Cloudifying” our tools
More resources
More calcul engine
Simplification of deployment
Tools lifecycle

43. IA for developers
Machine learning applied to :
● Code recommendation
● Team collaboration
● Auto layout mechanism

44. Chatbots
W
hyNot?

45. Deep learning
Soundscool:)
Layout?

46. Blockchain
Buzzword!
Model collaboration?

47. Virtual Reality?
OM
G!

48. What do you want ?
Come to chat with us

49. Open source is the only way
Catalyse of energies
Opportunism from different ideas and visions
Open protocols : language server, debugger, and others...

50. Graphical Server Protocol
● Lowering the cost of integrating a graphical tool in a platform
● Defining a protocol used to communicate between a platform and a
graphical designer
● Open source initiative : https://obeonetwork.github.io/GraphicalServerProtocol/

51. Next steps for Che & Sirius?
- Eclipse Che: Platform to build cloud tooling
- Extensibility, Pluggability
- Cloudifying your tools
- Sirius needs you:
- Contribute to Sirius : it will remain open source
- Share needs & feedback
- Participate to the Graphical Server Protocol
- Support Obeo

52. Thanks! Questions?
Stevan Le Meur - Che maintainer :
@stevanLM / slemeur@redhat.com
Mélanie Bats - Obeo :
@melaniebats / melanie.bats@obeo.fr