sovande

I am not aware of any specific studies that focus on a 30/30 cycle, but there's plenty of research that suggests taking regular breaks is good for you.

The ideal work-break routine is about the work you do, if you control your own time and, of course, what suits you best. For me, I’ve discovered that routine tasks, like writing documentation, do well with a 30-30 cycle. However, when I’m working on problem definition, such as programming and especially debugging, I need more focused time, but I do make sure to take a regular break every hour.

Didn’t read the code yet, but stuff like this tend to be brittle. Do you do something clever around stack overflow, function return overwrite or would that just mess up all coroutines using the same stack?

Not only the manual, but Gnus itself. I remember this guy from the university (UiO) when he started working on Gnus. He was a small celebrity among us informatics students, and we all used Emacs and Gnus, of course.

The effect of globalization is that the west is bringing the rest of the world over the poverty line at the cost of deteriorating ourselves. Hard to say how this will end.

Really cold weather doesn’t have much wind. It’s metrology. Without long term storage, wind power during the winter in the northern hemisphere is just meh. Same with any variable renewable energy source. Instead of celebrating the few times renewable energy actually produces energy when it’s needed we should celebrate every time a new Nuclear power plant comes online.

> Long Long is ridiculous and often confusing

It might be ridiculous, but it’s hardly confusing for a C programmer. But, yeah in and ideal world ‘long’ should just be defined as 64 bits

Exactly this (plus floating point types and unsigned qualifier) and done. It’s standard C, there is no need to invent yet another unnecessary “type” system for standard C native types. I do like bool though.