I mean, he was still reading Slashdot, so I guess "yes"
SpaceCadet
joined 1 year ago
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.
you are wasting 24 bits of a 64-bit register
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.
Hmm, I can't say that I've ever noticed this. I have a 3950x 16-core CPU and I often do video re-encoding with ffmpeg on all cores, and occasionally compile software on all cores too. I don't notice it in the GUI's responsiveness at all.
Are you absolutely sure it's not I/O related? A compile is usually doing a lot of random IO as well. What kind of drive are you running this on? Is it the same drive as your home directory is on?
Way back when I still had a much weaker 4-core CPU I had issues with window and mouse lagging when running certain heavy jobs as well, and it turned out that using ionice helped me a lot more than using nice.
I also remember that fairly recently there was a KDE/plasma stutter bug due to it reading from ~/.cache constantly. Brodie Robertson talked about it: https://www.youtube.com/watch?v=sCoioLCT5_o
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 earth's surface and we never will.
They should have just added an octet to IPv4 and be done with it.
you just need to get in the habit of plugging in like you would your phone
Yeah but not everyone lives in suburbia with ample plug-in options available to them. Where I live the street-side charging spots are usually occupied, and the parking spot that I rent has no charging.
For journey’s long enough for it to be more than a single charge you really should be stopping for more than a few seconds anyway as you need recharging.
True to some extent, I have to check my travel logs but I do feel like stopping for an hour every 300km or so is longer and much more often than I would normally stop on long road trips. My (diesel) car has a range of well over 1000km so often I stop for only 15 minutes for a coffee and to stretch my legs, or just for a restroom stop and a driver swap. We usually plan just one big stop (1h) for dinner. Most destinations I've been to I could reach without refueling at all.
There's also the issue of contention for charging spots. On gas stations near the big highways towards popular destinations you often already have to queue to get gas. This will become worse when EVs become common place and people occupy a charging spot for an hour instead of a fuel pump for 30 seconds to top up.
Little anecdote: every year around the holiday season, there are several company wide e-mails from EV driving co-workers requesting to swap cars (with a co-worker who has a CE car) to go on holiday. So I think the practical experience may not be as rosy as you paint it.
At 17:00 everyone’s got a beer on their desk and by 18:00 the doors are locked and the lights are out. One Thursday a month the table is used for beer pong after work and we play card games like Exploding Kittens.
I'd rather go home at 17:00 and do all those things with my real friends, or you know, spend some quality time with my partner.
I read that as librarians and was very confused.
So this is a huge pet peeve of mine: Flemish is not a separate language. It refers to a region inside of Belgium where Dutch is the official language. The Dutch and the Flemish share the same standard language.
I know dialects exist, and those can be considered a language on their own, but there is no unified Flemish dialect. West-Flemish for example is distinctly different from other dialects spoken in Flanders like Brabandic or Limburgish, and variants of Limburgish and Brabandic dialects are spoken in large areas of the Netherlands as well. So it doesn't make sense to create a distinction between "Dutch" and "Flemish".
The differences are on the level of American English vs. Australian English vs. British English. Or Austrian German vs. Swiss German vs. Bavarian German vs. North German ... So if those are not singled out, it doesn't make sense to separate Flemish from Dutch.
put Germans back to work
Well they weren't wrong ... :-/
You don't even have to NAT the fuck out of your network. NAT is usually only needed in one place: where your internal network meets the outside world, and it provides a clean separation between the two as well, which I like.
For most internal networks there really are no advantages to moving to IPv6 other than bragging rights.
The more I think about it, the more I find IPv6 a huge overly complicated mistake. For the issue they wanted to solve, worldwide public IP shortage, they could have just added an octet to IPv4 to multiply the number of available addresses with 256 and called it a day. Not every square cm of the planet needs a public IP.
Exactly. That would be like using a web browser made by Google so they have direct access to your internet browsing history. Ridiculous!