Last year my ISP forced v6 and disabled the option to set v4 only. I lost the Adgurd Home DNS configuration in all devices. But then learnt a few things and able to use internal ipv6 address for dns although still unable to configure ipv6 in Docker :/
In the USA they charge extra for IPv6? I'm in the UK and while there are some ISPs that don't provide IPv6 at all, and some that do shitty things like dynamic prefixes on IPv6, I've not seen anyone charging for it.
Likewise, server providers generally don't charge for it. In fact, they will often charge less if you don't need IPv4.
No don’t take shitposts literally. I’ve been using ipv6 for a decade at home now in the USA and I don’t pay extra for it ever. Also why are you assuming this post refers to the us?
There's been other posts about IPv6 and the TL;DR is that while there are shitty implementations everywhere, the USA seems to be ahead of the game of doing it badly, if at all.
The USA is ahead of most nations at about 50% so not sure how you’re coming to that conclusion based off of evidence. Outside of maybe Brazil in the americas on both continents our ipv6 adoption is better than the rest, Canada included.
I reckon I see most IPv6 complainers are from the US though…
In my country, turning on IPv6 is not really something ceremonial, it’s just literally clicking on the IPv6 checkbox. The default configurations set in the router are good enough for an average home user, firewalls and all that security jazz are enabled by default.
The DNS didn’t break just because I enabled IPv6, nor did my phone apps stop working. Life goes on, and I have gotten rid of that terrible CGNAT. Somehow this is not the case for many US users across multiple ISPs, I have heard IPv6 horror stories from Verizon, Comcast, and AT&T. Like how did you manage to do that?
I mean I’ve been using native dual stack for over a decade and I’m most definitely American. A fun anecdote was I was having issues with clicking on links from Google once and turned out ipv4 was busted but 6 worked fine for half a day. And there really isn’t any turning on ipv6 I get it by default and it’s with the most hated isp Comcast. They’re actually really good about v6 support I’ve not moved off them because of it. It’s literally 10ms faster than 4 lilely due to cgnat.
Is such a weird complaint. You should aim for your codebase to be as small, simple and readable as possible, while your tests should be a specification that guarantees behavior is consistent between refactors. When you add behavior, you add tests, when you remove a behavior, you delete tests.
The size of either is independent of eachother. Small code bases that provide lots of features should be simple to read, but with a lot of tests.
I keep asking myself what to choose, only for changing it a day after cursing myself to choose a stupid name.
Big endiant is great for intellisense to quickly browse possibilities, since it groups it all in the same place. But that’s also a detriment when you know what you want. You can start typing without the prefix but you’ll have to go through the better suggestions of intellisense first.
Little endiant is the same thing, but in reverse. Great when needed, but bad for browsing.
Although I do have some fix I’m starting to use. But it’s not applicable everywhere, and not in every language.
What I do is use module as prefix. Instead of dialogue_file_open, I create a file_open in the dialogue module, allowing either directly calling file_open, or dialogue::file_open. Using intellisense on the module allow for easy browsing too!
Although in OP’s post I’d rather have file_open_dialogue as it convey the more significant meaning, being to open a file, first. Then “dialogue” is just the flavour on top
Big endiant is great for intellisense to quickly browse possibilities, since it groups it all in the same place.
If only someone would train a program… we could call it a Large Language Model… to knowingly group the names together so we wouldn’t have to choose between human-readable format or dB format.
Guess that will never happen because instead we’re stuck using “AI’s” to inflate stock prices instead. /s
I remember seeing a proposed language that would allow each programmer to choose what name to use for each item. Don’t like ‘open_file’? Choose to see it as ‘file_open’ every time you review the file in the future.
While we battle with each other endlessly, we keep forgetting that the computer doesn’t care.
It’s fascinating how s-expressions are both data type and language syntax. Such power. Only other time I saw something remotely like this was XSLT & XML, which I admittedly do not miss one bit.
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.