bitcrafter

I for one like to keep things simple and just express everything directly in units of the number of periods of the radiation emitted by the ground state hyperfine levels of Cesium-133.

Is it worse than Clojure?

Uh, good for you?

Nonetheless, being able to produce tritium, which is the claim that appears in the headline and the article, is very useful, in part because many reactors use it as a fuel source.

There is only one place where I see "more fuel" show up, which is this single sentence:

The ability to generate tritium within the reactor is crucial. A sustainable fusion energy system needs to produce more fuel than it consumes. This development shows a path toward solving that engineering challenge.

I agree that this single sentence could have been better worded.

Any element below iron is technically fuel for fusion.

I'm confused... was that wall of text supposed to have sold me on something?

You want to turn my 300 lines of clear, readable and concise logic into 1,000 lines of English paragraphs that break up the functions of my code into yet smaller pieces of code devoid of context?

If a function has 300 lines without a lot of supporting documentation then I doubt that it is "clear, readable and concise" anyway.

Now I have to dig through that book, ignoring all the shit I’ve read hundreds of times because it doesn’t compile into anything, just to debug an off-by-1 error in a loop buried in a paragraph explaining the original developers diatribe on why we’re looping over that range?

I have never found it hard at all to skip past comments that are not relevant because my code editor helpfully colors them differently from the rest of the code, making it easy. Does your editor not do the same?

(Also, by now you should be especially good at skipping past it, given that you have apparently "read [it] hundreds of times" instead of skipping past it, for some reason.)

This is the sort of academic crap that sounds good but in practice is just terrible for anything other than small projects that are intended specifically to teach.

It depends on what you are doing. If you are implementing relatively simple logic like a REST API handler, then it is probably overkill. If you are implementing a relatively advanced algorithm, then having a running narrative of what is going can be extremely helpful.

It's not immediately obvious to me where the examples are.

If you have not already read through it, there is a ton of useful information about Python's data model in the user manual; it is my go-to resource when I want to do weird stuff with metaclasses and the like.

Furthermore, you might find it interesting to peruse the C code that is generated by Cython, because it gives you a concrete view of the kinds of steps that Python has to go through from a C perspective to work within its data model. (Cython is a bit faster than Python because it does not have to interpret bytecode, but unless you use special directives it still has to e.g. do general attribute lookups whenever you interact with a Python value, even if the value is an integer, and maintain reference counts.)

Finally, you might also get a lot out of skimming through the CPython bytecode instructions, as this has a lot of interesting details about how the bytecode interpreter works in practice.

I think that you may have missed the reference.

One should be wary about voting for the Alligators Eating Peoples' Faces party...

Yes, because of all the daemons.