gramstrong

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');

  const NameTag = styled.div`
    font-size: 12pt;
    margin: 3px;
  `;

When you find yourself nesting flexboxes, switch to CSS grid would be my advice.

Yes! Honestly, my commute (probably 20 mins average) was laughable compared to anyone who works in the city. But even after good work days, getting stuck in traffic with other tired people who were driving poorly would absolutely kill my mood for the evening. I could leave work feeling energized and be absolutely dead by the time I got home.

Not to mention that an extra 40 mins every day is huge for anyone who struggles to find time to exercise. For me that means I'm getting a 5-mile run in for "free" everyday and not feeling stressed out about it.

I guess I hope that you're successful, but one would assume that if today's Javascript climate was so toxic and having a tangible effect on your average user (not just the Hacker News user), then...there would already be swarms of clever individuals capitalizing greatly on this apparently obvious state of the web.

His use case at the end is describing microservice architecture. Microservice architecture is trending, ergo JWTs are trending. I don't see the problem.

And I think one of the reasons I like it is because it is simple..it also has decent support for embedded LaTex, and it handles code snippets well. It does the job well for what I use it for, which is normally lecture notes, TODO lists, and idea captures. I don't really use it for documentation or anything else more formal.