andix

I guess it's eternally stuck in the 90s. I didn't see Perl in a long time now. 10-15 years ago it was still everywhere.

edit: No, it's stuck in the 80s: "The data comes from a 5% sampling of Social Security card applications with dates of birth from January 1980 through December 1989"

https://metacpan.org/pod/Text::GenderFromName#REGARDING-THE-...

It's kind of surprising that this is even allowed. A lot of countries require at least the first given name to match the gender. Some names might be deemed suitable for both genders.

It doesn't look good on a 4K display, without some smoothing or upsclaing. It looks fine on a native 1080p screen though.

Are you sure those displays have everything needed for a smooth TV experience? Do they have eARC to connect a sound bar, and stuff like that? Modern TVs are also quite good at upscaling 1080/720p content, screens often aren't.

(I don't care about integrated speakers though)

Okay, just because aviation is now also developing in the wrong direction (maybe), all the things they did right in the past are suddenly pointless? I suggest to learn from the things they did right, not the things they did wrong.

Isn't that the same thing as "not making mistakes"? If you can reduce the blast radius and didn't, wasn't that a major mistake in the first place?

You're right, there is no mandate for learning and doing better in SW engineering. Many companies just don't care, also kind of fine. This doesn't mean that everyone doesn't care and nobody wants to improve.

Aviation is working with the same constraints. Development of new systems is very slow, that's true. But day-to-day operation is extremely fast paced, and still impressively safe. They are able to change an engine of an aircraft within hours, with a very high probability of not making any relevant mistakes in the process.

It's more about managing mistakes. Pilots and other people in aviation still make a lot of mistakes all the time. But aviation figured out how to deal with that fact. Design procedures in a way, that mistakes self-correct most of the time. Add sanity checks exactly where they matter, and many other strategies.

Not losing production data and not getting breached is also something we try to make zero mistakes at.

It is a good industry to learn from. I'm not suggesting SW should become exactly like aviation.

> "Just as the FAA mandates manual flying time even when the autopilot is perfectly capable, SRE teams can designate certain incidents, even the ones the AI could handle, as human-practice opportunities"

This is a great example. Aviation is a perfect industry to learn from, they figured out a lot of things about how to keep humans from making mistakes. While complexity increases and automation takes away more and more tasks.

Those devices run in a private network and usually don't have any internet connectivity at all. If they do access the internet, it's usually limited to a few hosts that can easily be routed over some compatibility layer or a proxy.

The problem is real. In IP discovery GUA is prioritized over ULA. And if the GUA goes away or changes regularly it leads to connectivity issues.

ULA work well in combination with DNS though.

There is some truth to it, because they only work well if used directly (either hard coded IPs or DNS).

This problem seems to be addressed already and might be solved in the future: https://datatracker.ietf.org/doc/draft-ietf-6man-rfc6724-upd...

(once again it's surprising how long it takes to clear up all IPv6 quirks)

It only failed to fully replace IPv4. But it runs perfectly fine along IPv4 and is very much alive. It replaced IPv4 where it was needed and didn't where it doesn't matter yet.

Email didn't replace letters on paper. But I wouldn't say email failed completely.

I know. The full product's name seems to be "Claude Duet", which would make everything much clearer and easier to google it.

I could deduct some of that from this sentence, sure.

But I wrote this comment because the article was frustrating for me to read. One single sentence would've made it much less confusing:

  Look, I really didn’t want to like **Claude** Duet, **Anthropic's new personal AI assistant**. I don’t want to be an Anthropic fanboy and ...

I'm also known to flag this kind of shortcoming in all technical documentation I review, and it annoys a lot of people that I do. I've put my judgement to the test already a few times in team meetings when someone objected this specific remark. Many times I could prove that there are always a few people in the room that would've benefited a lot from such a simple clarification. They just didn't speak up or ask, because they thought they were the only ones that didn't know a specific term.

My intention is also not to be rude, just creating some awareness for this issue.

> For context: I deployed IPv6 in my networks in 2006. I have war stories.

Early IPv6 was a mess. It took a surprising amount of time for IPv6 to become mature and usable.

> Use ULAs

Isn't that the default for modern routers? They just generate a random ULA during setup and assign it.

Random ULAs are also great for LAN-to-LAN VPNs, because there aren't any private IP overlaps. Everyone setting up their LAN on 192.168.0.x makes it quite a mess on IPv4.

I get your frustration. But not having access to IPv6 personally does not mean IPv6 is dead. It's very much alive and handles considerable amounts of traffic.

Note to everyone writing blog posts: Please start your post with one or two sentences explaining what you're posting about.

What is Duet? I have no idea even after skimming the article.

Edit: first google result is https://www.duetdisplay.com

I don't get your point. IPv6 is at "boring, just works". The majority of the worlds devices run on it dual-stack and it handles a considerable amount of traffic. A lot of 5G networks run on IPv6 single stack with IPv4 compatibility on top.

IPv6 is very much alive. And it's so boring and working so well, that you don't even notice it.

I guess a lot of sites just turn it off. Even if Cloudflare proxies it over IPv4 the IPv6 source address still shows up in server logs. Features like geolocating users or fraud prevention might need additional work for IPv6.

Okay, if you say so. Hotel Wifis are known for being on the bleeding edge of technology, and as the main innovator pushing new internet technology. Everything starts with hotel Wifis. /s

So they can use GLM from a trusted provider, that is highly committed to respect local laws and regulations.

Just think about a defense contractor. Choosing trustworthy vendors is crucial to them. They can't just use a random provider from Open Router. They need to vet and certify their vendors. If they already have Mistral on the list of approved vendors, they can now just switch to the most recent open weight LLM if Mistral starts serving it.

Looks like the consensus is much more leaning into the direction of non copyrightable.

Open weight and open source are different things. It's important not to mix that up.

Sure, but even if a provider peers through Amsterdam it doesn't mean their IPs must be geolocated and registered there. It's probably because of favorable legislation.

Also some car entertainment systems with integrated 4G/5G use Dutch IPs. Which leads to the weird situation that I sometimes get dutch radio ads on TuneIn or some websites redirect to the Dutch version.

Cloud providers and hosters seem to have the least interest in implementing IPv6. Sitting on a huge supply of IPv4 addresses gives them a competitive advantage. So they try to disable IPv6 as a default.