pbiggar

41 ms·

511.
by pbiggar 7y ago
We're not suitable for GDPR compliant applications yet. Now that we've got Dark actually working and shown to the world, we can start addressing it. Currently hosted in GCP, US west.
512.
by pbiggar 7y ago
> I think the fact it maintains the "backend/frontend" separation makes it an awkward product solution imo. When we were thinking about the scope for Dark, we briefly thought about trying to remove all the complexity for f
513.
by pbiggar 7y ago
GCP.
514.
by pbiggar 7y ago
We hope we can deliver! > Can apps written in Dark scale to 10k LOC or will the browser UI get jittery? We've had a number points where there editor became unresponsive and we had to rearchitect parts of it. We feel pretty confident
515.
by pbiggar 7y ago
Agreed about the 2D canvas; we've been cutting scope aggressively to launch this. We have a different metaphor in mind but it will take us some time to implement.
516.
by pbiggar 7y ago
Error handling is done with Results and Options. We have a concept called an ErrorRail to simplify this: https://medium.com/darklang/real-problems-with-functional-la...
517.
by pbiggar 7y ago
Thank you, Jack!
518.
by pbiggar 7y ago
When we were designing Dark, we wanted to be sure that it would actually be a thing that was safe to do, so it isn't just the same as hot reloads. Have a look at my video in the blog post: feature flags and versioning are a super impor
519.
by pbiggar 7y ago
> Can we access the data store/our data outside of dark? Yes and no. You can easily put an API in front of it so that you can expose it however you like, download it, etc. But there isn't something like a postgres connection st
520.
by pbiggar 7y ago
Hmmm, I wonder if it's a growth hack that Medium is doing. In incognito mode, i don't get the registration requirement. I'm told clicking "next" just gets you through it? Sorry about this, I think medium wasn't
521.
by pbiggar 7y ago
Thank you for the kind words! > The one thing that didn't get covered in the "Dark in action" video that should have is where do the twilio/slack tokens get stored? I'm sure there's some environment/glo
522.
by pbiggar 7y ago
We haven't started work on the built-in code review, but that seems like a cool idea, thanks!
523.
by pbiggar 7y ago
Yes, that was a bit vague, sorry. What I meant was that our datastores are simple key-value stores at the moment.
524.
by pbiggar 7y ago
Thanks!
525.
by pbiggar 7y ago
Specifically in the context of fundraising, we said "backends are way too hard to build, we can remove all the accidental complexity of infrastructure, deployment, and APIs". Many people felt that that was not possible. The "
526.
by pbiggar 7y ago
The model here is that we own the responsibility of making it scale. We haven't solved the problem of significant workload, but there doesn't seem to be any reason why this wouldn't work - certainly our current (low-scale) us
527.
by pbiggar 7y ago
Honestly, that's totally cool. There's a certain risk profile that's right for where Dark is now (new startups, low risk projects, under-resourced projects/teams). Folks with a different risk profile should not be using
528.
by pbiggar 7y ago
We charge for infrastructure (that is, we host your infra, so you pay based on usage) - this is also what we did at CircleCI. Small users will pay us very little or fit within the free tier. Huge users will pay a lot. We plan to support ent
529.
by pbiggar 7y ago
> Each of these tasks are hard problems individually, what gives you the confidence that a small startup can build all of them? All of this while trying to make your company profitable. For sure it's hard. FYI we're hiring: ht
530.
by pbiggar 7y ago
1. The "foreign function interface" in Dark is HTTP. So to do machine learning, either use a service that for it, or put your ML stuff in a container with a HTTP wrapper around it. 2. We plan to charge for infrastructure, on a usa
531.
by pbiggar 7y ago
Honestly, our "prototype" was screenshots from an 800 line demo, and about half the people we spoke to believed that this wasn't actually possible to build.
532.
by pbiggar 7y ago
Thank you for the kind offer! I will definitely reach out.
533.
by pbiggar 7y ago
We have user tested, and a ton of people have built full apps with it. That said, you are correct that it can be a rough experience at times, which is one of the reasons we're in private beta. We wanted to show people what we were work
534.
by pbiggar 7y ago
We've also built tools for guarantees around correctness. My video discusses our deployless tooling, and it's also discussed in the blog post: https://medium.com/darklang/how-dark-deploys-code-in-50ms-77... W
535.
by pbiggar 7y ago
We answer that a little in our FAQ: https://darklang.com/language#faq I don't think there are any languages that allow the same thing that Dark allows - the integration with the infrastructure is the whole point. I cer
536.
by pbiggar 7y ago
The collaboration is google-docs style. You can see if you're working on the same code as someone else, see the feature flags they're building, etc, to avoid conflicts. That said, we haven't tested this with teams of more tha
537.
by pbiggar 7y ago
We do intend the HN audience to love this too. Our target audience is developers building backends. We don't expect we'll wrestle people from their Emacs, so we're definitely not targeting all possible developers today, but d
538.
by pbiggar 7y ago
We will absolutely support light mode, and we plan to deal with many other accessibility concerns (I touch on that very briefly at the end of my video). This sort of inclusivity is massively important to us. I hadn't realized Dark mode
539.
by pbiggar 7y ago
Not planned. We plan to expose the APIs around this so you could build something yourself that syncs to github possibly, but that's not the design for sure.
540.
by pbiggar 7y ago
Apologies, we don't know why this is happening - something with medium and vimeo. The videos on our home page go fullscreen: https://darklang.com .

More ›