top | item 41256301

(no title)

g15jv2dp | 1 year ago

There's no reason it wouldn't "work", the question is "why". Having such precise dates obviously comes with some compromises (e.g., the representation is larger, or it's variable depending on the value which comes with additional complexity, etc.). So surely there must be some pros to counterbalance the cons. "Because it's what Go does" is an answer, but I don't know if it's a convincing one.

discuss

order

nalgeon|1 year ago

[deleted]

g15jv2dp|1 year ago

WTF. I'm interested in what you've created and want to understand the reason for your design decisions, and this is how you reply?

edit: Well, it seems that the parent comment has been edited. But honestly, after reading the initial comment, I'm not interested in engaging in any way whatsoever with this person.

goldfishgold|1 year ago

There's nothing in the linked blog post justifying why you might want a higher precision time. In fact the blog post would benefit from an explanation that outlines the current datetimes in sqlite and why they're insufficient.

marcellus23|1 year ago

I think you're being overly defensive. The GP is curious about the decisions you made, and just asking questions in a bit of a blunt (but not rude or accusatory) style that's typical for HN.

edit: the comment I'm responding to was much more vitriolic, it's since been edited