Viewing profile — uecker

Easy and still expressive, so you can map many things to C. And while the language standard does not define an ABI it takes a lot of care not to require any ABI break.

You can do more with less energy, if you use it more efficiently, which sometimes may be more cost effective compared to producing more. Electricity consumption peaked in Germany i…

Your understanding of this is poor. First, the same is true with neighbors putting renewables on the grid, it is not just Germany having renewables anymore. But the issue is not th…

I certainly also remember the kernel crashing, but this was in the 90s. Later perhaps once or twice on faulty hardware. Shell, I don't think I have seen this ever.

How does "emergency-dumping" create cost to neighbors? But what you miss is that most of the EU now has a lot of renewables.

This seems too low by an order of magnitude. In 2021, nuclear power produced 69 TWh in Germany. For comparison, renewables produced 240 TWh in 2021 and 292 TWh in 2025. But I agree…

Germany invested in renewables already at a time when they were very expensive. This created an economy of scale that brought prices down to everybody. Nuclear was never economical…

People who did this found renewables to be cost effective.

The difference is that Germany's investments in renewables at a time when they were still expensive helped to create an economy of scale, which brought down prices for everyone and…

Russia did not completely cut gas exports to Europa, but reduced in substantially, but this was a reaction to sanctions and the decision in Europa to reduce imports from Russia (bu…

But it did exactly this. The pipeline was not the only way to import Russian gas.

Can you explain what you mean exactly regarding this augmenting this syntax?

That was discussed, but consistency with sizeof was considered more important. And if you figured out how to parse sizeof, parsing countof is not an additional burden.

Sorry, that others are equally bad is not an excuse, and also not that Rust's design makes it more difficult to package. Either you care about security or you don't.

Basically all C programs I use, shells, editors, terminals, etc. But I do not claim that there "never has been a memory-related bug" but that it is not "riddled with" memory-relate…

It had no crash during 30 years, not after 30 years.

Those style guides would also disallow having multiple declarators in a single declaration.

I would say a modern style of C using proper abstractions and modern tooling is less prone to memory safety issues than C written in the style of C89.

If I would add another array, it would look like: int c_style_array[2][5][3]; There is also no jumping back and forth. C declarations are also recursively constructed. One can comp…

Somehow, magically, some people managed to write C software that I now use for three decade with not a single crash in all this time.

The C programs I use daily are generally very fast, very lean and very stable: Programs such as linux, terminals, shells, vim, etc.

I assume he means multi-dimensional arrays: std::array , 5> array_of_ints; int c_style_array[5][3]; But the C-style array is more readable, so I am not sure what the complaint real…

I think we agree on this. Fil-C does not ensure this. Showing the absence of run-time errors at compile-time is a hard problem, and the most realistic solution in general is via mo…

It certainly works in my C programs. And Fil-C demos imply that this also works for a lot of other complex real world programs, i.e. a basic Linux distribution with libreoffice on …

Of course, I just wished enough Rust enthusiast cared also about other real-word security issues enough to get this fixed: https://rustup.rs/