Darklang lets you build trace-driven, deployless, serverless backends. Join the community at https://xitter.cf/t.co/z5sYaMXCgA

San Francisco, CA
Joined February 2019
Darklang retweeted
In 2021, we started rewriting Darklang from OCaml to F#. Finishing up our session replays from #fsharpConf 2023, we discuss why we chose F# over OCaml (and Rust!), and discuss how it's going, what we love about F#, and what we miss. 🎥 msft.it/60199GnWJ
1
9
24
18,254
Darklang retweeted
It's been 2 years since I last built using @darklang. Tonight I built an API, nothing fancy, but it was a quick and fun build. I should use Darkland more often.
2
11
3,832
What I'm working on for @darklang in April
1
1
5
5,398
This piece is soooo much more than a product announcement, even for the most forward-looking software development product of the decade. 🙃 The headline is, the tiny @darklang team is ripping out the Dark editor and replacing it with AI-based code generation.
3
8
87
50,079
Giving a talk at @HoustonFPUG via Zoom tonight, and I'll be going into a lot of recent stuff about @darklang that hasn't been covered elsewhere. You should join!
Feb 15 Meeting: Paul Biggar on "Darklang: A Functional Language for the Cloud" tinyletter.com/hfpug/letters…
1
1
2,066
What I'm building for @darklang, December 2022
1
1
Darklang retweeted
In case twitter dies soon: - darklang.com/discord-invite - RSS: blog.darklang.com/rss - darklang.com/mailing-list - ⭐️ github.com/darklang/dark Working on a mastodon
2
4
24
What do you want the future of programming looks like? For @paulbiggar less is more. Episode is out NOW! @darklang devtools.fm/episode/42 Full episode for patreon members 👇️ patreon.com/devtoolsfm
How does @darklang handle migrations? As a language feature 💅 Catch the full episode with @paulbiggar tomorrow!
What is deploy-less development? How might a language support it? Find out all about this and more on this Friday's ep w/@paulbiggar from @darklang
Darklang retweeted
.@darklang continues to be my favorite tool for things that *should be easy* today: setting up a simple webhook listener and persisting the data until you know what to do with it
1
3
Why build @darklang? To shed all the infrastructure baggage we carry from the last 40 years of application development. Catch the full episode with @paulbiggar this Friday
5
2
11
I mean obviously the layoff. Sucks for everyone involved, even if there was no better option. I think slowing down how @darklang is built will prove to be a positive in the long run, but took a while to come to accept that
1
1
4
(You mean why _isn't_ @darklang open source, right?) A license should match we want you to do with the product. Main goal of @darklang is we remove tons of complexity by running it for you. Other reasons: (AWS, sustainability, open source not meeting its goals, forks bad)
1
1
1
No, not at all. Anything interesting to steal? In general, I don't look around for new and revolutionary things with @darklang, as it has enough that fall out of the initial design, and we've enough work ahead of us. But always happy to hear good ideas.
For @darklang to be self-sustaining and (large-scale) products built on it. Also want to see @darklang influence what others are doing in the industry. Have already seen things like natto.dev which say it has, that's lovely to see
1
1
2