2023-08

2023-08-04 JetPorch Dev Blog #1 (projet abandonné)

Hi everyone!

Thanks for signing up for this newsletter, if you have, and if you have not, at least for thinking about it.

I’m going to be using it for both announcements and development blog topics about Jet. If you decide that dev blog posts are too much and you only want announcements, you can tweak what categories you subscribe to in your substack settings!

So, yeah, the Jet has cleared the runway! Today is Friday, just a handful of days after announcing this project, and we’ve already got 292 users that joined chat in Discord and over 200 for this Substack!

I am so happy to have you and be a part of all of this again, and we are going to deliver on and exceed expectations! For comparison, I don’t exactly remember, but I was floored when ansible had only 40 people in chat, and I think that was a few months in 2012 after starting the project.

It feels good that people have faith in me on this one and I will not let you down .

I could write some marketing junk about how the need for classic IT orchestration/automation is still there in light of Kubernetes and blah blah blah, but you already know this probably. While some people are on all Amazon AWS lambda architectures or hosted Kubernetes, they are also a hostage to cloud provider pricing and decisions when you do this.

Most people have lots of stateful systems and data/messaging layers. Large enterprises have datacenters that are only growing. There’s machine learning and HPC. Networking is big - I should probably share some thoughts on where that needs to go at some time.

Emergency patch management.

The need for orchestration has increased and not lessened. With lots of interest in edge computing and many trying to de-cloud, some folks just want to manage VMs in classic ways. Some people have systems that were always managed that way, and seeing all the complexity hell of the alternatives, I don’t blame them at all.

I want to help all of these folks, both enormous, large, and small — and it IS possible to make one tool that does all of that. So back to it with the status updates!

While I can promise more technical (and Rust!) details in future posts, here’s what’s currently done so far for Jet:

…

So yeah, things are good! Rust does raise the barrier to entry for developers, but I think we can make a core module pattern that is very well abstracted and easy to work on, and again, any module that speaks JSON is going to work fine too. We can probably help people learn Rust just like Cobbler helped some people take an interest in Python back in the day.