Early bad experiences made a lot of people reluctant to try again.
There's a lot of edge cases to bite people still.
That said, something like 50% of users have working v6 now, which helps to file down the edges. Growth of v6 in the last 10 years has been much more significant than the previous 10 years. I suspect the next 10 years will be pretty significant, too.
I don't think many organizations are in a position to force adoption though.
You have mandates from say US government for government services and vendors and similar in some other countries. Some countries can force it through strong regulations on equipment sales. And then there's Jio (and maybe other ISPs) that have significant market power in some locales and a significant lack of v4 resources and can strongly encourage vendors and partners to support v6 for better service to users on their network.
If you're willing to jump through hoops, you might want to check if it's still possible to setup an EIN and a new SMB T-Mobile 5G internet and get a static ipv4 for a small charge per month.
Personally, I had major issues with the 5g wan equipment and my network as well as a snafu with ordering... Sales rep put in the order for a static ip with a ssn based SMB account, but that got removed during provisioning and couldn't be added back. (And then billing issues because the account didn't get cancelled properly, either)
Sure, but if they're a new ISP, chances are they have a hard time getting IPv4 and they likely run CGNAT. If they run CGNAT, the benefit of IPv6 is there's a lot of high volume traffic that will move to v6 and the CGNAT use will be smaller. Routing v6 packets is much easier than tracking connection states and munging packets...
If they have enough v4 for all their customers, sure fine.
Unfortunately, he.net tunnels have terrible reputation, so if you use this for your regular browsing, you're likely to get hit with more captchas than if you're on a cgnat with well behaved neighbors. Some sites will just not work, with no errors, because why waste errors on networks with bad reputation.
It wasn't always like this, but it was for me the last time I tried.
Cars are often sold. If everyone knows that nobody will buy it in 15 years, the person buying it in 12 years will pay less, which means the person buying in 9 years pays less, etc, so the person buying new doesn't recoup as much and has less to spend on a replacement.
> Not even traffic patterns will give you up in the age of ubiquitous websockets and/or http2 streams.
SSH is dead simple to detect, because the server sends an outbound greeting in ASCII text; and the client doesn't send anything until it gets the greeting. The binary protocol does not look like a TLS stream at all either.
In most (all?) US states, you need a license to be a _Professional_ Engineer. This is a legal distinction that carries weight _and_ legal liability. It doesn't mean that you cannot "engineer" without a license. There's legal distinctions on what work a licensed engineer can and cannot do, and what work must be done by or under the supervision of a licensed engineer. e.g. a junior's work has to be signed off by a supervising PE. To become a PE, a licensed Engineering Intern must have first passed a preliminary exam issued by the state and worked under a PE for a minimum amount of time with satisfactory performance (think apprenticeship).
It's the legal liability that SWEs don't want. e.g. You wouldn't be able to just slap "This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE." on your software and walk away from it when lives are at stake. A so-called Profession Software Engineer would have to accept liability for their work product, and those of the juniors working under them.
I started down the road to becoming a Professional Engineer while I was in college as I studied Electrical Engineering and was more interested in hardware/power engineering. I took, and passed, the Engineering Intern Test in my state (which is the preliminary exam you take before you can start your journey to become a PE). Then life happened and job/career opportunities took me in a different direction/industry, and I've been doing software instead. So, I never became a licensed Professional Engineer. I'm still a licensed engineering intern, though. I'm still bound by the legal and ethical standards that it entails and could lose my license for violations.
There are certainly things where you need to have an officially licensed engineer actually stamp the plans. That doesn't mean everything about the plans was done by someone who holds that stamp, just that they were reviewed and signed off by the person holding the license. Lots of people may work on those plans. They're still doing engineering work. And that's just for the kinds of things which actually require a licensed "engineer".
There's still tons of jobs which is often still called "engineering" which often don't involve anyone who has a stamp. Few electrical engineers, chemical engineers, mechanical engineers, or lots of others actually have any kind of engineering license. They still get degrees in things like "Bachelor of Science of Electrical Engineering" or "Master of Science in Mechanical Engineering". Their job roles usually have "engineer" in it. And yet it seems like the job people only really criticize as "you're not an engineer, engineers are licensed" is SWE.
Elections certainly have consequences, and I wish acting outside constitutional scope had consequences, too. (maybe this specific issue is within scope or there is a reasonable question about it, but so many other issues seem unreasonably out of scope, IMHO)
I don't know any of the details, but dram is basically a whole lot of bits and and each bit is one capacitor and one transistor.
In the diagram for 8F Squared, there's a capacitor at every other junction between word lines and bit lines. If the lines (and inter line spacing) are 2F wide, you have one bit in a 2Fx4F rectangle, or one bit per 8F squared.
In the diagram for 6F Squared, there's a capacitor at every bit line on every other word line. If the lines (and inter line spacing) are 2F wide, you have one bits in each 2Fx3F Rectangle, or one bit per 6F squared. (I guess the word lines without bits are needed for spacing or to drive the transistor or maybe it's just illustration and doesn't mean much)
In the diagram for 4F Squared, there's a transistor at every bit line on every word line. Now you have a bit in every 2Fx2F square, or one bit per 4F Squared.
If you can make dram in all three styles with the same F, 4F squared is twice the density as 8F squared. If the F doesn't hold constant, it's squishier, of course.
I was not really active in computing back then, so I don't know how widely distributed these releases were, but NT was clearly gestating longer than Win32s.
There's a lot of edge cases to bite people still.
That said, something like 50% of users have working v6 now, which helps to file down the edges. Growth of v6 in the last 10 years has been much more significant than the previous 10 years. I suspect the next 10 years will be pretty significant, too.
I don't think many organizations are in a position to force adoption though.
You have mandates from say US government for government services and vendors and similar in some other countries. Some countries can force it through strong regulations on equipment sales. And then there's Jio (and maybe other ISPs) that have significant market power in some locales and a significant lack of v4 resources and can strongly encourage vendors and partners to support v6 for better service to users on their network.
reply