uecker

I think Rust has similar flaws as C++: too much unneeded complexity and abysmal compilation times.

Anyway, I do not see how this affects the design of C in a way that makes no sense anymore today (except that one could require CHAR_BIT to be eight, but there are still DSPs where this is not the cas…

The "stronger type system" is mostly a myth in my opinion. It was true in the past in pre-prototype C. The void pointer rules are better in C IMHO as they avoid unneeded casts (that then rem…

You can just run it through a compiler in c++ language mode.

There is not much real evidence for "devs wrongly assume" and as someone writing numerical code (clusters, NUMA, SIMD, etc.) I think C is still the ideal tool for this.

The "nor is the hardware a PDP 11". Byte access was the main new feature of the PDP 11 that C adopted. Are you saying being able to access individual bytes is not relevant on modern hardware…

In practice, the [static n] notation can give you useful warnings and bounds checking. https://godbolt.org/z/PzcjW4zKK And while the (*array_ptr)[3] notation take a moment to get…

Yes, but this GCC behavior is not conformant to ISO C.

Yes, I do not believe for a second that wayland is a net benefit for the majority. Every improvement one can have in Wayland could have been implemented in X without breaking compatibility, without ca…

The quiz is not entirely accurate though. For example, pointers to the same address must compare equal. Other stuff is ancient and some of it was already removed in C23. Again other things are entirel…

Not my experience and we have lot of Linux machines. Drivers and hardware expectations of programs certainly change over time, but this has not much to do with Wayland vs X.

Sure, they know best of course ;-) This is the arrogance and gas lightning we are talking about. But I am not complaining about KDE, they can do whatever they feel best for their projec.t I do not us…

This sounds more like random configuration problems with your drivers. The rendering model for modern X clients is the same as for Wayland, so the idea that there could be room for a fundamental impro…

Well, I can only report from my experience and this is the pain I still see with Wayland but not really with X. If KDE wants to hurt some of their users, this is their decision.

It might matter to some but not to many, and in practice the pain imposed on many others could have been avoided by simply improving X. That developers already like to rewrite things is well known, b…

Is is a regular occurrence that students in my lab that use or switch to Wayland still run into problems. Switching back to X11 reliably works as a fix. The sad thing is that there is also no apparent…

yes, exactly this.

It looks better to me than the other macro solution as it is more transparent what is done compared to DEFINE_ENUM. But I agree it is not as succinct as C++'s reflection syntax.

In practice it is written like like this: #define MY_ENUM(x) x(MY_A) x(MY_B) x(MY_C) enum my_enum { MY_ENUM(ENUM_ENTRIES) }; static const char *my_enum_names[] = { MY_ENUM(ENUM_NAMES) }; b…

In practice, I see people write very performance C code where it matters, while moving on quickly where it does not. C++ code is often highly templated with annoying compile times, but still often slo…

C is not slow compared to C++. C++ compilation time are slow though.

Are X macros awkward? I find them very straightforward and clear.

This does not make your comment above less wrong.

Nowadays you would work in git and then you would be able to easily detect any discrepancy between the upstream tar ball and the upstream source imported via git. But yes, better support for securing…

Typo-squatting attacks are more of an issue for non-curated software collections, not so much for Debian. If you use npm or cargo or similar, then you have indeed far bigger worries. Compromising the …

If your compiler (or other tool or automatic build environment) is compromised and inserts a backdoor in the binary during building, the fact that you need to hold a key while signing or not is comple…

A hardware key does not help if the developer's machine is compromised, as there is no change to understand what is signed anymore, or do you think the hardware key will show all the source code …

An attack would be far easier without reproducible packages. One could upload a compromised binary to debian by becoming a debian developer, blackmail a debian developer to so, or compromise the compu…

This is a huge achievement for Debian and the free software world. It took a while though until this was understood. In 2007 when pointing out on debian-devel that this is needed, I was still told wha…

Well, I would say google "might" be counting differently or have huge bias.