Our great sponsors
-
openvscode-server
Run upstream VS Code on a remote machine with access through a modern web browser from any device, anywhere.
-
webpack
A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
Based on some back-and-forth in our Discord, we decided to try out a handful of Cloud IDEs. Ultimately, this PR (and some ground-clearing ones that preceded it) introduced support for Gitpod, Replit, Stackblitz, and Glitch.
In Part 4 of this series, I'll be talking about some of ways the scope of PR #1322 grew to include cloud-based IDEs! As alluded to in Part 1, our conversion from Webpack to Vite all started because of a discussion about opportunities for dependency updates in our project. Between this and us greatly reducing our build script footprint, we saw in this endeavor an additional opportunity for reduced friction in getting setup for Cloud IDE support. To us, Cloud IDE support presents an arguably easier path for prospective contributors, because it allows them to skip the hard parts of preparing their local environment for development.
In Part 4 of this series, I'll be talking about some of ways the scope of PR #1322 grew to include cloud-based IDEs! As alluded to in Part 1, our conversion from Webpack to Vite all started because of a discussion about opportunities for dependency updates in our project. Between this and us greatly reducing our build script footprint, we saw in this endeavor an additional opportunity for reduced friction in getting setup for Cloud IDE support. To us, Cloud IDE support presents an arguably easier path for prospective contributors, because it allows them to skip the hard parts of preparing their local environment for development.
Based on some back-and-forth in our Discord, we decided to try out a handful of Cloud IDEs. Ultimately, this PR (and some ground-clearing ones that preceded it) introduced support for Gitpod, Replit, Stackblitz, and Glitch.
Based on some back-and-forth in our Discord, we decided to try out a handful of Cloud IDEs. Ultimately, this PR (and some ground-clearing ones that preceded it) introduced support for Gitpod, Replit, Stackblitz, and Glitch.
Based on our experience at present, Stackblitz, Replit, Codesandbox, and Glitch are not reliable enough to test significant feature contributions to an application at the scale of Open Sauced. From what we see, the reliability challenges deal with the virtual filesystems in use - Open Sauced is a five year old project, and the codebase has grown. In fact, we feel that the performance benefits of Vite (especially its use of esbuild) made it possible for us to get the Cloud IDE support to the level that it is today.