Forgot your password?

typodupeerror
Australia

Australian Scientists Discover 'Oldest Living Thing On Earth' 172

Posted by timothy
from the sorry-dad's-television dept.
New submitter offsafely writes "Scientists in Australia have discovered the oldest living life-form to date: a small patch of Ancient Seagrass, dated through DNA sequencing at 200,000 years old." Says the linked article: "This is far older than the current known oldest species, a Tasmanian plant that is believed to be 43,000 years old." What I want to know is, How does it taste?

Comment: Re:How to poke a dead body (Score 1) 545

by obarel (#38699208) Attached to: How To Get Developers To Document Code

Yes, I completely agree, of course. Having "17" in the code requires some explanation.
In this case, I'd probably have something like:

enum { OBJECT_INFO_SIZE = 17 };

(my assumption here is that I need to skip a certain size in bytes in some byte stream that needs to be parsed - of course if sizeof(struct objectInfo) works then that's even better).

But even so, someone might say "I understand that you are skipping objectInfo, but *why*?" where a comment could really help:
/* Skipping the objectInfo strucutre, as it is optional [section 4.2.2] */
offset += OBJECT_INFO_SIZE;

Comment: Re:How to poke a dead body (Score 1) 545

by obarel (#38696596) Attached to: How To Get Developers To Document Code

Well, I've also seen comments like this:

/* Increase byte count by 17 */
byteCount -= 17;

But the comment can become useful if you only change it slightly:

/* Skip the objectInfo structure */
offset += 17;

Then you don't have to search in the code where objectInfo is stored - it's clear that it isn't.

Sometimes I find myself reading the code, explaining it to someone, and then I say "actually, that's exactly what the comment is saying..."

Comment: Re:How to poke a dead body (Score 1) 545

by obarel (#38690908) Attached to: How To Get Developers To Document Code

There's also a risk that someone would introduce a bug while keeping the documentation correct. So what? We live in a dangerous world.

Comments can be useful, and there is no need to avoid them just because they could be wrong. If the code is wrong, you need to know what it's supposed to do (and why) before you can decide that it's wrong. That's where comments can make your life easier.

Comment: Re:Tolkien's prose (Score 2) 505

by obarel (#38644230) Attached to: JRR Tolkien Denied Nobel Due To Low Quality Prose

I'm always annoyed when I watch a film, find it boring / stupid, and then get told by fans that the film doesn't make sense unless I read the book first. If I wanted to read the book, I would have read the book, but I actually wanted to watch a film. If the director can't do his job, that's not my problem (even though I get to pay for the ticket, the popcorn, and the time).

But then I realise that most of the films-from-books I've watched, having read the books first, were over-simplified, shortened, shallow versions of the book, and would probably be boring / stupid / full of obscure references that wouldn't make sense to anyone who hasn't read the book first.

The fact is, it's a huge challenge to convert thought provoking prose which takes you days or weeks to read into 2 hours of action. Even films that are based on short, simple stories have serious issues in most cases. That is, unless the books themselves are nothing but action and read like a script...

It's no longer a question of staying healthy. It's a question of finding a sickness you like. -- Jackie Mason

Working...