It’s pretty clear that you didn’t actually watch the video… The video has nothing against TADC…

Even if all support is dropped, everything is running on open source software, so nothing is going to stop working as a result of dropped support.

Finding replacements might become tricky at some point though.

It doesn’t really matter whether Zigbee was merged into something else, because it simply doesn’t have any technical means of phoning home. It simply can’t access the Internet.

There’s no intermediate corporate owned servers, there’s no proprietary software.

So it doesn’t really matter what the corporation does because it can’t affect my “smart” devices.

That depends on the kind of “smart”.

I have a bunch of IKEA “smart” light bulbs, but they are connected through a Sonoff USB Zigbee dongle. And all of it is controlled through the open-source zigbee2mqtt and home-assistant.

No one, but myself and my family, have any control or ownership of any of those devices.

Do whatever you want, as long as it doesn’t harm others.

Forbes article about it: https://www.forbes.com/sites/maryroeloffs/2023/07/27/tesla-exaggerated-its-cars-driving-range-and-canceled-service-appointments-if-drivers-complained-report-says/

You are correct. And yes that is kinda the whole point of the distilled models.

32b is still distilled. The full one is 671b.

Quite a lot of young women jumped on the grey hair trend where I live. But of course it might not have been a trend where you live.

Here’s a bunch of examples: https://www.latest-hairstyles.com/color/silver.html

You are aware that there were an almost global trend in 2024 of dying your hair grey, even for young women, right?

Systemd?

My team is constantly looking for new technologies to make sure we’re not turning ourselves into dinosaurs. We all know that Kubernetes won’t last forever, something better will come along some day.

That being said I don’t really see the full value of Triton or Xen with unikernels… They might have a bit less performance overhead if used correctly, but then again Kubernetes on bare metal also has very little overhead.

Kubernetes is certainly comes with a learning curve, and you need to know how to manage it, but once you have Kubernetes there’s a ton of nifty benefits that appear due to the thriving community.

Need to autoscale based on some kind of queue? Just install the Keda helm chart

Running in the cloud and want the cluster to autoscale the nodes? Just install cluster-autoscaler helm chart

Want to pick up all of your logs and ship them somewhere? Just install the promtail helm chart

Need a deployment tool? Just install the ArgoCD helm chart

Need your secrets injected from some secret management solution? Just install the external-secrets helm chart

Need to vulnerability scan all the images you are using in your cluster? Just install the trivy-operator helm chart

Need a full monitoring stack? Just install the kube-prometheus-stack helm chart

Need a logging solution? Just install the loki helm chart

Need certificates? Just install the cert-manager helm chart

The true benefit of Kubernetes isn’t Kubernetes itself, but all the it’s and pieces the community has made to add value to Kubernetes.

Apology accepted, and thank you for not name calling.

And yeah, if you can save the ops team salaries by picking Heroku, then it certainly might offset the costs.

When you talk about Triton, do you mean this? Because funnily enough one of their bigger features seems to be that you can run Kubernetes on top of it. It looks pretty cool though, but I must say it was quite hard to find proper info on it.

Triton also seem to push for containerization quite heavily, and especially Docker… So when you talk about Triton are you suggesting to use the Infrastructure Containers or Virtual Machines instead?

I’m not quite sure what you are getting at… Are you implying that I’m autistic because I only have 10 pods in a Kubernetes cluster?

Presently our clusters run roughly 1400 pods, and at this scale there certainly are benefits to using something like Kubernetes.

If your project is small enough to make sense on Heroku, then that’s awesome, but at some point Heroku stops making sense… both for managing at scale, and costs. Heroku already seems to be 2-4x as expensive as AWS on-demand. Presently we’re investigating moving out of AWS and into a datacenter, as it seems that we can reduce our costs by at least an order of magnitude.

The right tool for the right job.

I agree that many small businesses jump to Kube too early. If your entire app is a monolith and maybe a few supplementary services, then Kube is massive overkill.

But many people also tend to overlook all of the other benefits that suddenly become very easy to add when you already have Kube, such as a common way to collect logs and metrics, injecting instrumentation, autoscaling, automated certificate handling, automated DNS management, encrypting internal network traffic, deployment tools that practically works out of the box, and of course immutable declarative deployments.

Of course you can build all of this yourself, when you need it, but once you have the foundation up and running, it becomes quite easy to just add a helm chart and suddenly have a new capability.

In my opinion, when the company it big enough to need a dedicated ops team, then it’s big enough to benefit from Kube.

On slow terminals k9s can be rather sluggish when scrolling through the lists

If you’re on Android, then Firefox can indeed have uBlock Origin there too

You sure about that? https://lemm.ee/post/49389586

The DuckDuckGo search engine gets it’s results from the Bing search engine

Encryption is really really hard, and avoiding some form of sidechannel attack is much much harder.

Sure key exchange also isn’t trivial, but I would say that key exchange is significantly easier. Care to elaborate?