Looks good - not a knock, but for me I'd like comparisons to see how it does against the existing orchestrators/schedulers. Or at the very least, where it differentiates itself against them. Because choosing a new scheduler over more established ones is quite a risk, imo. I feel you have to sell why we'd take a risk with an unknown (to me) product.
Currently I feel like the site does a great job selling that Flockport has a lot of the fundamentals, in an easy to use package. Great. But I still want more info.
So in concrete terms as an example, how do you differentiate yourself when compared to Nomad?
edit: sorry to be typical overly negative HN commentator - I don't mean to be, I'm just seeking information, and feel the site is a bit lacking to describe that. I appreciate your hard work here :)
Thanks for the feedback. This is far from negative. There is definitely value in comparative docs that lets users get a quick overview, and we will put one together.
However we also want to start new conversations in the community about containers and orchestration and reach users who find existing platforms too complex. And we have put together a lot of content to kindle these discussions.
More technical scrutiny could lead to simplification and lower barriers for both users and developers.
Currently I feel like the site does a great job selling that Flockport has a lot of the fundamentals, in an easy to use package. Great. But I still want more info.
So in concrete terms as an example, how do you differentiate yourself when compared to Nomad?
edit: sorry to be typical overly negative HN commentator - I don't mean to be, I'm just seeking information, and feel the site is a bit lacking to describe that. I appreciate your hard work here :)
edit2: Something I love for new software is when they do comparisons, like this: https://www.nomadproject.io/intro/vs/index.html