Looks like v3.0 just dropped, though after a very cursory glance at the release notes, I wonder what motivated the major bump specifically.
I deploy on a single machine with Docker, as my apps are both small scale and non-critical (people pay for them though). Kubero popped up when I researched how I would do a multi-server setup should the need for High Availability arise. It might flatten the learning curve and drop the operational overhead of Kubernetes enough to push me in this direction.
As for running the cluster myself, I probably would try to run K8s on talos.dev as well.
I will peruse your learning path when I am done with writing my master's thesis. Thanks for putting it together!
Lots of bullet points and keywords about the "What" : provable recursion, next-token prediction, and formal verification... and all items in "What makes it special". Can you provide a practical motivation, even speculative for people like me who have little time? Not necessarily "What use does it have right now", but "The qualitative difference with other models might enable use case XYZ in the future".
I have noticed it is low power and this is great in itself. What does the more rigorous formalism bring to the table? No snark at all, I am fascinated by formal methods, but still looking at them from afar.
My work is about inferring solutions to Constraint Satisfaction Problem by using belief propagation in the corresponding constraint network, a few keywords caught my eye here :)
Do you have any illustrative example so I can understand better what you are hinting at?
Not exactly the approach your describing, but Futhark[0] offers an alternative to CPU execution, it compiles to CUDA or OpenCL to run on GPU (or multi-threaded CPU).
Is the amount of data transfer the main reason to use JSON or do you find Web Components play better with JSON payloads? I could imagine the template string being rendered on the server, fetch()-ed by the client and swapped with this.innerHTML.
Do you manage any amount of cross-component state? It's one use case where JSON would win over "HTML over the wire".
> I suspect that all the free hobbyist FOSS labor artificially depresses dev salaries, hurting everyone else. Otherwise, the FAANGs would have to hire people to replicate what they currently get for free.
The way I see it, FOSS enables a ton of smaller entities to launch products when they would not have the capital otherwise (see: anything built on Django). Those represent a lot of jobs too! This could be the software version of the Jevons Paradox.
Megacorp are a different problem. They do contribute back to the commons, but this seems like a drop from the bucket of the quintillion dollars they represent. Is it fair? That's a moral judgement, because software being FOSS means its legal in any case.
> Moreover, well-known algorithms for linear programming like simplex and primal-dual methods have straightforward (and illuminating!) combinatorial interpretations when restricted to minimum-weight bipartite matching.
I you have any resource illustrating this point, please share. I would be very interested.
I liked this video [0] about how the Hungarian Algorithm is a particular case of the primal-dual method and I am eager to dig further.
I applaud the benchmarking though.