uecker

17 ms·

421.
by uecker 7mo ago
Germany has more wind in winter, so traditionally has more production of renewables in winter months.
422.
by uecker 7mo ago
It also has to be considered in light of the fact that Lennart builds a company for "cryptographically verifiable integrity on Linux".
423.
by uecker 7mo ago
Not sure what you are trying to say. Inconsistent definitions is a consequence of being able to build things separately, which is a major feature of C and C++, although in C++ it does not work well anymore. The reason to not build things
424.
by uecker 7mo ago
It will be a mix. There is certainly still a lot which can be done on the demand side, e.g. when to cool a cool storage house during the day, or when to run certain production lines.
425.
by uecker 7mo ago
I am tempted to click the "report abuse" link ;-)
426.
by uecker 7mo ago
No, capacity factor is a distraction. The only meaningful question is whether it is cost effective or not compared to other production methods,, and solar - taking into account the low capacity factor - is starting to look very good.
427.
by uecker 7mo ago
Better importing solar panels once in a while than importing fossil fuels all the time.
428.
by uecker 7mo ago
C++ ODR requires different definition to consist of the same tokens, and if not the the program is IFNDR. Name mangling catches some stuff, but this becomes less relevant today with more things being generated via templates from headers. I
429.
by uecker 7mo ago
The ODR problem is much more benign in C. Undefined behavior at translation time (~ IFNDR) still exists in C but for C2y we have removed most of it already.
430.
by uecker 7mo ago
The editor. Otherwise, the site looks great!
431.
by uecker 7mo ago
Why does this need to access to all my repository just for generating a PR?
432.
by uecker 7mo ago
There is a lot of tooling for C though, just not in mainstream compilers.
433.
by uecker 7mo ago
Not having experience myself, how is GNAT?
434.
by uecker 7mo ago
Neither "ODR violations" nor IFNDR exist in C. Incompatibility across translation units can cause undefined behavior in C, but this can easily be avoided.
435.
by uecker 7mo ago
I was talking about building code not run-time. But regarding run-time, no other language does outperform C in practice, although your argument about "better semantics" has some grain of truth in it, it does not apply to any exist
436.
by uecker 7mo ago
"That makes everything slow, inefficient, and widely dangerous." There nothing faster and more efficient than building C programs. I also not sure what is dangerous in having libraries. C++ is quite different though.
437.
by uecker 7mo ago
You could call it x.val, no need to use a long field name. But you would rarely access it directly anyway. I do not see any type checking advantage here for other languages.
438.
by uecker 7mo ago
A user in C can just wrap the type in a structure and define explicit operations on it. You do not need another language for this.
439.
by uecker 7mo ago
One doesn't need the undefined behavior and this is not what I said, and one could make it erroneous behavior. But with mainstream compilers being able to trap or wrap, it would be no practical difference except in marketing.
440.
by uecker 7mo ago
Sure, buddy.
441.
by uecker 7mo ago
IMHO the security advantage of Wayland is mostly a myth and probably the same is true regarding tearing. The later is probably more an issue with respect to drivers and defaults.
442.
by uecker 7mo ago
"Some people just want to live in the 80s forever." I think this shaming of free software users that want to make other choices is rather terrible.
443.
by uecker 7mo ago
And X11 always had a mechanism for isolating clients as well, i.e. trusted and untrusted clients. Nobody used it because it was irrelevant before sandboxing.
444.
by uecker 7mo ago
It is definitely not a language that can be learned by reading blogs. But the advice really applies to almost everything you do related to security, safety and reliability. In other languages you may have a panic in production or a supply c
445.
by uecker 7mo ago
There are other languages such as Ada that allow you to more precisely specify such things. Before requesting many new types for C, one should clarify why those languages did not already replace C. I agree though that using "unsigned&q
446.
by uecker 7mo ago
While standard requires twos-complement we did not make all shift cases defined so far.
447.
by uecker 7mo ago
The standard will not forbid anything that breaks billions of lines of code still be used and maintained. But it is easy enough to use modern tooling and coding styles to deal with signed overflow. Nowadays, silent unsigned wrap around caus
448.
by uecker 7mo ago
That makes me worry that you code actually has more issues because with small _BitInt you would run into signed overflow more often.
449.
by uecker 7mo ago
You could just use -Wsign-conversion.
450.
by uecker 7mo ago
Thanks! I will consider the Librem 5 for my next phone.

More ›