• 0 Posts
  • 57 Comments
Joined 1 year ago
cake
Cake day: June 29th, 2023

help-circle

  • 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/













  • Yeah I agree, they are but I guess what I’m trying to get at is in day to day conversation I use “programming language” as a term for compiled languages hence “real” and “scripting language” for scripting languages. I never say “real” in conversation, just in the context of this post and as I mentioned it’s not to say scripting languages aren’t good languages, just how I separate them. Your distinction is much better in more comparative dialog such as this


  • I’m aware of the increasing prevalence of JIT, that doesn’t change the other markers I listed. Ironically though the language the post is about, CPython still lacks JIT. Also I disagree in general, there are things scripting languages can’t do and will never be practical for. It’s not that they aren’t useful programming languages, that’s not what I’m saying but I think having a separate category for them is useful.


  • I personally draw a distinction between “real” programming languages and scripting languages. Scripting languages being languages that are traditionally source distributed. They tend to be much easier to write, run slower, often but not always dynamically typed, and operate at a higher level than “real” programming languages. That’s not to say they aren’t actually useful or difficult to learn etc. It’s not a demeaning separation, just a useful categorization IMO. Not to say the categorization always holds water in all those attributes, luajit is way faster than Java but it does follow the other bits. As someone who loves C there are lots of languages that seem too limiting and high level, doesn’t mean they aren’t useful tho.


  • Yes, honestly this situation reminds me a lot of the LTT trying Linux and destroying his system by installing steam despite apt warning him in the best way it really could that he probably didn’t want to do that. Sure the package shouldn’t have been in that state in a stable distro but shit happens. It goes to that point of, users will go through great lengths to achieve the end goal blindly jumping past warnings on the way no matter how dire they might be.