they're building a generic tool and simply can't be responsible for how others use it

AutoDesk is undoubtedly aware of its sales with a massive coal plant, unless they are a horribly run and incredibly lucky company. Beyond that, it seems like AutoDesk has gone as far as promoting their involvement in developing the excavators, no?

Would you sell hammers to a sweat shop?

Yeah, why not? If you're a hammer manufacturer, then you should absolutely concern yourself with whether or not you're dealing business with ethical consumers.

I think if you commit yourself to your ideal, you're either going to end up being complicit in some really nasty stuff, or end up drawing a very arbitrary "line" where you stop being apolitical.

Normally an extreme appeal to emotion. In this case excessive use of caps-lock and a fictional narrative that doesn't substantiate itself.

I'm not sure what the best social media model for such a platform would be -- preferably something mostly non-anonymous like Facebook, but self-moderated (within the bounds of the law) like Reddit used to be.

Remote workers who previously worked in Seattle have done this to where I live now - which has only displaced their housing affordability crisis to a different location, and on to a different demographic.

This is just a semantics argument. I can replace "ugly" with "hard-to-read" if you want. I think it's both, in this instance.

>Honestly, I find that rating the readability of the object versions vs the switch statement is bikeshedding.

I agree in the context of code review, but since this is what we're talking about I figured I'd share my opinion.

>Another thing that is worth mentioning is that objects consume memory and allocating memory in JS for this is just wasting orders of magnitudes more cycles and sacrificing throughput for no good reason - other than to try to be clever and avoid an idiomatic and optimizable construct.

Premature optimization. If you need to optimize, then do it. Otherwise you should prioritize what you consider understandable and easy-to-write code. I guarantee the vast majority of javascript written would not be ill-affected by this.

I'm sure I'll get flamed, but I really liked this:

  const getPosition = position =>
      ({
          first: 'first',
          second: 'second',
          third: 'third'
      }[position] || 'infinite');