Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
pbiggar
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
57 ms
·
571.
▲
by
pbiggar
7y ago
We're manually doing SSL at the moment, and our customer controlled the DNS. Should be fixed now.
572.
▲
by
pbiggar
7y ago
We've got some stuff on our blog. See here and the links at the bottom: https://medium.com/darklang/the-design-of-dark-59f5d38e52d2
573.
▲
by
pbiggar
7y ago
Founder of Dark here. Here's a thing I wrote about docker before, that led me to create Dark. https://circleci.com/blog/its-the-future/
574.
▲
by
pbiggar
7y ago
Dark founder here. Many people remember writing directly on the server quite fondly, because it had a great turnaround. But we stopped doing it because it wasn't safe. Dark makes it safe [1], so you can start doing it again. [1] https
575.
▲
by
pbiggar
7y ago
> The scope they're claiming is gigantic, they must be taking compromises somewhere. There's no way is all unicorns and rainbows. There's two ways we deal with the gigantic scope: - do the most important stuff to validate
576.
▲
by
pbiggar
7y ago
Hi! Let me push back slightly on "visual programming". Dark looks and feels like writing textual code. There are some built-in visualizations, especially around code organization and infrastructure, but it's much more like co
577.
▲
by
pbiggar
7y ago
Founder here. This is fair. Dark is still quite early, and while we're talking about it, it's currently got a lot of sharp and ugly parts that we want to tidy up before we go public. Happy to answer questions on it though - I answ
578.
▲
by
pbiggar
7y ago
Founder here. Totally fair concern - we're not thrilled about the lock-in either because we want people to try Dark and see that it solves a problem for them. We're looking at ways to improve this - would love ideas, and will be w
579.
▲
by
pbiggar
7y ago
Yes, this is pretty close! There are multiple instances in the cloud - when a HTTP request comes in we look up your program from the DB and run it.
580.
▲
by
pbiggar
7y ago
Dark founder here. Yes, completely agree with this. To a certain extent, Dark is aimed at being what lambda/serverless should have been. The thing that frustrates me about Lambda (and really all of AWS) is that we're just dealing
581.
▲
by
pbiggar
7y ago
Cofounder/CTO here. Sorry this went up when I was sleeping, so I missed the discussion. I'll answer some things through the threads but if you have any questions for me I'm here.
582.
▲
Dark emerges from stealth with unique ‘deployless’ software model
(techcrunch.com)
5 points
by
pbiggar
7y ago
|
0 comments
583.
▲
by
pbiggar
7y ago
Link for the lazy: https://medium.com/darklang
584.
▲
by
pbiggar
7y ago
Yes, we'll have support for that, including handling sync conflicts when you get back online. It's not gonna be a great experience since Dark is really really designed for working on production, but it should work ok.
585.
▲
by
pbiggar
7y ago
Good question. The answer to most questions like this is "it'll probably be the same as now". I know it seems like everything is different, but we're not really trying to invent much new stuff, only what's required
586.
▲
by
pbiggar
7y ago
Thanks for pointing to that, it's super interesting. One of the things we designed Dark around was being able to safely and easily continuously deliver language and framework changes. The Zope 3 project was a disaster by the sound of i
587.
▲
by
pbiggar
7y ago
> What are the fundamental features of Dark that are not possible to add to an existing language? An obvious example is the structured editor. To do that, we have to have a language in which there is a meaning to every incomplete program
588.
▲
by
pbiggar
7y ago
Email me personally for now. I do plan to publish broadly later.
589.
▲
by
pbiggar
7y ago
Not currently but I'm sure there will be at some point.
590.
▲
by
pbiggar
7y ago
We did of course consider it. I don't think it's possible to use existing languages to do this. Presumably, we'd have to use Javascript as our basis cause everyone knows Javascript. But then we'd have people wanting &quo
591.
▲
by
pbiggar
7y ago
No, it's an ML. (You're right that we haven't published samples, we think people get distracted by syntax and we want to focus on the goals at the moment)
592.
▲
by
pbiggar
7y ago
No it's not! Sorry about that. Email me direct (see my profile) and I'll try to fix it.
593.
▲
by
pbiggar
7y ago
> Maybe the editor should be customisable via Dark itself? That's the plan!
594.
▲
by
pbiggar
7y ago
Thank you! Yes, your understanding is correct and your explanation is lovely. Much appreciated. A thing to clarify is that you're not really deploying code in 50ms. It's more that all the code you write is in production, behind a
595.
▲
by
pbiggar
7y ago
It's much simpler. Those have complex in-process hot swapping. Dark's "hot swap" is a write to a DB, then new HTTP requests use the new code. As we grow and start to look at compilation and optimization, I think we'
596.
▲
by
pbiggar
7y ago
Author here. Was this in response to the article or the title? Because the article goes into great detail about this. To answer, the whole system is based on feature flags (which are equivalent in this case to green-blue/canary release
597.
▲
by
pbiggar
7y ago
The sustainability of Dark is super important to use. We're not fucking around with customers' livelihoods. For our early customers, we have a handshake agreement that we won't leave them hung out to dry. If Dark was to shut
598.
▲
by
pbiggar
7y ago
Author and Dark CTO here. > Reading on Darklang.com I see they kind of address this. The ecosystem they’re building is training wheels for developers, a way to make “coding 100x easier.” No no no no no. This is not what we're doing.
599.
▲
by
pbiggar
7y ago
Thank you! I'm at https://twitter.com/paulbiggar or paul@darklang.com.
600.
▲
by
pbiggar
7y ago
The model is quite different to how people write code today. Instead of a process that takes code from your machine and sends it to prod (and thus has a lot of risk), you code in a sorta sandbox _in prod_. That is then enabled for users via
More ›