Not to mention these modern showers that have a slab of glass on the 1st 3rd but then open door for the rest such that water leaks all over the place. Looks great on insta but sucks at being a shower.
I think it might be as simple as ipv4 is just nicer to look at…maybe we should have just done “ipv5” and added another block. Eg 1.1.1.1.1. I know its stupid, but ipv6 addresses are just so hard to remember and look at that I think its just human nature to gravitate towards the simplicity of ipv4.
The problem with "add another block" is, that you have to change everything everywhere to make it work... and if you're changing everything, why not expand it properly.
Only a tiny minority of people have to look at those addresses, the majority just types "facebook", enter, clicks on first google result and gets facebook (because ".com" is too hard to write).
Who remembers IPv4 addresses? If you have more than a small handful of devices in your network you're probably going to want some kind of name service.
dead::beef is just as memorable as 1.1.1.1, and my v6 delegated prefix is just as unmemorable as my public v4. The "easier to remember" argument just sucks hard.
I don't think many people are memorising a bunch of wildly different IPv4 addresses either.
At best, I remember the prefix of my private network, and a handful of single-number suffixes of important hosts (i.e. my LAN is 192.168.1.x, and I remember that .100 is my local file server...)
> I know its stupid, but ipv6 addresses are just so hard to remember and look at that I think its just human nature to gravitate towards the simplicity of ipv4.
If only there was a system that allowed for easy to remember human labels to be translated to a machine-usable sequence of bits that we call "an address"…
Eh. Judging by the large negative response I think the point might still have a point. Can you quickly rattle out ipv6 cidr blocks when you are setting up network configs? Most can grok and crank on ipv4 no problem. But for ipv6…its to the calculator. Not saying its a valid reason. Just saying ppl are lazy sooo if you want something adopted you might have to lean into lazy.
I have difficulty remembering ten numbers, why do I have to say 1-212-487-1965 when I can just say Santa Rosita 71965? Maybe we should have just done another exchange name and added another name. Eg Hawthorne Santa Rosita 71965. I know its stupid, but 10 digit phone numbers are just so hard to remember and look at that I think its just human nature to gravitate towards the simplicity of telephone exchange prefixes.
Yet again, another fundamental misunderstanding (either genuine or not, I'm not sure) about the low-level technologies and their origins that underpin all of this. "Can't we just..."? No.
1) you hit the cap
2) aws sends alert but your stuff still runs at no cost to you for 24h
3) if no response. Aws shuts it down forcefully.
4) aws eats the “cost” because lets face it. It basically cost them 1000th of what they bill you for.
5) you get this buffer 3 times a year. After that. They still do the 24h forced shutdown but you get billed.
Everybody wins.
The real take away is that so much functionality depends on a few players. This is a fundamental flaw in design that is getting worse by the year as the winner takes all winners win. Not saying they didn’t earn their wins. But the fact remains. The system is not robust. Then again, so what. It went down for a while. Maybe we shouldn’t depend on the internet being “up” all the time.
They also could forget about it. I bet I've probably seen Oxy in some cloudflare post from years ago (maybe even from a launch week or something) but it never resonated.
But I might have encountered this problem or am about to, and such a post might resonate more.
It is like advertising in a way. But for knowledge. As long as people upvote it, it's resonating.
Isn't this the point of upvoting though - if people find it interesting and new, they will upvote and stuff will be visible.
I also think HN does some sort of deduplication if something has been posted recently (to count as upvote instead of new submission), but not sure of the details.
It's also the point of commenting. I think they were hoping for a more specific explanation along the lines of "I'm interested in it because it has X, Y, Z implications" or "Oxy continues to be important because ____ and here's the best comprehensive intro to it."
I think it would be nice to have a Hacker Canon of stuff that's no longer news but still worth reading. Maybe the HN front page could have a few threads looking back 1/5/10/20 years where people could re-discuss things in a historical context.
In my experience people ~25 years of age and younger, who are not tech-savvy enough to install an adblocker, simply do not surf the web. Everything is an app, thus the internet browser becomes an online shopping (no/very few ads) and "googling" tool, though this second use is fading away as well with the rise of LLM chatbots. The ads baked into short-format content are much less obtrusive than the popups or fake download buttons of yore—though in my view this makes them even more insidious. I've witnessed my friends not even realize a video was an advertisement until they'd already watched it in full.
* Grain of salt; just the anecdotal opinion of a jaded zillenial.
Agreed. Its only going to get worse and all current trends validate that. It’s clearly trending towards closed source big brother platforms. E.g ios, android, windows and macos.
It does look that way. Though there is one potential silver lining around the madness going on in geopolitics: much of the rest of the world is rethinking it's long-standing strategy of relying on American software. That makes Open solutions look a lot more attractive, even to the average politician, than say a year ago.
reply