uecker

17 ms·

391.
by uecker 6mo ago
I agree, but are you responding to me?
392.
by uecker 6mo ago
Renaming c. to .cpp may work with ancient c89 code, but not with anything remotely modern. But while the code then is technically C++, it is not better. I still prefer C for new projects to any other language, because I value short compil
393.
by uecker 6mo ago
This is a misrepresentation based on a misunderstanding on how standardization works. The C standard committee has long recognized the need for better safety and carefully made it possible so that C could be implemented safely. But the pro
394.
by uecker 6mo ago
I mostly just install a -dev package on Linux and I am done.
395.
by uecker 6mo ago
Well, there is Annex K which is based on a previous Microsoft effort. Almost universally it is considered terrible and few people implemented it.
396.
by uecker 6mo ago
Thanks! Two notes: GCC has its "access" attributes which can give you similar bounds safety as clang. Please see also my experimental library. https://codeberg.org/uecker/noplate/ While I do not had en
397.
by uecker 6mo ago
I find it extremely useful and it works well for many use cases. This already implies that "it is useless" is pure nonsense. If it does not work for your usecase, just don't use it.
398.
by uecker 6mo ago
I am not sure why this means why "NFS is really stupid" if the user assumes that a distributed file system can be treated just like a local system. That is provides the same interface is what makes NFS extremely useful.
399.
by uecker 6mo ago
I don't think the problem is nearly as big as people claim. Experts are often right! While there are counter examples and inefficiencies in the system (and there are idea of addressing this, by distributing some part of the money in ot
400.
by uecker 6mo ago
This is exaggerating and generalizing too much. Science still works extremely well in general.
401.
by uecker 6mo ago
I do not see what this has to do with Unix. The problem is not that programs interoperate or handle text streams, the problem is a) the supply chain issues in modern web-software (and thanks to Rust now system-level) development and b) tha
402.
by uecker 6mo ago
"endless list of CVE" seems rather exaggerated for coreutils. There are only very few CVEs in the last decade and most seem rather harmless.
403.
by uecker 6mo ago
These are not the "same risks" at all.
404.
by uecker 6mo ago
I would say the least thing the scientific community needs is the packaging mess of Python introduced also on the lower level via Rust.
405.
by uecker 6mo ago
According to my experience, all the "zero-cost abstractions" from C++ most of the time make it more annoying to maintain and/or understand the code, especially with respect to resource management, introduce compatibility issu
406.
by uecker 6mo ago
Indeed, and this is why people who care about this are also proving memory safety in C. The issue is that we do not have good open-source tooling that specifically focuses on formal verification of memory safety in C.
407.
by uecker 6mo ago
Fair enough, but I have seen how it works and for just temporal memory safety, it could be simple.
408.
by uecker 6mo ago
Depending on what you are doing, yes. But the statement I responded to "your only choice is crash" is certainly wrong.
409.
by uecker 6mo ago
For temporal memory safety.
410.
by uecker 6mo ago
Even without Fil-C I do not think it is even clear that new software should be written in Rust. It seems to have a lot of fans, but IMHO it is overrated. If you need perfect memory safety Rust has an advantage at the moment, but if you are
411.
by uecker 6mo ago
What makes you think that one can not add an explicit bound check in C?
412.
by uecker 6mo ago
I do not know how Fil-C handles this, but it could raise a signal that one can then catch.
413.
by uecker 7mo ago
The problem is not that society is too complexity but extremely unequal distribution of money. Those few that have most of it usually did not earn it by providing a useful service to society and for them it becomes a random investment ga
414.
by uecker 7mo ago
XML is already terrible. But the main problem seems to be that they created something similar but incompatible to make.
415.
by uecker 7mo ago
There is something fundamentally wrong with Windows or Visual Studio that it requires ugly solutions.
416.
by uecker 7mo ago
This is fitting for something simulating cargo, which is a huge supply chain risk itself.
417.
by uecker 7mo ago
That Rust gives you correctness is very misleading claim.
418.
by uecker 7mo ago
Memory safety is not the same a scorrectness and more advanced type is also not the same thing as correctness.
419.
by uecker 7mo ago
One could import it as ammonia from locations that can produce a lot of it via solar.
420.
by uecker 7mo ago
True, but higher demand for heating in winter is not specific to Germany. In the end, Germany will likely need to import energy anyway - just as it does today. But this means this question may not be the most relevant.

More ›