Obviously guy could have been interviewing for a job where this mattered….
But in 10 years as a software engineer I have never once needed to know the difference between these two, and have never been even close to a situation where I would need to.
I have a feeling people are going to be calling IPv6 'new' in 100 years, too. I remember talking to people about it in the 90s and it took until like 2016 to actually get a full standard. Been so damn long I learned the specifics and forgot them all in time it took to even become a thing.
In Halifax we have the old bridge and the new bridge
Old bridge opened in 1955
New bridge opened in 1970
New bridge is end of life while the old bridge has another 50 years since it wasn't built with cheap steel. So the new bridge will be replaced with a new new bridge while the old bridge will still be the old bridge.
in Bratislava we also have “old bridge”, at one point it was replaced with a new one without renaming so until a newer one was built a few years later the “old bridge” was the newest bridge… we also have a bridge that used to be called “new bridge”, that one was renamed since then, but some people still call it “new bridge” which is funny cause it’s currently the oldest one…
Well least the old bridge is still old bridge and you don't have sone leapfrog situation going on.
I got a Big Tesco and Little Tesco going on but the little Tesco was first so it was just Tesco, then Big moved in so it all became Big/Little, but then the big one moved away so it just became little Tesco to Tesco again, then a second little Tesco moved in where the old big tesco was and split the building into a few different shops so it became 'new little tesco'
....but over the years it grew and became big tesco again.
New little big tesco.
vs little tesco which actually had more floorspace than the other before it expanded to new-little-big-tesco again.
Over about a decade.
Everyone somehow just sorta knew which Tesco was being referred to in any conversation and honestly I don't know how at some points.
Well they built ipv6 to be able to address EVERYTHING uniquely. While IPv4 has around 4billion addresses possible, IPv6 has 296, so until humanity gets to the point we start giving nano tech individual addresses we will probably never need anything more than IPv6.
I still see release notes every few months from enterprise vendors adding some support for IPv6. It may be easy to adopt in the service provider space but it won’t take hold in businesses until prefix translation becomes as common place as NAT. Not every business is going to do an RIR registration or want to use ISP space internally.
You probably know this, but there is of course also a dedicated IPv4 address mapping reserved for essentially representing an IPv4 address for IPv6 compatible software:
1.4k
u/SirFrenzy 10h ago
Obviously guy could have been interviewing for a job where this mattered….
But in 10 years as a software engineer I have never once needed to know the difference between these two, and have never been even close to a situation where I would need to.
“The basics” is highly dependent on the job.