91–100 of 159 posts
This is a cool idea regardless of being simple or complex. Who cares, its cool. Nice job
This is ~17k lines of shell scripting and claims to be "simple". Kuberentes is probably ~1m lines of Go. I'm not entirely convinced that this is less complex (simpler) than Kubernetes. There are many factors in complexity, but a big one for me is what I have to hold in my head – global state. From any given point, what do I need to understand to know what's actually going on. For Go, this is actually comparatively li…
To be fair Kubernetes itself probably has 17k lines of bash, and it is a good thing. It is the first go-to project that I use as a reference for bash scripting best practices. edit: wc reports 47023 lines in *.sh[1], out of which 23836 are unique[2]. [1]: find . -name '*.sh' | xargs cat | wc -l [2]: find . -name '*.sh' | xargs cat | sort | uniq | wc -l
It can distinguish between actual lines of code, comments and empty lines for a lot of different languages.
Earlier quoted context omitted.
Thanks :) The real use case is super simple clusters, which could be just 1 node, no etcd, no API (SSH managed), no iptables. Simplenetes is not a living breathing thing which auto heals it self, it's a deterministic approach where you can see your cluster with all hosts in the git repo which represents the cluster. Also, it's focused on making local development easy, so you can develop in a micro services architectu…
> clusters, which could be just 1 node Despite whatever the k8s crowd misuses the term to be, 1 node is not a cluster. It might be a single node managed using cluster-capable technologies, but it's still not a cluster.
Main upside is that I can put Kubernetes on my resume.
This is my kind of tom foolery. Love it. You should come work with me at Heroku: https://www.heroku.com/careers/software-engineer-heroku-runt...
While Kubernetes is hopefully Very Good, it is complicated, and I have often wondered what other approaches would yield (e.g. more imperative ones, because writing admission controllers is not exactly easy). So I'm glad to see people playing around, though I don't know if this amount of bash is healthy or if 17,000 lines is simple.
Earlier quoted context omitted.
To be fair Kubernetes itself probably has 17k lines of bash, and it is a good thing. It is the first go-to project that I use as a reference for bash scripting best practices. edit: wc reports 47023 lines in *.sh[1], out of which 23836 are unique[2]. [1]: find . -name '*.sh' | xargs cat | wc -l [2]: find . -name '*.sh' | xargs cat | sort | uniq | wc -l
You might enjoy having a look at https://github.com/AlDanial/cloc It can distinguish between actual lines of code, comments and empty lines for a lot of different languages.
It's the same as cloc, but ludicrously fast.
Earlier quoted context omitted.
Where?
- "Let's put the Dev and Ops back into DevOps." - "Simplenetes doesn't go there because that is when DevOps becomes MagicOps." - " You enjoy the simple things in life."