Live data from Hacker News

Bowery – The Next Generation of Web Development

bowery.io

11–20 of 48 posts

Re: Bowery – The Next Generation of Web Development

#12
post #5

Unlike most development environments, Bowery requires an internet connection. And I'm out. So, this seems like a sort of Google App Engine, but running on Node? BoweryDB and the Cache sound just like what App Engine provides - except that the App Engine also runs on my local dev box. The problem with this (and the App Engine) is that it's totally locked in. Your database is proprietary, your middleware is proprietary…

AppEngine's lockin is significantly overstated. AppScale exists and works well.

Re: Bowery – The Next Generation of Web Development

#17
My take: Bowery is basically Google App Engine for Node.js.

Of course, they put their own spin on things. The whole 'bowery connect' thing is unusual - they say that your "dev environment is online" but I'm not sure what they mean. It appears that what 'bowery connect' does is initialize a git repository and starts sync'ing filesystem changes to a remote host. In other words, rather than GAE's more traditional "deploy" command, bowery is constantly deploying.

The benefit of doing deploy in this way is clear: it's much easier on the user (nothing to install apart from an editor), and it's much easier on the bowery people because they don't have to provide a local analogue to the hosted environment. The dev environment is the hosted environment. This is possible because, presumably, the hosted environment serves branch URLs extremely cheaply.

No doubt the kernel of this project has it's origin in a late night conversation that started, "What if HTTP endpoints were as cheap as git branches? What if you had an active endpoint for every branch?"

Post reply on HN