That's interesting, I suppose there are advantages to that. I personally believe those advantages don't outweigh the downsides of forcing users to run code in their browsers but that's an interesting perspective.
Scoopta
joined 2 years ago
Dragonfucker strikes again. The number of posts I've seen by him or about him in here is... something
Is that really easier than just responding to clicking things server side? Again I fully understand there are some use cases where that's just not possible but in my, admittedly limited, web development experience you can get a whole heck of a lot done server side with no JS at all
Discord I get because it's real time chat. Gmail I get less so, it has some real time chat stuff but the core functionality could be done with far less JS IMO. Maybe I just feel that way because I'm a JS minimalist. Unless the website's core function needs JS(real time chat etc) I'm a firm believer you should be able to disable JS and the website should not break.
As someone who believes in, deploys, and locally validates DNSSEC I disagree with your meme lol.
I was going to make a similar joke -_-
Tl;Dr: yes, for the most part
IoT type devices have mixed support. Even if v6 is supported by the device some stuff in general can be squirrelly if you connect it to a v6 only network. Pretty much all typical user operating systems work fine on v6 only networks though. Windows typically uses v6 LLAs to connect to printers even if the network has no v6.
Yeah, it's definitely preference, I'm just stating mine...in an admittedly slightly obnoxious way lol.
Nah, thin is best
This is funnier than the joke
It isn't really future proofing, it's becoming increasingly important now. IANA exhausted their v4 supply in 2011, most RIRs followed shortly after. I believe Africa is the only region left with available IPv4 addresses. Depending on where you live and how big your ISP is even having a v4 address is iffy. A lot of smaller ISPs already put customers behind a double NAT. NATs in general add latency to connections and make inbound connections difficult. A good dual stack network typically has lower v6 latency. There are also several popular server hosts that charge extra for IPv4 connectivity because of the increasing scarcity. An IPv4 address on AWS is more expensive than their cheapest server offering for example. This means using APIs for v4 only services can add an uncesscary cost burden to consumers of the API depending on their needs. Ultimately it's not important for this website because it's a joke but it's important for anything serious.
Keep in mind that back in 1980 when IPv4 was introduced there were more people than IP addresses. Even in 1980 it was impossible for every person to get just a single address. For the job IPv4 was given of connecting the world it actually failed out of the gate from a certain perspective. IPv4 was never adequate for the task we gave it and over time it's only become less adequate. It's a tad silly that v6 was introduced in 1995 and is still the "protocol of the future."
Anyway, rant over, see this nifty website, they provide shame as a service lol. https://whynoipv6.com/
๐ค the black hair girl looks familiar, can't place her though