All out in the Cloud - CloudEast 2012
0 likes•1,318 views
The document promotes an online integrated development environment (IDE) called Cloud9 that allows developers to code from any device without limitations. It can be run from anywhere, supports cursor and tab syncing between devices, and debugging state syncing. The IDE servers are scalable and behind a load balancer for high availability. Developers can use their own virtual machines and it integrates with services like GitHub.
All out in the Cloud - CloudEast 2012
- 1. ALL OUT IN THE CLOUD
- 2. @drbernhard
- 19. Build the best fucking IDE
- 20. Run it from anywhere
- 31. If my critics saw me walking over the Thames they would say it was because I couldn't VIM.
- 32. Create Deploy Run/Debug Share Test
- 37. Limitation free dev environment
- 40. Work on a plane
- 48. Bring your own VM
- 55. Cursor syncing Tab syncing Debug state syncing
- 57. Architecture
- 59. Elastic Load Balancer Proxy Proxy IDE server IDE server IDE server IDE server Insta Insta Insta Insta Insta Insta Insta Insta nce nce nce nce nce nce nce nce
- 60. VFS Instance
- 64. Happy coding!
- 65. Questions?
- 66. http://c9.io http://github.com/janjongboom @drbernhard
Editor's Notes
- #2: \n
- #3: Hi!\n
- #4: Chriet Titulaer, CD-Rom discs, Philips, houses. “Wonderful world” \n\nLarge sets information.\n
- #5: Encarta. mid 90s days and days. Virtually everything.\n
- #6: Insanity. Buying, putting, starting. Quick info. 2000s: internet main supplier.\n
- #7: RightMove, Wikipedia.\n
- #8: Start of the cloud era. Stand alone apps -> internet. Not just local.\n
- #9: Mid 2000’s, view-only to content creation.\n
- #10: The longer, the less desktop apps survive. No more MS Office.\n
- #11: Alternative in the cloud. Not just replacement. Allow me to work in a way.\n
- #12: Backups, carrying around floppy disks.\n
- #13: Innovation: new workflows.\nSlow transform 80s - 2000s. Took 20 years for a revolution to take place.\n
- #14: Another revolution: consuming content -> producing content. It’s time to\n
- #15: build the cloud in the cloud.\n
- #16: Desktop apps will be replaced. 3-5 years Photoshop local is old skool.\n
- #17: Also applies for programming. Screen sharing Skype. ‘Doesnt happen on machine’.\n
- #18: Crashed hard disk. Offload compilation. 2 full working days.\n
- #19: Two years ago: goodness of the cloud to devs. Last step. Vision:\n
- #20: \n
- #21: Got us busy for two years. Pulling off. Combined with the craftmanship of\n
- #22: some extremely talentend and handsome young folks,\n
- #23: resulted in Cloud9 IDE. Online IDE, built by. Best IDE for javascript.\n
- #24: Traditionally devs that use Java, .NET, they are completely used to having all the great tools: IDE's, testing suites, continious integration services;\n
- #25: whereas the javascript developer, or actually anyone who does dynamic languages, well... not so much! They're happy with just syntax highlighting!\n
- #26: Result. Online IDE. Runs JS, Ruby, PHP, Pyton. Quick glance:\n
- #27: Blazing fast editor. Used MS, Google, GitHub. Open source.\n
- #28: Run and Debugger. Node.js. Live inspection, variable editing.\n
- #29: \n
- #30: Context aware code completion. In the workings, but available for node.js.\n
- #31: 5. Go to file and go to definition\n
- #32: 6. VIM Mode. Bindings to VIM right from your web IDE. \n
- #33: \n
- #34: \n
- #35: Some highlights. Capable of taking over, when doing dynamic languages. Building an editor is not the greatest challenge.\n
- #36: Other people executing code. Scary. Bring down servers.\n
- #37: White listed patched applications. No binary execution. “C’mon move over to the cloud”, limit apps.\n
- #38: I should be able to run everything in the cloud, the same as local\n
- #39: All web apps face. Requires internet connection.\n
- #40: Local storage. Resyncing. Run and test. 400 MB repo.\n
- #41: \n
- #42: Extremely awesome. Not possible w/o cloud. Potential of Cloud IDE.\n
- #43: \n
- #44: Don’t create security holes. Don’t restrict. Two ways: 1. VM.\n
- #45: Run on OpenShift. Spawned.\n
- #46: True freedom. Linux box. Java? MemSQL? Already GIT.\n
- #47: Run from command line or SSH terminal.\n
- #48: Only paying. Fully functional. Real VIM, Telnet, Watch Star Wars ASCII. VM included on every project.\n
- #49: Disadvantage, will die after closing + bound to C9.\n
- #50: Internal: spawn EC2, provision image, give credentials. Bind ANY SSH enabled server.\n
- #51: Work on Airplane. Open source, grab from GH. Dont like hosted. Still bound to local machine.\n
- #52: Around via Git, switch local <> cloud.\n
- #53: Local version. Open source + real time sync. On your machine: work local + advantages of cloud. Available everywhere.\n
- #54: Amazing.\n
- #55: Real time code collaboration. Audience participation: MobileEast.\n
- #56: Join in coding session.\n
- #57: When someone joins in you can have a little chat with them, and then you can start the debugger just like you would on a normal project, the great thing here is that breakpoints and paused statements are shown on both screens and both parties control the debugger. They both have access to seperate live inspectors.\n
- #58: As we&#x2019;re all cloud devs. Architecture. Used to be Joyent, now EC2.\n
- #59: Data center latency. Faster than ever before. Server architecture.\n
- #60: Sticky connection users->IDE. Redis. Use Redis 2 go. Data loss moment. Never lost any files, but lost day of metadata.\n
- #61: IDE -> OpenShift. VFS, SSH, node.js. Local FS, FTP, SSH. Future: Google Drive, Dropbox.\n
- #62: Also channel support. Internal devs: latest greatest.\n
- #63: Participate live action coding. MobileEast. Mobile app Cloud9, Ripple, PhoneGap. Stickers.\n
- #64: You can find Cloud9's source on GitHub, at github.com/ajaxorg/cloud9, including all libraries like VFS under /c9 or /ajaxorg. The editor is under ajaxorg/ace.\n
- #65: \n
- #66: \n
- #67: \n