HN user

sofetch

23 karma
Posts5
Comments24
View on HN

why you felt the need to make a comment just to make yourself look smart.

I hardly think it made me look smart. It's borderline trivial. The parent comment was insanely reductive in the stadnard HN style. I was hoping to help reduce the appearance of future such comments.

Sibling comments indicate that it had no positive effect. Such is life.

Goodbye PowerDNS 6 years ago

Do you have proof that the opposite is true?

Why would this be necessary with the big gaping hole in the assertion?

except for addressing security and abuse.

I expect Google and I have very different conceptions of what qualifies as "abuse" and how to "address" it.

What's not so standard, in my opinion, is that people be required to restrict their use of language to the noted restrictive sense of a definition as used "in [that] document."

Yes, yes, all of the adjectival disclaimers were used to try to align the discussion directly to how words are used "in [that] document." While the document is highly important, there are many technical contexts in which it is completely appropriate to talk about decades without the slightest consideration of how the same term might be used therein.

I feel like this entire thread has been an elaborate attempt to demonstrate that you know an ISO definition. With the carefully constructed adjectives used to describe the definition ("standard technical meaning", "In a technical context") leading inexorably to the "ISO" gotcha.

To save others time, here's the ISO-8601 document which is apparently being referenced: https://dgn.isolutions.iso.org/obp/ui#iso:std:iso:8601:-1:ed...

"decade" is defined in 3.1.2.22:

decade time scale unit (3.1.1.7) of 10 calendar years (3.1.2.21), beginning with a year whose year number is divisible without remainder by ten Note 1 to entry: Decade is also used to refer to an arbitrary duration (3.1.1.8) of 10 years, however decade is not used as such in this document.

Erlang/OTP 20.0 9 years ago

Nerves boots into the ErlangVM, but runs on a buildroot Linux. This makes it possible to run on a wide variety of hardware, but with the associated baggage.

GRiSP uses RTEMS[0] as its base which should make its performance more predictable.

[0] https://www.rtems.org/