> The report estimates that carbon emissions from models with the least efficient inference are over 10 times as high as those with the most efficient inference. DeepSeek’s V3 models were estimated to consume around 23 watts when responding to a “medium-length” prompt, while Claude 4 Opus was estimated to consume about 5 watts.
This makes absolutely no sense. I suppose they meant watt hours, and that's a weird way to explain carbon emissions...
Not offended and I find it funny, though you nailed my itching:
> "Veganism is a philosophy and way of living which seeks to exclude—as far as is possible and practicable—all forms of exploitation of, and cruelty to, animals for food, clothing or any other purpose; and by extension, promotes the development and use of animal-free alternatives for the benefit of animals, humans and the environment. In dietary terms it denotes the practice of dispensing with all products derived wholly or partly from animals."
My personal take is yes, assuming there's no animal exploitation or cruelty involved.
That said AFAIK there is no consensus: some abstain from all animal inputs while others focus on avoiding harm, which itself can be interpreted in different ways. It's more a philosophy than a rulebook, lab-grown meat kind of sits in a gray area. I'd be curious to try it :-)
Nice philosophical point. To iron-on more irony, zooming out a little, one could also argue much real historical experience was first erased when it was written down with the presumption of authority.
It's impressive how much details they give in the release notes, down to the filenames of added sprites and changes to the shaders. I can't think of another game that does that.
Java Minecraft has always been super transparent. I remember being shocked when I signed up for their early modding SDK prior to Microsoft and it was literally just the source code for Minecraft that I could compile against.
In science fiction maybe. We're hitting real limits on compute while AI is still far from a level where it would harmful, and FHE is orders of magnitude less efficient than direct calculation.
Yes, you are right that a post-increment in a switch statement is no differently than elsewhere. The goal I had set was to implement a small easy to read C compiler. For that reason I tried to implement it as a single pass compiler that would generate code on the fly. The target was a small stack based language, which did support variable scoping and gotos, but not a switch. My first attempt was to implement the switch statement with chained if-statements where the switch expression would be evaluate over and over again. This only works if the switch expression did not have side effects and that the 'default' case would always come at the end. But that did not work, so I had to come up with another solution, a solution that would only evaluate the switch expression once. I decided to store the value on the stack and duplicate the value whenever needed for comparison. But that would require the value to be popped once a case was selected. A goto jumping from one case to another should land after the location where the value is popped, otherwise it would corrupt the stack. I fear that this solution does not work correctly when a case occurs within a for, while, do-loop, or if-statement. cases may occur everywhere in the enclosed code. This is sometimes used to emulate co-routines or generator functions.
Did you know that C has a keyword that is only a keyword in some places and that there is a function that can have two or three parameters?
Maybe the strategy from TCC itself is useful here: emit case bodies as a giant block first then jump back with cascaded if's at end. https://godbolt.org/z/TdE11jjxb
> Did you know that C has a keyword that is only a keyword in some places and that there is a function that can have two or three parameters?
defined is a pre-processor 'keyword' that only is used in conditions after #if and #elif. Elsewhere it is ignored by the pre-processor. You could argue that it is not a real keyword. But lets see what happens when you define it as a define with: '#define defined 1'.
The function main can be defined with two or three parameters. The third contains the environment. You can also get the environment with 'argv + (argc + 1)'.
reply