Scoopta

Does the UX suck? Genuine question. Debian is where I moved after I outgrew mint and I’ve never had a problem with it or felt like it was cludgy

A lot of companies run Debian and Debian based distros, Google on their servers for a start

If you’re using systemd they just recently introduced run0 which works very similarly to what’s talked about here

Should probably fix that given we’ve been out of IPv4 for over a decade now and v6 is only becoming more widely deployed

🤔 that’s a fair point…

It’s actually not. Objective-C is a superset of C. C++ is not. It’s MOSTLY compatible…but it’s not a superset. See the restrict keyword, or the need for casting to and from void*, or the inability to name variables new or delete, or class, or this. I can’t count how many C projects I have which use this as a variable name that WILL NOT compile as C++…or the need for extern C to call C ABI code…in no way is it a superset

EDIT: lol, you can downvote me if you want but I think you need to lookup what a superset is

There was actually a really interesting idea I heard to have no time zones. And I actually think it could be a good idea. It’ll never happen because people would need to re-learn time but if it was always the same time everywhere it would make scheduling and business so much easier. No one would need to convert between different zones or be late because of an incorrect conversion. The downside is that times which are conventionally morning or evening etc, would no longer would be so people would have to get used to time just being a construct for scheduling and not a representation of the natural day/night cycle…but it actually doesn’t sound like a half bad idea.

From a development perspective it certainly sounds easier to have one global timezone with DST than a bunch of smaller ones without it. Would that make sense in reality? Probably not but I definitely think timezones take more work to compensate for properly.

In amd64/x86 kernel space you can dereference null as well. My hobby kernel keeps critical kernel structures there XD.

const volatile is used a lot when doing HW programming. Const will prevent your code from editing it and volatile prevents the compiler from making assumptions. For example reading from a read only MMIO region. Hardware might change the value hence volatile but you can’t because it’s read only so marking it as const allows the compiler to catch it instead of allowing you to try and fail.