>> However, the tech exists for a reason and is not inherently bad, the issue is the lock-in, the lack of choice and interoperability.

The marketing excuse for the tech might be features or efficiency, but the reason for the tech is lock-in and minimising product lifetime.

The days when manufacturers had friendly, cooperative relationships with their customers are long gone :( Can we bring them back? I hope so, but am not hopeful.

>> It has barely hit 50% and it's already plateauing.

Well, the curve has got to level-out at 100%.

No, it can level out below that and is (as the parent was saying).

How far below is the question. It could level out at 60% - that is believable. However it can't level out at 99% - Somewhere around 95% major sites will decide IPv4 isn't worth supporting and they will just ignore that final 5% of customers, which will force them to upgrade - which in turn will give others confidence to remove their final 4% of customers - until IPv4 dies.

There are still ascii dialup bulletin boards out there. and operating model T’s. IPv4 will be around for longer than you or I.

There are also still Telex and X.25 networks around there, not to forget the whole public telephone network!

But at some point, getting a native connection to all of these started becoming increasingly rare, and now these are largely emulated/tunneled on top of IP. The same can happen for IPv4.

> IPv4 will be around for longer than you or I.

That's a matter for the legacy network on the other side of the internet to handle, as it converts my IPv6 packets to IPv4.

That’s indeed what they’re saying, but they’re simply wrong which is obvious from looking at the graph and accounting for seasonal variation.

From Corsair

>> DDR5 technology comes with an exclusive data-checking feature that serves to improve memory cell reliability and increase memory yield for memory manufacturers. This inclusion doesn't make it full ECC memory though.

"Proper" ECC has a wider memory buss, so the CPU emits checksum bits that are saved alongside every word of memory, and checked again by the CPU when memory is read. Eg. a 64 bit machine would actually have 72 bit memory.

DDR5 "ECC" uses error correction only within the memory stick. It's there to reduce the error rate, so otherwise unacceptable memory is usable - individual cells have become so small that they are not longer acceptably reliable by themselves!

As I understand it, the 50-move rule must be invoked by one of the players, lets assume our immortal players agree not to invoke that rule.

The 75-move rule is automatic, so that would be the limiting factor.

Note, that 75-move rule is only applicable after no pawn has moved or a piece has been captured. So our immortals can do a lot of shuffling things around.

I'm thinking that the number of moves of the longest game is going to be (16 pawns * 7 moves each + 16 pawns being captured + 14 other pieces each being captured, not the kings) * 75 moves for shuffling around = 10650 moves.

That's only 1 week at 1 move per minute! But given the permutations, it might take much longer to calculate the actual moves required to get to the end state :)

Here's an actual constructed game that is presumably as long as possible (with explanation): https://www.reddit.com/r/chess/comments/168qmk6/longest_poss...

Pawns only get 6 moves :) But also they can't all make 6 moves because they can only move past each-other via capture, so half of them would get 5 moves instead (if you're counting all the captures), so that gives a maximum of ~8850.

And I though the arbitrary, non-mnemonic, unrelated-to-anything project/app names had got too much ... obviously we're way past that :(

Author here. I know not everybody loves the name. If I was trying to sell it I might be concerned about that. But it's open-source, and I'm not trying to make any money off of it, just trying to give something back to the community.

I was originally trying to name it something serious-sounding and I quickly found out that pretty much everything decent is taken. And even if you can come up with a good name that's not already in use by three other projects, good luck getting a decent domain for it.

I'm also a musician, and I've been through the drama of trying to come up with band names many times in the past. Here's what I've learned: the name matters, but only so much. If people like a band, they're gonna listen no matter how dumb the name is. Do you think Metallica is actually a good name? How about Def Leppard? Lynyrd Skynyrd? The Beatles? Those names are kinda stupid and nobody cares, lol.

Same thing with software. If the product is good, people will use it, and they are not going to care much about the name. I think Luxury Yacht is better than some made-up word that doesn't mean anything but maybe has some vague connection with kubernetes if you squint at it just right, like a magic eye puzzle.

Just my opinion, though. I'm not wrong, and you're not wrong, we just think about things differently, and that's OK!

Personally, I would like the name to be somehow related to the system. When I'm facing a stack of names and icons, make it easy for me.

Names without some connection to the thing are just more difficult. Maybe the name isn't descriptive - you can only have some many versions of ed, edit, edt, vedit, gedit, zed... I'm perfectly happy with puns and jokes - eric can be connected to (monty) python. It's the connection that makes it memorable. Even yacc and grep have some connection to the program.

I've been using Vivaldi browser for a while now, but neither the name nor icon have formed a natural connection to browsing for me. Same with Lazarus (an IDE), no obvious link (worse, it's nothing to do with raised from the dead). But "Bluefish Editor" at least tells me what it does, not a full description, but plenty.

To me, it looks like the whole article was generated by AI. Using slop to promote slop ;(

How about requiring all APIs to be open? Companies are free to run/maintain/drop servers and apps, but we'd have the ability to use the hardware we bought, if we write our own apps.

That might actually be good for security. If APIs must be public, proper cloud security becomes necessary (rather than relying on obscurity).

There are several versions of the Cray 1 Hardware Reference manual online. They're not as descriptive as Design of a Computer, but still informative.

thank you! that is very informative.

Oh great - yet another way to get AI slop. Slop text, a slop cover - just raw slop, straight from the slopperizor. And the internet gets another little bit deader.

> software is easier than hardware

Software is certainly easier to replicate that hardware, 1M copies cost almost exactly the same as 1 copy :)