Around here, it isn't possible to do native lawn. The grasses are too tall and the low groundcovers can't be walked on. I'm trying to plant wildflower meadow but it will be a couple of feet high.
My idea is that there are two types of lawns. There are the lawn you use, and it is fine to be grass. But there is a lot of lawn that is landscaping and that can be native plants.
Cars don't follow traffic laws. Cars roll through stop signs and run red lights. Cars speed and weave through traffic. They go the wrong way down one-way streets. Since cars are much bigger, this is much more dangerous.
What happens when your new version is broken? Kubernetes would rollback to old version. You have to rerun the deployment script and hope you have the old version available. Kubernetes will even deploy new version to some copies, test it, and then roll out the whole thing when it works.
Also, Kubernetes uses immutable images and containers so you don't have to worry about dependencies or partial deploys.
Citrus isn't one species but hybrids of citrons, mandarins, pomelos in Citrus genus. It isn't like cabbage that produces multiple cultivars. Citrus genus is supposed to be diverse cause they do hybridization in wild.
I also think going back farther is a stretch. The first assembly languages were imperative, but what made Algol, Fortran, and Cobol interesting were functions and other features that allowed complex programming. Algol has the most descendants but Fortran was the first imperative programming language.
I have come to think that having both SLAAC and DHCPv6 were a big flaw in IPv6. SLAAC is awesome but having two config mechanisms is confusing. It doesn't help that Android refuses to support DHCPv6.
I think SLAAC came from world where computers were expensive, DHCP servers were separate, and they wanted to eliminate them. But we are in world where computers are cheap and every router can run DHCP.
We could have had easy config with DHCPv6 giving out MAC based addresses by default. The auto config would still work on link-local.
there's Prefix Delegation support since Android 11 (so there's some DHCPv6 support, but of course in a fucking worse way with the mandatory "we know better" attitude)
NAT64 doesn't make sense for consumers. There are too many apps that hardcoded IPv4 in their code. People are going to complain that their old Xbox games don't work.
For most people, dual stack works fine. For mobile, the solution is 464XLAT that translates locally. There is MAP-E that does translation on gateway with IPv4 on local network.
For businesses, NAT64 makes more sense cause they can control what software is running. Even there, usually have to make IPv4 subnet for the old printers.
Blasting through hard rock is easy. Finland has perfect rock and makes lots of tunnels with blasting. Soft rock needs support so TBM tunnels and shores up.
It is the British that changed things. They also used to call it soccer and then changed in the 1980s. Canada and Australia still use soccer, probably cause they have native footballs.
My idea is that there are two types of lawns. There are the lawn you use, and it is fine to be grass. But there is a lot of lawn that is landscaping and that can be native plants.
reply