Yes.

The TWINSCAN EXE 5000 has a resolution of 8 nanometers.

https://www.asml.com/en/products/euv-lithography-systems/twinscan-exe-5000

The Google app is often used as a web browser by the tech-illiterate.

It even has tabs.

This is how my grandparents use it.

Ha, I see.

Yeah, sarcasm over text forums is sometimes difficult to pick up on.

You are wrong.

DRY has been applied to written code at least since the book Clean Code, which has been widely recommended to programmers for nearly two decades.

I’m not making a stance here about whether or not that is the right recommendation, but saying that DRY was never meant to be applied to “the code you write” is simply wrong.

(I remember DRY being pushed before that book, but it’s the only primary source I have at this moment.)

To be clear, the right of free speech given in the first amendment is the right to express any opinion without fear of repercussions.

There is no inherent right that your opinions must be given a platform, or that any particular platform has the right to exist.

The first amendment is entirely orthogonal to the question of whether or not TikTok should be allowed to operate in the US.

Maybe.

Linux won because it worked. Hurd was stuck in research and development hell. They never were able to catch up.

However, Linus’s kernel was more elaborate than GNU Hurd, so it was incorporated.

Quite the opposite.

GNU Hurd was a microkernel, using lots of cutting edge research, and necessitating a lot of additional complexity in userspace. This complexity also made it very difficult to get good performance.

Linux, on the other hand, was just a bog standard Unix monolithic kernel. Once they got a libc working on it, most existing Unix userspace, including the GNU userspace, was easy to port.

Linux won because it was simple, not elaborate.

After two years of development and some deliberation, AMD decided that there is no business case for running CUDA applications on AMD GPUs. One of the terms of my contract with AMD was that if AMD did not find it fit for further development, I could release it. Which brings us to today.

From https://github.com/vosen/ZLUDA?tab=readme-ov-file#faq

Yeah, if you’re not up to the challenge of maintaining your own system, Arch isn’t for you.

From an engineering perspective, I prefer Debian distros. Apt is the greatest package manager ever built. For a production server, I’d choose Debian or maybe Ubuntu if I needed to pay someone for support.

But for a desktop, Ubuntu kinda sucks. These days, I think I’d recommend Fedora to Linux noobs.

And for my toys at home, I run Arch btw.

Album art I see:

• Sgt Pepper’s Lonely Hearts Club Band (1967)
• The Velvet Underground and Nico (1967)
• Led Zeppelin (1969)
• Dark Side of the Moon (1973)
• Weezer (the blue album) (1994)

Other music art:

• The Nirvana logo (smiley face) is on the wall.
• The Rolling Stones logo is shown as an album art (IIRC it was never the cover of a studio album).
• Yellow Submarine (1968) is there, but it’s not the album art.

With pipes/sockets, each program has to coordinate the establishment of the connection with the other program. This is especially problematic if you want to have modular daemons, e.g. to support drop-in replacements with alternative implementations, or if you have multiple programs that you need to communicate with (each with a potentially different protocol).

To solve this problem, you want to standardize the connection establishment and message delivery, which is what dbus does.

With dbus, you just write your message to the bus. Dbus will handle delivering the message to the right program. It can even start the receiving daemon if it is not yet running.

It’s a bit similar to the role of an intermediate representation in compilers.

This doesn’t work for code bases written in non-English languages. Especially east asian languages.

Any line containing an identifier that is also a word would be highlighted.

More and more programming languages are supporting unicode identifiers for this use case.

Dunno. Haven’t had the chance to try the argument.

But like, I’ve literally never heard someone say “jay-pheg”.

Yes!

I’ve always been in the “jif” camp.

Now I have a new counter!

Nit: It’s “à la carte” meaning “by the card” or “according to the menu”. Often the accent is dropped in English writing, but it’s always written as three words.

This is just a stupid, meaningless nit-pick. I totally understood what you were saying, so it’s really not important. It’s just, the more you know, ya know?

XDG is a Red Hat thing.

Stuff outside of their influence is unlikely to change, like OpenSSH or ZSH.

The alternative to IPv6 is CGNAT.

CGNAT is really annoying for users, since the entire ISP looks like a single IP address. This can lead to situations where the entire ISP accidentally gets classified as a bot or otherwise blocked. It’s not too hard to find these kinds of stories from StarLink customers.

We are at the point where we are are legitimately out of IPv4 addresses. Household NAT isn’t enough and CGNAT has too many problems. IPv6 code was written ages ago and is very stable in all OSs these days.

It really is just these legacy middle boxes holding us back.