I'm as shocked as you, but the Darklang back end rewrite is complete

blog.darklang.com

42 points·pbiggar··5 comments

While it's cool to hear about this project progressing, I still am wary of working in a stack that has no options to run anything on my local machine (editor included).

Thanks! I understand the wariness - the idea is that Darklang is solving a particular problem, which is building cloud backends. I believe that adding in other constraints (common ones are local development, using existing languages, using existing editors, and using existing hardware/clouds) will make it worse for solving the core problem. Plus, there's plenty of great options that run on your local machine, so just don't use dark for that.

Hey, if you get customers and are filling a need more power to you! I was burned early in my career by a product like yours is all. All that being said, from a technical level it's cool seeing what your project is up to.

Yeah, absolutely fair. That said, I think there's a movement away from local because:

a) deployments are getting complex enough that it's hard to get dev environments locally

b) it's cheaper and quicker to pay for cloud development machines anyway

c) things have enough scale that local development doesn't match production anyway

Saw this on twitter recently which supports this a bit:

https://twitter.com/swyx/status/1533910738942562304

Congrats to Pbiggar. Can we call you the Dark Lord now? ;-)

Reply on news.ycombinator.com