css-only-chat VS tanka

The idea of using CSS-triggered requests for analytics was really cool to me when I first encountered it.

One guy on twitter (no longer available) used it for mouse tracking: overlay an invisible grid of squares on the page, each with a unique background image triggered on hover. Each background image sends a specific request to the server, which interprets it!

For fun one summer, I extended that idea to create a JS-free "css only async web chat": https://github.com/kkuchta/css-only-chat

Isn't CSS Turing complete? Someone even implemented a chat client in it: https://github.com/kkuchta/css-only-chat

If it's something like a new reply to an issue raised, then you can either have it so these only show when the page reloads. Depending on how critical these notifications are, probably not the best solution. An alternative is to have a page that never stops loading. I've never actually used this approach, but I remember this guy used the approach for a JS-free chat system: https://github.com/kkuchta/css-only-chat

Here's an actual CSS-only implementation of a chat app that I happened to stumble across yesterday while tinkering: https://github.com/kkuchta/css-only-chat

I would recommend implementing a similar API to Grafana Tanka: https://tanka.dev

When you "synthesise", the returned value should be an array or an object.

1. If it's an object, check if it has an `apiVersion` and `kind` key. If it does, yield that as a kubernetes object and do not recurse.

Maybe you'd like jsonnet: https://jsonnet.org/

I find it particularly useful for configurations that often have repeated boilerplate, like ansible playbooks or deploying a bunch of "similar-but" services to kubernetes (with https://tanka.dev).

Dhall is also quite interesting, with some tradeoffs: https://dhall-lang.org/

A few years ago I did a small comparison by re-implementing one of my simpler ansible playbooks: https://github.com/retzkek/ansible-dhall-jsonnet

- validation is often impractical (at least identifying exactly where the error is… I’m looking at you Helm!)

Unrelated to OP, but you can leverage Tanka to extend helm charts with functionality not provided by upstream.

https://tanka.dev/

Although jsonette might be considered more complex Tanka is a great alternative for k8s config management.

At Grafana Labs we're using jsonnet at scale, while being a powerful functional language it is also excellent for rendering JSON/YAML config. We have developed Tanka[0] to work with Kubernetes, for other purposes I can recommend this course[1] (authored by me).

[0] https://tanka.dev/

[1] https://jsonnet-libs.github.io/jsonnet-training-course/

If you're hitting the limits of Kustomize, maybe look at Tanka as well.

Yes, try Tanka.

yes. basically. and this is a path that multiple people are trying to solve. e.g. AWS CDK8s, https://tanka.dev/, etc

Compose would be awesome.

http://tanka.dev

(Note I work for Grafana Labs who fund Tanka and use it for all production config)