dark VS flyctl

Yes. Darklang was originally in OCaml using js_of_ocaml, and we ported it to F# using Blazor (https://github.com/darklang/dark/tree/main/backend/src/Wasm). It works.

We found that in dotnet 6, the code was much slower, with long startup times and a much bigger download, than in js_of_ocaml. It also had a lot of issues in running in a Webworker, which wasn't the case for js_of_ocaml.

In dotnet 7, the webworker issues are better and AOT is easier, so startup is faster. Download sizes are still bad, and it's still slower than js_of_ocaml.

However, dotnet allows almost any code to run in WASM, which js_of_ocaml had large limitations. This meant a decent chunk of functionality had to be worked around to make separate js vs native targets, which also was a massive pain and took a long time. Dune's virtual targets wasn't ready at the time - I think we were one of the test cases for it.

Why should I use this instead of https://darklang.com/

First it was probably Dark. They made a lot of noise some years ago, but then I never heard of them again (looking at their current website, looks like they moved on to AI now, obviously).

Reminds me of Darklang. Personally, I don't think vendoring cloud services into a language is going to be beneficial. I'm curious how the language deals with vendor updates. Do I have to upgrade the language then? If so, I see a lot conflicts coming from this. Then it comes down to Javascript or HCL, the HCL bit makes me think that the below statement is not as truthy as it is on the surface:

We still don't have all that many users (~100 active), so I'm not sure you'll find an answer here. But we collect that sort of feedback publicly, which might answer your question: https://github.com/darklang/dark/discussions/categories/feed...

I wish I could remember what took me to YCombinator's website on the 10th of October, 2022. That was when I first heard about Wasp and another language called DarkLang. After I learned about Wasp, I was intrigued and curious to know how it works, which led me to join the discord server the next day.

Some languages that try to integrate an HTTP server and a database:

Ur/Web: http://impredicative.com/ur/

Dark (Darklang): https://darklang.com/

There are others in this space I did not assess like Encore, Shuttle, Modal, and Dark. These were not assessed for the sake of time. If you're interested in IfC, I encourage you to take a look at these others.

Oh, finally! I was waiting to build my serverless CRUD webapp in Dark (OCaml + JavaScript and Fsharp?) until they had support for returning negative numbers on a GET request!

Fly.io is a platform that enables developers to deploy and run their applications close to their users. It leverages a global network of servers to provide low-latency, high-performance hosting solutions. It simplifies the deployment process by offering a powerful CLI and automated workflows, making it easy to deploy applications with minimal hassle. Additionally, Fly.io supports various programming languages and frameworks, including Next.js, making it a versatile choice for modern web development.

With the Wasp CLI, you can deploy the React frontend, Node.js backend (server), and PostgreSQL database generated by the Wasp compiler to Fly.io with a single command.

This is a MVP for Serverless Postgres.

1/ It uses Fly.io[0], which can automatically pause your database after all connections are released (and start it again when new connections join).

2/ It uses Oriole[1], a Postgres extension with experimental support for S3 / Decoupled Storage[2].

3/ It uses Tigris[3], Globally Distributed S3-Compatible Object Storage. Oriole will automatically backup the data to Tigris using background workers.

I wouldn't recommend using this in production, but I think it's in a good spot to provoke some discussion and ideas. You can get it running on your own machine with the steps provided - connecting to a remote Tigris bucket (can also be an AWS S3 bucket).

[0] https://fly.io

[1] https://www.orioledb.com/

[2] Oriole Experiemental s3: https://www.orioledb.com/docs/usage/decoupled-storage

[3] Tigris: https://www.tigrisdata.com/

Fly.io - Very similar to Heroku too, easy to use and support for multiple stacks/languages.

Fly.io is a cloud platform that allows developers to easily deploy scalable applications. In this article, we will introduce how to manage databases effectively in an application using Remix, Prisma, and LiteFS on Fly.io.

Deploying applications can be a complex and time-consuming process. App deployment tools, such as Fly.io, aim to simplify this process by providing a platform for easily deploying and managing applications.

To begin with, you could go with a Platform-as-a-Service (PaaS) provider like Heroku, or Fly for a more seamless experience. You can also do a bit of DevOps: set up a Docker installation on a VPS and deploy your app there.

To begin visit fly.io to create an account. Next install flyctl a command line tool for creating and deploying fly apps. macOS

For frontend deployment, I used Netlify (for the generous free package) and the recommended fly.io for server + database (also cheap package).

Create an account on Fly.io.