7 ms·

Creator here — thanks for posting our project! For more info, check out my Medium announcement post here: https://medium.com/@ericsimons/stackblitz-online-vs-co

• acdjuiamadfn 9y ago
  I want to ask 3 things: 1) Man hours taken in this project 2) Your intended goal 3) Possible avenues to make money.
• akuji1993 9y ago
  As I already said in another comment, Sass support would be a huge deal for me and our team. Without it, it's not that viable for us to use since we write all our styling in scss. But it's still very nice and I would certainly use it for small projects or some fast hackups.
• fgblanch 9y ago
  Is it actually a modified version of VScode (As sourcegraph does) or are you just using the Monaco editor? As some mentioned in other comments i would also be insterested in running vscode frontend in the browser while havinf the backend in a VPS. Thanks and congrats on the project it's great!
  • Hydraulix989 9y ago
    Yes, that's one use case (desktop/web interop) where using something Electron.JS might actually make sense (to the extreme detriment of battery life, memory usage, and CPU usage).
• afshinmeh 9y ago
  Sorry for posting two comments. Could you please explain what is the difference between your project and this: https://github.com/CompuIves/codesandbox-client https://github.com/CompuIves/codesandbox-client And this is the online editor: https://codesandbox.io/s/new https://codesandbox.io/s/new
  • ericmsimons 9y ago
    From the start, our goal was to port VS Code, NPM, and Webpack loaders to run entirely in your browser and still work offline. With StackBlitz, the browser is installing, bundling, and serving everything — our servers don’t do any of that. While CodeSandbox is a nice playground for React apps specifically, we have never intended (nor have any aspiration) to compete in the online playground space. We’re attempting to build the first fully in-browser IDE.
    • afshinmeh 9y ago
      Right. Well, from what I can see, even the elements on the page and the offline editor works exactly same as your project. Almost everything, even the `npm install` thing is the same. All in all, what you have done is great and absolutely useful for quick tests.
      • ericmsimons 9y ago
        ...CodeSandbox has no offline support whatsoever. It sounds like your motivation is to promote an unrelated product in this HN thread, and that's super lame :(
        • rattray 9y ago
          I think they simply didn't understand the distinction that one runs js bins (npm install, webpack build) on a server, and the other in the browser. They also might not understand why it matters.
          • deleted 9y ago
            [deleted]
          • peternicky 9y ago
            Care to explain further?
            • 9y ago
• mncharity 9y ago
  A minor thing which struck me when reading the Medium post. When early on, the Angular folks were energetically arguing that the reason you could count on Angular 1, was because they were building on a new technology no-one had ever used before (!), and they were backed by Google (!), my thought was: you've just told me a great deal, but it's likely not what you had in mind. > we <LOVE> Microsoft! I had the same thought reading this. EDIT: Fyi, esft.com, linked from your twitter, is currently 502.
• ontouchstart 9y ago
  Thanks for pushing the limit of browser. I made a customer npm package that wraps react-16.0.0-beta.3 and it runs well in both RunKit and StackBlitz. https://twitter.com/ontouchstart/status/893886659070230529 https://twitter.com/ontouchstart/status/893886659070230529 I am sure it will be a great tool for npm package authors to test new server and browser ideas.