3 ms·
IPv4 works just fine for websites. Also why would ipv6 appeal to developers? What do I care if GitHub supports ipv6 or not?
by kojon99 8y ago
IPv4 works just fine for websites.
Also why would ipv6 appeal to developers? What do I care if GitHub supports ipv6 or not?
- Faaak 8y agoSame old, same old. You care because you may need various IPs when doing complex applications; which you can't have right now because of IPv4 exhaustion
- augustz 8y agoI really wish IPv6 had a better argument than you can't get IPv4 addresses needed to build a complex application. The majority of complex applications being built today are being built to be IPv4 accessible and may even be using IPv4. You can use 17 million private addresses + buy plenty of public IPv4 addresses. AWS and Google are both building major clouds that are both complex and STILL heavily IPv4 oriented (I and others pinging them to add IPv6 for a long time). They throw in an IPv4 for every running instance and even their elastic IPv4's are cheap if attached to an instance.
- iknowstuff 8y agoIt reenables all of the devices on the internet to be able to directly connect to each other. No NAT, no STUN etc.
- p49k 8y agoDo we even want that anymore and is it still a smart idea?
- euyyn 8y agoThat decision should be taken by filtering (or just preventing it altogether) in each specific case. With dynamic IPs, it's already a no from the start.
- Rjevski 8y agoWe actually do want that especially for the internet of things, so that your lights and garage door keep functioning during an AWS outage that takes out the relay servers (used to work around NAT) or if the manufacturer goes out of business.