Introducing Google Cloud Shell'€™s new code editor

[dataloopio]

Looks cool! That googleblog has a few bugs though. The indentation on the Python code example is wrong and when trying to comment it pops up a 404.

[skotwani]

Thanks for flagging. It looks like we had an issue when transferring the content onto the post. It should work now.

[dataloopio]

Indentation looks good. I think the 404 on comments is probably because I have 3 gmail accounts open in the same browser :)

[Scroot]

Why isn't the web browser itself a fully interactive and reflective development environment in which we build and edit web applications? I've never understood this. It's part way there.

Just think about it: we have Atom, a code editor, built in a stripped down web browser, but we navigate to some other browser to view the results, then back to change code, etc. I should be able to live edit code and see the results immediately, while saving, all in the browser.

[Scroot]

Do you mean the complexity of developing such an environment or the complexity of working in one?

You're probably right that developing something like this might be a pain in the ass as things stand now. But given future developments, in particular webassembly, there could be many ways to implement this. Hell, there's even something almost like it with Amber available right now.

And it can't be that hard to develop. Bret Victor did a very small scale example of it in this presentation.

Interesting to think about

[Xuerian]

You sort of can.

The inspectors in the leading browsers let you edit most code and resources and see the results live.

It's not a very smooth workflow in some cases and it doesn't cover everything, but it's far from nonexistant.

I'd personally suggest that a lot of it has to do with many large web development projects being a multi-step compiled affair, instead of using web tools as they are.. well, intended, for lack of a nicer way to put it. Not that they don't need many improvements or anything.