7,962 karma · joined January 26, 2009
Previously founder/CTO of Dark (http://darklang.com), and founder/CEO of CircleCI (https://circleci.com). PhD in CS.
https://hachyderm.io/@paulbiggar
https://bsky.app/profile/paulbiggar.com
https://twitter.com/paulbiggar
https://blog.paulbiggar.com
Contact: paul@techforpalestine.org or paul.biggar@gmail.com
While I personally agree that self-hosting is a nightmare, the biggest complaint we've heard about Dark has been related to vendor lock-in. I think this is a pretty good selling point for StaticBackend, for a few reasons: 1) what if you get too big for the hosting? 2) what if the company goes go out of business! 3) what if the company determines that hosting you is against the T&C (see the Parler thing this week, for example, although I completely agree with AWS' decision there).
I don't think self-hosting is really a good idea if you can avoid it, but a lot of people are soothed by the idea that they could, if they really needed to.
First thought: You don't have 40%, you have at most (11 months / 48 months vesting) * 40% = 9%. But, at 11 months you haven't hit your cliff, so you actually have 0%. That is, if they can fire you. It sounds like they're the CEO so they probably can, but if not the board can.
Producing Wrong Data Without Doing Anything Obviously Wrong! Todd Mytkowicz, Amer Diwan, Matthias Hauswirth, and Peter F. Sweeney. ASPLOS 2009.
https://dl.acm.org/doi/10.1145/2528521.1508275
I happened to be at that ASPLOS and I thought it was fascinating. Good to see it recognized as one of the most important papers in compilers.
Regarding marketing and selling what we have: we tried that and it's pretty clear we're missing important bits, in particular packages for common vendors (stripe, slack, etc), and a package for user management, as well as common things like validation. People love the concept (as do you, thanks!), but were struggling to build things because of what was missing.
As we went to build these, the tech/product debt that we had built up during our experimental phase really started to become apparent. We were missing common and expected things like user-defined types (maybe not important for dynamic langs, but we're a statically typed functional language, so being able to create types is kinda important), configurable (or at least changable) HTTP middleware, and a few other things.
The reason for the rewrite is that had been taking long detours around our tech stack for a while. Now that there's limited resources (as in, just me), the cost of taking the long way to everything we build is just a little too high, so it feels like a rewrite (note: just of the backend, the majority of the code is in the frontend and doesn't need to change!) is necessary to get to product/market fit.
I also hope it won't be the death of us. Fortunately, F# isn't a valid value for $hotlang! (Good thing I didn't pick Rust!)
- we're able to deploy (safely!) in 50ms rather than minutes because of it. [1]
- we completely host the infra and you don't need to think about it (including DBs and queues, which are nicely integrated into the language) [2]
- trace driven development, where we use real values from production and show you them in your editor [2]
[1] https://blog.darklang.com/how-dark-deploys-code-in-50ms/
[2] https://darklang.com/launch/demo-videoThe language in which the Dark interpreter is built has a GC, and we just use that.
A GC is a huge undertaking, and we already have to build an editor, a language, a stdlib, and infrastructure.
When we add a new version of a function, all the calls to the old function are unchanged. The autocomplete shows new users the new version (and not the old version), while people who are calling the old version get shown both.
> Welcome HN! If this is your first time hearing about Dark, check out the website[1], our What is Dark [2] post, and How Dark deploys in 50ms [3] to understand what we're about. Thanks for checking us out!
[1] https://darklang.com [2] https://blog.darklang.com/what-is-dark/ [3] https://blog.darklang.com/how-dark-deploys-code-in-50ms/