Scoopta

IMO if you have to put "you can't do xyz with IPv6" in your documentation...then you need to not ship that product...but Comcast is Comcast...sooo

IMO if you're serious about IPv6 you should probably have your own router running OpenWRT or the like. That's not to say consumer routers don't exist with good v6 support. AT&T provided routers have very good v6 support including full firewall rules for both v4 and v6 on top of the v4 port forwarding for NAT. We'll ignore their PD issues lol. Sounds like Xfinity might just be behind the times. I'd put OpenWRT on a router and use that instead of the ISP router anyway.

I believe OP is already aware of this. At least based on the wording in his post. He specifically says "opening ports in the IPv6 firewall." Could be mistaken though.

Honestly what I find kinda crazy about this is the price of $0.005/hr is the same cost as the cheapest EC2 instance, meaning you can get an entire server(low power but still) or a single IP address. Interestingly GCP also charges for in use IPv4 which I didn't know, last I used GCP they only charged for IPs you weren't using

Well the spec was created in 1995 and the 6bone(tunnel based testing network created in 1996) was shutdown in 2006 due to the increase in native routing. That is IPv6 had a sufficient internet presence that the test network no longer felt necessary...and here we are almost 20 years later...soooooooooooo...yeahhhhhhh. Tbh IPv6 has existed for basically the entire existence of the wide spread use of the Internet yet it was never deployed back then.

ObjC has always been a language that's interested me in the sense that it's very unique and it just seemed interesting. That being said I've never been involved in the apple ecosystem, not open enough for me so I got my mobile start on Android with Java...then realized I loved java, hated android development and never went back to mobile platform stuff LOL. I still haven't moved to kotlin and with modern Java as it is I don't currently plan to. Maybe I'll give it a try if I ever try android development again but for now I'm just a user on the mobile side.

Honestly it's not just steam unfortunately. It's also most games in general :/. Some games have working IPv6 support but the overwhelming majority don't. Even non-steam games don't work. Then you have games like terraria where the server fully supports IPv6(this is likely by accident) but the client has no support and so you can only connect to a v6 server using a proxy...games and anything around gaming (discord) is a pain point with IPv6 for sure. At least the only part of discord that breaks are the voice calls as you mentioned ://

Consumer routers, no, enterprise routers...yes

I did mention not trivial also DNS64 isn't that difficult comparatively. Especially since Google public DNS offers it. Setup the NAT, set your nameservers to 2001:4860:4860::6464 and you're good.

The only practical way to go IPv6 only right now is to use NAT64. This allows you to access IPv4 websites using your computers IPv6 address however it's not trivial to configure, you'll need a proper router(or Linux server), not just whatever router your ISP provides, and said router will still need an IPv4 WAN address but your PC, phone, etc can go IPv6 only and still access legacy sites like GitHub etc. For reference my home network is IPv6 only. I use jool for NAT64

The mention of iOS 16 having 66% of system binaries not using swift is very interesting. I'm actually curious as to the equivalent number on Android. How many system APKs currently don't use kotlin?

I get making fun of java's verbosity for things like checked exceptions but hello world really isn't that much worse than most other languages especially considering all the "boilerplate" is required for any program more complicated than hello world in pretty much every language. But if a useless program really is too verbose for you see java 21.

void main() {
  System.out.println("hello world");
}