greghendershott

See also: Recent scrubbing US government web sites for words like "diversity", "equity", and "inclusion".

Writing about biology, finance, or geology? Shrug.

Dumb filtering is bad enough when used by smart people with good intent.

Sure it's offered free of charge -- and immediately next to the big "Download" button is a big "Donate" button.

> Maybe they do actually donate to the project, contribute code, or support in other means.

Maybe instead of shaming, the question is a cue for them to mention one of those things.

---

In the US it's Thanskgiving week. It's nice to give thanks. It can also be nice to give other things -- like support to a project that has saved/made your company non-trivial money. Not required, but nice.

To be clear, I think it would be fair if they answer something like: "I am trying to get my company to contribute... but as my original story showed, my company is pretty shitty at making simple decisions." :)

I rarely read The Register. Is that the usual tone -- as if the author wishes they were Lady Whistledown, the gossip writer on Bridgerton?

On the other hand, I've just spent several more-or-less full-time months taking advantage of the drracket/check-syntax library, provided by the core Racket team.

On the third hand, I spent all that time, so wrt "bus factor 1", there will be no pleasing you. :)

Not sure why you're being down-voted. (As usual here, only clicking a down-vote button contributes little value.)

- You are correct that implementing markdown consistently is hard because there is no real spec. CommonMark is a spec, which helps, but a heroically thorough spec, so it's still not exactly trivial to implement.

- You are correct that markdown can escape to HTML. Indeed certain marketing email "features" probably would do this?

If I am missing something maybe someone could make an actual contribution to the discussion and explain.

In any case I think by far the most important point was made elsewhere: Google AMP is awful for the web and for email, both.

p.s. edit: Actually, I think the even more important point is that anything except plain text email is awful. :) So there, sure, use markdown or org-mode formatting conventions. Humans are pretty good at handling messy human protocols.

This seems unnecessarily harsh.

Capitalization isn't a deep signal.

There are lIsPs like Clojure that argue (> data functions macros). Although I mostly disagree (for example I love Racket macros), I understand and appreciate the sentiment. I have heard it from other people who have worked with a variety of LiSp code bases over the years. TL;DR: Any form of non-trivial DSL needs supporting materials like documentation and a simple, clear design.

Although it is nice to be able to expand macros, fully-expanded macro-generating macros are clear in approximately the same way as assembly language. It is impressive if you can navigate that, but even more impressive if can manage not to need to do so.

> Now an assistive technology user has an equal (and maybe even better) conceptual map of the content and actions they can take on this website compared to a non-assistive technology user. They can get a quick overview of everything on the site, easily navigate to the section of the page they want, and quickly find what they are looking for.

Often there's substantial overlap between improving accessibility and helping "power users".

Sometimes that overlap can help convince managers to spend more time on these kinds of features.

(Unless maybe your whole model is herding people to ads or "promoted" stuff.)

No. :)

Continuations are in the category of things best explained by burrito analogies.

I remember the golden age -- when it seemed like every week there was a Lifehacker.com post about a cool way to use and customize Gmail, GReader, etc. I gladly guzzled the Kool Aid.

It was magnitudes more effective than any marketing I've ever seen Google do. Ethics aside, you could argue that Lifehacker writers should have gotten Google CMO level stock grants.

It's already non-easy to figure out what customers want, make it, make sure they know you have it, and get them to buy it.

On top of that, lately it seems more challenging not to be an oligopoly if you have customers in Europe and/or the US.

I suppose this represents an opportunity for startups to help other startups to manage compliance and payment.