Dark mode issues hahahahaha

Oh that’s sad. The nature of commerce and competition means that proprietary stuff will never go away because making closed stuff is the way MBAs are taught to create “competitive advantage”

What’s holding GNU/Hurd back? Can’t be hardware anymore since it became blazing fast

That was not the UNIX way… True UNIX way would end silently and have zero as $?

bon… désolé

Kotlin won’t save your skin if the code you wrote should be performant but you layered it into a heap of abstract classes, interfaces, factories, etc and, realistically, no one else would use or expand on that

Well, there is always root (for some phones). And consider that Apple crowd never had an option

Only once, tho

This is the scorched earth approach to error handling

This is the best answer… Or the outer classes being delegated access to the inner ones and so on, like an onion.

I wonder if this is one of the situations that Kotlin delegated parameters were designed to handle? (I’m new to Kotlin and still don’t understand that “by” construct there)

…and that, kids, is why java has this thing called imports

No, he is on a pointer to a pointer to a point tonight

In essence those are just a PC, switch, NAS, and UPS…

Technically correct is the best kind of correct