I used to tell people that John McAfee always exited a room by jumping through a window while yelling, “MCAFEE RULES!” Which he didn’t, but maybe he did? Anyway, I miss that crazy motherfucker. Sometimes nuts make the world more fun.
IPv6 = second system effect. It’s way too complicated for what was needed and this complexity hinders its adoption. We don’t need 100 ip addresses for every atom on the face of the earth and we never will.
They should have just added an octet to IPv4 and be done with it.
Every time there’s a “just add an extra octet” argument, I feel some people are completely clueless about how hardware works.
Most hardware comes with 32-bit or 64-bit registers. (Recall that IPv6 came out just a year before the Nintendo 64.) By adding only an extra octet, thus having 40 bits for addressing, you are wasting 24 bits of a 64-bit register. Or wasting 24 bits of a 32-bit register pair. Either way, this is inefficient.
And there’s also the fact that the modern internet is actually reaching the upper limits of a hypothetical 64-bit IPv5: lemmy.world/comment/10727792. Do we want to spend yet another two decades just to transition to a newer protocol?
You’re not “wasting” them if you just don’t need the extra bits, Are you wasting a 32-bit integer if your program only ever counts up to 1000000?
Even so when you do start to need them, you can gradually make the other bits available in the form of more octets. Like you can just define it as a.b.c.d.e = 0.a.b.c.d.e = 0.0.a.b.c.d.e = 0.0.0.a.b.c.d.e
Recall that IPv6 came out just a year before the Nintendo 64
If you’re worried about wasting registers it makes even less sense to switch from a 32-bit addressing space to a 128-bit one in one go.
Anyway, your explanation is a perfect example of “second system effect” at work. You get all caught up in the mistakes of the first system, in casu the lack of addressing bits, and then you go all out to correct those mistakes for your second system, giving it all the bits humanity could ever need before the heat death of the universe, while ignoring the real world implications of your choices. And now you are surprised that nobody wants to use your 128-bit abomination.
You’re not “wasting” them if you just don’t need the extra bits
We are talking about addresses, not counters. An inherently hierarchical one at that (i.e. it goes from top to bottom using up all bits). If you don’t use the bits you are actually wasting them.
you can gradually make the other bits available in the form of more octets
So why didn’t we make other bits available for IPv4 gradually? Yeah, same issue as that: Forwards compatibility. If you meant that this “IPv5” standard should specify compulsory 64-bit support from the very beginning, then why are you arbitrarily restricting the use of some bits in the first place?
If you’re worried about wasting registers it makes even less sense to switch from a 32-bit addressing space to a 128-bit one in one go
We are talking about addresses, not counters. An inherently hierarchical one at that. If you don’t use the bits you are actually wasting them.
Bullshit.
I have a 64-bit computer, it can address up to 18.4 exabytes, but my computer only has 32GB, so I will never use the vast majority that address space. Am I “wasting” it?
All the 128 bits are used in IPv6. ;)
Yes they are all “used” but you don’t need them. We are not using 2^128 ip addresses in the world. In your own terminology: you are using 4 registers for a 2 register problem. That is much more wasteful in terms of hardware than using 40 bits to represent an ip address and wasting 24 bits.
I have a 64-bit computer, it can address up to 18.4 exabytes, but my computer only has 32GB, so I will never use the vast majority that address space. Am I “wasting” it?
You are using the addressing bits in the form of virtual memory. Right now. Unless you run a unikernel system, then in that case you could be right, but I doubt it.
Anyway, this is apples and oranges. IP addresses are hierarchical by design (so you have subnets of subnets of subnets of …), memory addresses are flat for the most part, minus some x86 shenanigans.
Yes they are all “used” but you don’t need them. We are not using 2^128 ip addresses in the world.
But we do need them! The last 64 bits of your IPv6 addresses are randomized for privacy purposes, it’s either that or your MAC address is used for them. We may not be using those addresses simultaneously but they certainly are used.
Despite that, there still are plenty of empty spaces in IPv6, that’s true. But they will still be used in the future should the opportunity arise. Any “wastage” is artificial, not a built-in deficiency of the protocol. Whereas if we restricted the space to 40 bits, there will be 24 bits wasted forever no matter how.
That why we should adopt my ipv12. Its three levels of addresses rach 512 bit longs. One for host one for network and one what ever the heel else need. Planet that’s it we asogn each planet a 512 bit address
I see where you’re coming from, but no matter how many null pointer exceptions there are in Java code, you’re almost always protected from actually wrecking your system in an unrecoverable way; usually the program will just crash, and even provide a relatively helpful error message. The JVM is effectively a safety net, albeit an imperfect one. Whereas in C++, the closest thing you have to a safety net, i.e. something to guarantee that invalid memory usage crashes your program rather than corrupting its own or another process’s memory, is segfaults, which are merely a nicety provided by common hardware, not required by the language or provided by the compiler. Even then, with modern compiler implementations, undefined behavior can cause an effectively unlimited amount of “bad stuff” even on hardware that supports segfaults.
Additionally, most languages with managed runtimes that existed when Java was introduced didn’t actually have a static type system. In particular, Perl was very popular, and its type system is…uh…well, let’s just say it gives JavaScript some serious competition.
That said, despite this grain of truth in the statement, I think the perception that Java is comparatively robust is primarily due to Java’s intense marketing (particularly in its early years), which strongly pushed the idea that Java is an “enterprise” language, whatever that means.
We still use on-prem Exchange with Microsoft Office at work, and it’s really becoming a problem. Microsoft already auto adds shortcuts for 365 (which we don’t use and doesn’t work with our setup), and the “Mail” app (which also doesn’t work with out setup), and now I have to explain to people to use the regularly titled Outlook icon and not the “Outlook (new)” icon (which again, won’t work with our setup).
You’ve missed the point; group policies are being ignored and break with every other update as Microsofts cadence and quality assurance continues to enshitify.
Stop calling out my commit messages… I swear “fixed bug x (for real this time)(ok now it should be fixed) added feature y” is a valid commit message scheme.
Maybe; but Valve has plenty of patch notes that say “X fixed,” but it’s not actually fixed and then the next update says “X fixed. No really this time.” lol
I see this point a lot and I don’t get it at all. You can do something awesome, free and open-source but use tools that aren’t, especially when we’re talking about community building. Sure, you can do your outreach exclusively on Mastodon or Farcaster, but the most eyes just happen to be on closed platforms, so it’d just be self-sabotage. Doing the only thing that makes sense doesn’t make you a hypocrite.
But as you mention, NaN propagates.
So at checkout, your wallet will become NaN, as the shops money balance. Then it will spread to your bank account and before you realize what happens the whole banking-district is in flames.
I get quite a bit of flak from my colleagues for paying for search, but I kid you not, I don’t regret splurging on a Kagi subscription at all. It’s personally less stressful for me, having to wade through less cruft, and I think I even work significantly faster because of how I use it.
It’s sad when you think about it. Search was such a good experience in the past.
I also pay for Kagi and I’m super happy with that decision. I do wish they’d stop putting so much AI cruft into their search engine, but at least I can disable it.
With most topics, I find fastgpt to be the most up to date, accurate and best sourced. And with just a normal search there’s basically just one expandable strip with AI, no real annoyance for me.
This is why I jumped ship to DuckDuckGo like 4-5 years ago already, never looked back
Coincidentally, yesterday I was quickly setting up a new computer for some testing whilst talking to somebody about another so I was half distracted. I did a search for some package to install and got absolute unusable crap. I didn’t understand, tried again, tried different search parameters and it just got worse, and then I noticed that, since this was a new computer, the browser was using google.
I switched to DDG, and first page first hit was what I needed.
DDG also has been in a steady decline and apparently has been using Bing as it’s back-end now. I’d love to use a self hosted open source browser, or of not that, an open source federated search engine, akin to Lemmy, but I don’t see either coming into existence anytime soon.
bing itself is unusable tho. I get a full page of “sponsored links” before any tentatively relevant search result pop up. DDG at least removes the sponsored bullshit.
For what it’s worth, DDG isn’t perfect either. There are plenty of times I have to use Google instead. I don’t keep track of how often it anything but it’s definitely not perfect.
apparently has been using Bing as it’s back-end now.
A lot of stuff uses Bing to search, as it’s the largest search engine with an official public API that any developer can just sign up and use. Voice assistants like Alexa use Bing too.
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.