I.e. the player view is a left-handed guitar (confusing, but to leftie players); audience view, right-handed.

> It's more cost-effective for Amazon to send a $50 shirt to the dumpster rather than resell it.

It's not a $50 shirt. It's like a $5 shirt to them, which some sucker is willing to pay $50 for. Used, it becomes a $10 shirt.

A dumpster can be found right in the neck of the woods of where the returning customer lives, whereas it may have to travel far and pass through more processing if it goes to another customer elsewhere.

It needs to be inspected, repacked.

There is a risk in every returned item. Sometimes people return a perfectly good item. But sometimes it's because there is something wrong with the item, such that the next buyer is also likely to return it, even if they get it cheaper.

Basically returned items are entirely outside of the profit-optimized delivery path. They incur costs and risks, at a reduced revenue.

I'd never return an item which matches the description and isn't damaged.

If it isn't damaged in any way but does not match the description, that's a problem; if it is sold with the same description, the next customer will also see that it doesn't match. A new listing has to be created for that product. Not gonna happen, or not in the processing time frame of that particular return.

I have custom syntax highlighting. For instance, I have a home-grown script which takes a man page file (identified by a suffix like .1) and renders it readably, so it looks like a man page on your terminal, rather than nroff source code. (The only unsolved problem is that CGIT renders a column of the original line numbers down the left, which exceeds the length of the rendered page.) I also have accurate syntax highlighting for a home-grown programming language. That syntax highlighting exists only for Vim, which has a superb syntax highlighting engine. So in fact Vim is launched, via expect, to do some HTML rendering! There is no way that is getting translated into client-side.

Pre-rendering is not really an option over numerous git repos, that have numerous files in them, with the added dimension of history. What CGIT has instead is tunable caching.

Bots which aggressively scrape the history are hostile to the caching scheme, however. It works best for human visitors which mostly look at the head of the master branch in each repo, and poke around just a little bit in the history or look at other branches.

However, there is an obvious incentive to minimize these no-return refunds and require users to print labels and go through the motion of returning items that won't be restocked.

It discourages fraud: people abusing the no-return refund as a way of getting free stuff!

The no-return refund has to be a kind of perk for the customer who rarely returns anything or whatever.

I would say that it would be astonishing if Amazon pretending to accept returns and then throwing away is a thing that absolutely does not happen, and honestly cannot blame them for it. We are a throw-away-stuff society, and Amazon is not outside of that society.

Indeed, but, by the way, those are assumptions that some newer languages now make about the entire world.

Stick with it for five (5) years consistently, then report on it.

The main problem on my site is that bots hit the CGIT repo, where visiting files triggers syntax highlighting scripts.

I put in a skill-testing-question type system where you get a maximally long-lived access cookie if you answer right (so legit users are bothered as infrequently as possible).

:)

OpenLook (closed-source 1980s Unix desktop)

The Open Group (oligarchy of Unix vendors organized around a proprietary standard)

X/Open, Open Software Foundation (OSF) (Groups that merged to form The Open Group)

OpenStep (Proprietary software covered by a commercial EULA from NeXT)

OpenGL, OpenMAX, ...

You've inherited OpenFatigue from your dad!

More:

In the Lisp world, Open Genera.

OpenDOC, OpenVMS, OpenType, ...