kivikakk

Or “belt-and-braces”. What the fuck.

Consider Forgejo: https://forgejo.org/.

Something very, very different to everyone else, it would seem.

Your browser prefetch probably already did the DNS lookup anyway.

10% of a very potent dosage is hardly homeopathy.

In general people have come to expect that hitting return once in a comment field on GitHub will produce a newline, having been the case for many years, so we try to preserve that expectation. Hence not changing the option being used when rendering comments.

Conversely, they don't expect the same from Markdown files stored in their repository (e.g. I put each sentence in a paragraph on its own line for my blog, for easier diffing and editing). Additionally, we couldn't normalise these documents even if we wanted (to prevent everything breaking by being over-vertically spaced). Hence not changing the option being not used in this case!

As of this announcement, file backed content _does_ use GFM (try a table!), but not the `hardbreaks` option.

GFM itself leaves that line unchanged because we don't actually change that option in our implementation — the reference implementation `cmark` (which we built upon) supplies the "hardbreaks" option, described as follows:

> --hardbreaks Treat newlines as hard line breaks

We turn this option on when rendering issues, issue comments and so on, but leave it off when rendering blobs (such as README.md). Both are GFM, one just uses this option to make it more conducive to communication.

Right here: https://github.github.com/gfm/#strikethrough-extension- :)

> So why haven't Github, Shopify, Twitch, Groupon or others pour any resources in ?

GitHub does; Tenderlove works on Ruby there!

> I am not going to read Techcrunch article about [mental health].

Then:

> Mental health is a subject that doesn't get attention in any facet of American culture.

???

Major (consumer) ISPs in Australia offer native dual-stack.

It seems disingenuous to describe ";" as a "comment macro". It's not a macro, it just causes the reader to ignore characters until EOF, \r, or \n. (https://github.com/clojure/clojure/blob/master/src/jvm/cloju...)

The fact that the CommentReader is dispatched from a table called "macros" (https://github.com/clojure/clojure/blob/master/src/jvm/cloju...) means nothing, unless you also call string literals "string macros", s-expressions "s-exp macros", etc., since mostly everything is dispatched from that table.

Neither in Australia.

Your account is dead.

> the subset that it optimized for would still be C

This doesn't mean to imply the subset is the entirety of C; it means the subset is part of the definition of C — just like you can say "'int x = 4;' is C", even though it's a (demonstration of a) subset of C.

The JavaScript which happens to be optimised under the name "asm.js" is still JavaScript that executes in any non-optimising runtime, and the semantics with those optimisations and without are the same.

Fuck that noise. It's representative of a shit state of affairs when 'mastery' of one particular language is necessary to gain respect among fluent speakers. No respect for those who haven't 'mastered' the thing we have mastery of? Fuck, it sounds like a recipe for supremacy or something.

Or .MUM?

There are a couple: https://www.google.com.au/search?q=site%3A.museum

One reason: there can only be so many root nameservers, which are capable of only so much traffic. Additional layers help keep DNS decentralised.

Usually, "transgendered" is not preferred by trans* people themselves. It sounds awkward.

For a transgender person, one's gender is always what it is; it's just the body that might need adjustment. Also, it's hard to say when one's "arrived" anyway; there's not really a point when you just say "tada!" and you're all done. It's a very gradual process.

Some trans* people will still rrefer to themselves as trans* even "after" transition (inasmuch as you can pinpoint an 'after') because they internalise that as part of their identity; others don't.

Hint: if you leave off the word transgender, it should still describe who they are; Audrey's a woman. Audrey's transgender. Audrey's a transgender woman.

It's probably just be the circles you travel in, but to me it wasn't jarring whatsoever. (I use the singular they in any case when I'm referring to someone whose gender I don't know/a hypothetical person where gender doesn't come into it, or if that's what they want me to use!)

Sure, but it's the #2 bullet-point on their home page, and they don't use the word reliably, but:

> Be confident sending private information and pictures.

... be confident? That kinda implies it's reliable enough to be confident in it.

"completely incorrect" is useless prescriptivism. They can call it incorrect all they like, it won't stop anyone.

I saw the quoted text in the original page and stopped reading right there; who on earth wants to use a query library where you have no idea whether what's returned is an array of elements or just an element?

I think that happened: http://web.mit.edu/remy/

Or just install it on a Linux VM!

Also a tad ironic in light of his subsequent invocation of "belive".