Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.



CodeSandbox does almost everything in the browser however. The only thing it doesn't do in the browser is dependency bundling, which StackBlitz does in this case.

Essentially CodeSandbox can work offline if you already had the website open while you're online, then you can still continue offline. StackBlitz has the advantage that the tab where your application is can also be opened initially offline, which is handy for showing your application when you have no connection, but if I'm not wrong you cannot continue developing offline. I'd love to hear that I'm wrong, I'm really impressed with StackBlitz.

I'm the author of CodeSandbox btw :).


> but if I'm not wrong you cannot continue developing offline

Completely false, see -> https://twitter.com/ericsimons40/status/893238309085822977

You even responded to that thread yesterday, not sure how you didn't see this...


I did see that tweet. Maybe I was a bit unclear. I mean that the whole editor itself doesn't open when you don't have a connection (at least for me). My reproduction steps are:

1. Open https://stackblitz.com/fork/react

2. Disconnect from internet

3. Refresh the tab

At least for me this gives me a 404. I'm on Chrome. However, when I open the preview tab while offline it doesn't 404 on me.


Care to explain further?


There's already Atom In Space but it's not complete I don't think. Not sure how hard/reliable it would be to run.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: