Language Engineering in the Cloud
1 like839 views
- Cloud9 is a fast-growing startup with 30 employees and 2 offices that creates the best JavaScript IDE. Their core product is an online IDE called Cloud9 that uses Node.js and has many features like collaboration, VIM mode, and offline support. - Cloud9 supports language engineering in the cloud through its plugin architecture and use of language services. These services provide features like syntax checking, code completion through an asynchronous interface. - Cloud9 aims to expand language support and analyses through open-sourcing components, using their language foundation that provides language services in a technology-agnostic way, and building an extension store.
Language Engineering in the Cloud
- 1. Language Engineering in the Cloud Lennart Kats @lennartcl
- 2. 9
- 3. <utrecht>
- 4. Language Engineering Research Compilers Domain-specific languages Language extensions Parsers
- 7. Spoofax
- 8. Spoofax “DOES THE TYPE CHECKER CATCH THIS?”
- 9. Spoofax “DOES THIS HYPERLINK POINT TO THE RIGHT PLACE?”
- 12. Fast-growing startup: Cloud9 IDE
- 13. Venture capital 30 employees 2 offices
- 14. Core Product
- 15. Organization Front-end Products Back-end Support Language Marketing & business Node.js development
- 16. Open Source
- 17. Goal Create the best (JavaScript) IDE out there!
- 18. Key Features
- 19. Collab
- 20. Collab
- 21. Integration with Cloud Services
- 22. VIM Mode
- 23. Offline Mode
- 24. Terminal Access
- 25. Language Support
- 28. Everything is a plugin file tree search JS completion terminal file system save
- 29. Plugin components Client-side JS Server-side JS XML for UI
- 30. Evented I/O for JavaScript V8 JavaScript engine Everything asynchronous No threads
- 31. Scaling
- 32. ELB Proxy1 Proxy2 Proxy3 IDE1 IDE2 IDE3
- 34. XaaS in Cloud9 Browser Developer IDE SaaS Red Hat PaaS Amazon IaaS
- 36. ELB Proxy1 Proxy2 Proxy3 IDE1 IDE2 IDE3 Gear1 Gear2 Gear3 ... Gear n
- 39. Cloud9 Language Services DEMO
- 40. Editor, plugin Cloud9 architecture
- 41. UI, Events, Language Foundation WebWorkers Editor, plugin Cloud9 architecture
- 42. Interface base_handler UI, Events, Language Foundation WebWorkers Editor, plugin Cloud9 architecture
- 43. Implementation Language services Interface base_handler UI, Events, Language Foundation WebWorkers Editor, plugin Cloud9 architecture
- 44. base_handler • handlesLanguage() • parse() • analyze() • outline() • complete() • ...
- 45. Language Foundation All language services are functional and described by a single function The Spoofax Language Workbench, OOPSLA 2009
- 46. Language Foundation All language services are technology-agnostic findNode(), getPos() Accelerating the creation of customized, language-Specific IDEs in Eclipse, Charles et al., OOPSLA 2009
- 47. Language Foundation All language services asynchronous WebWorkers or Client/Server I/O
- 48. Language Foundation Concise specification using generic traversals Stratego/XT 0.17. A language and toolset for program transformation, Bravenboer et al., SCP 2008
- 49. Treehugger.js • Based on Stratego/XT • 100% JavaScript • Use any parser • Efficient
- 50. Implementation Language services Interface base_handler UI, Events, Language Foundation WebWorkers Editor, plugin Cloud9 architecture
- 51. Parser JS Services Implementation treehugger.js Interface base_handler UI, Events, Language Foundation WebWorkers Editor, plugin Cloud9 architecture
- 52. Treehugger.JS DEMO
- 53. Computational Model Server-side: - CPU resources expensive Client-side: - CPU resources “free”!
- 55. What’s Next Whole-project analyses • Incremental • Distributed • Multi-user
- 56. What’s Next Parser generators • Incremental • Recovery • General
- 57. What’s Next Java IDE • High expectations of Java IDEs • Can’t we reuse existing IDEs? • OpenShift to the rescue
- 58. What’s Next Cloud9 Extension Store • Extend Cloud9 for tools, languages • GitHub
- 59. Community Reachout • Open source, GitHub • R&D • Graduate students • Education • Third-party extensions
- 60. Conclusion Open-source OpenShift Advanced language analysis expanding to server and other languages Lennart C. L. Kats @lennartcl http://lennart.cl
Editor's Notes
- #2: \n
- #3: \n
- #4: \n
- #5: \n
- #6: \n
- #7: \n
- #8: \n
- #9: What I brought to the table\nIDE compulsory\n
- #10: intimate connection between the two\nboth from user and developer perspective\n
- #11: Language workbenches combine interactive definition and use of DSLs\n
- #12: Scenario: scoping rules!\n
- #13: Scenario: scoping rules!\n
- #14: \n
- #15: After four years, I completed my PhD and went on to do a 2 year postdoc\n
- #16: \n
- #17: \n
- #18: \n
- #19: Accel/Atlassian\n
- #20: \n
- #21: 30 ppl; half developers\n\nproducts: strategies, website, UX, support\n
- #22: \n
- #23: \n
- #24: 2 areas: features based on the connectiveness of the cloud, and features familiar from desktop IDEs\n
- #25: \n
- #26: \n
- #27: \n
- #28: \n
- #29: \n
- #30: \n
- #31: \n
- #32: \n
- #33: \n
- #34: \n
- #35: \n
- #36: \n
- #37: \n
- #38: \n
- #39: \n
- #40: \n
- #41: \n
- #42: \n
- #43: IaaS: scaling, pay-by-use\n
- #44: IaaS: scaling, pay-by-use\n
- #45: IaaS: scaling, pay-by-use\n
- #46: \n
- #47: \n
- #48: \n
- #49: \n
- #50: \n
- #51: \n
- #52: \n
- #53: \n
- #54: \n
- #55: \n
- #56: \n
- #57: \n
- #58: \n
- #59: \n
- #60: \n
- #61: \n
- #62: departure from DSL approach\nefficient: caching\n
- #63: \n
- #64: \n
- #65: \n
- #66: \n
- #67: NodeJS: single-threaded; openshift: computational power per user!\n
- #68: \n
- #69: \n
- #70: \n
- #71: \n
- #72: \n
- #73: \n
- #74: \n