Recent submissions

Comment · 2 years ago
Comment · 2 years ago
Comment · 2 years ago
I'd say the developer experience is completely different. With Celest you can almost pretend you are writing the frontend and backend code as one single codebase. And then you change a flag and the part of your code that needs to be in the cloud is moved to the cloud, seamless. I think you have to try it out to really grok how much easier it is.
Comment · 2 years ago
Just to clarify what Dillon said:

When you do `celest deploy` it sends your current code to the cloud. After that if your code contains: `celest.init(environment: CelestEnvironment.production);` it will use that code you just sent to the cloud. If your code contains `celest.init(environment: CelestEnvironment.local);` it will use the code you have in your local machine.

But in practice you develop locally, so you don't need to deploy all the time.

Also, you can call `celest.init` as many times as you like, while the app is running, to change from local to cloud and vice-versa, on the fly!

Comment · 2 years ago
Committing to open-source the code (and provide detailed instructions on how to run the code) in case the company shuts down is the most important. It could be part of the service contract. I've read all parts of the Celest code which are public, and I can attest it's very well-written and easy to understand.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton