aejm

The problem: too much AI The solution: more AI!

They can relatively easily sink it, and in fact are required to be able to in order to get their US FAA launch license. As part of the environmental assessment specifically, but I could be wrong on that. For those curious, they have recovery teams on sight who can essentially shoot it to further puncture the hull or attach explosives even. They have experience with their Starship boosters not sinking off the coast of Texas and floating into Mexican waters.

Incredibly disappointed to see it will be using a gasoline combustion engine.

I think this version is an improvement over the old one! In particular how it highlights the packages in the ecosystem better.

I wonder if you would feel different after witnessing an execution (by guillotine)? I believe Camus is arguing that you would, giving his father as example of someone who similarly changed his mind.

Thank you for the clear response!

I notice there is an Enterprise Edition, can you please specify which features are not open source? Do you predict new features you add will be ee licensed as a way to pay back your VC funders?

A really solid looking editor! Just a heads up on small, mobile screen sizes: the UI elements of the top row overlap unusably, the rest of the UI seems usable just quite zoomed in and I really had to pan around a lot to do anything. Fundamentally a solid and usable UI, I’d recommend a little more polish on smaller screen sizes. Good work!

Thank you!

Using a JavaScript framework kind of defeats the whole purpose doesn’t it?

I agree completely with your sentiment. The word I use to describe it is “quality”! Most people don’t produce quality work or take pride in it, even beyond the tech industry. I believe the tool of AI is exasperating an underlying problem

Glad to hear you prefer Docker Swarm/Compose, I feel it’s a solid tool for when you need some of the more complex multi server deployments, and helps you avoid all the costs and complexities around K8s. Plus, running docker compose in development and docker swarm in production feels like the closest you can get to having your development environment match your production environment.

In the latest FOSS project I’m starting, I’m not avoiding all “open core” supposedly FOSS projects. In my experience, they’re the projects most likely to do a rug pull and change licenses. If they cannot commit to their entire project being free and open, they are less likely to actually be committed to the principles of free and open software.

While I was quite excited about some of the ideas being discussed in this project, it being VC backed is a complete non starter for me. Your claims of being built in the open don’t make me feel any better, you will eventually need to make returns for investors.

Thank you for taking the time to reply! Agreed, it does seem like any auditor would be able to verify all this information from other sources, but I really like the idea of having multiple independent levels of attestation for my organizations important financial and legal documents.

This is really good inspiration for some of my plain text accounting projects! Could you please go into more detail about your RFC3161 attestation of commits? I'm assuming you're signing your commits with a gpg key to assert that it was in fact you who made the commit. Do you use an external timstamping service and an external ca authority, or do you build your own chains of trust? If you were asked to attest your accounting commits, what would that look like to the auditor?