ruben_varnish

Let us get back to you on that.

Leaning towards making the modules/examples permissive, indeed.

Imagine having all that being run by Varnish as the data plane?

Do you think the whole MACH stack users would then move their workload to such a controller/ingress/gateway?

I think they wouldn't, because they don't necessarily understand (or need?) the advantages of caching at scale and flexibility that Varnish provides.

But if you say that you will accelerate everything in their K8s cluster... Then maybe ;)

We'll see. I have a wish for Kubecon in Q4

I do owe you an email reply on that. I haven't forgotten that, just so you know.

But yes, Varnish Cache is not exactly what you would call Cloud Native.

Varnish Software have launched Pro currently on AWS only at a much lower price point, but it is still somewhat limited. I think that a Free-tier providing some of the goodies you mention would also cover much of what's needed for today's workloads including better memory management, in-core TLS and a better developer experience by having much better K8s support. Much of this could and should go into Varnish Cache, but that is a longer road as the project as such has a different focus than we do.

Expect more on that front this year @pbower :)

TinyKVM is certainly technology that in itself is rather groundbreaking, but it is obviously even more powerful in the context of request handling at lightning speed. But you are right it could be used for other things.

Would you have read this if neither Deno, Varnish or TinyKVM would have been in the title? ;)

But we hear you. Will put a page on our website and should probably consider seeing up a community site as well as it is indeed, grabbing some attention.

One of the most well executed marketing stunts ever seen must be the "Powered by Ubuntu Linux" stickers that System76 provided back in the day when your OS was still relevant and people thought Ubuntu would be the next big thing in the desktop/laptop space.

I have personally learned so much from that experience that it is very difficult to overlook when thinking of brand hacks.

Every time a friend or colleague asks why I use "that" I simply thrown my laptop to the floor, pick it up and continue working on it.

Then I ask them to try the same with their Apple laptop.

That normally makes them never ask such questions again.

I learned that from an IBM (and later a Lenovo) sales person when presenting the X series. It's designed and built to tolerate real use. And some abuse :-)