HN user

gramstrong

298 karma
Posts0
Comments103
View on HN
No posts found.

A better question is where do you draw the line in terms of companies supplying actors that are directly contributing to human suffering? We (America, but others as well) cut trade and enact sanctions exactly for that reason, all the time. This idea that capitalism should be entirely apolitical is farce, people only want it to be apolitical as far as they are personally comfortable.

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?

No it's not. doctorhandshake wasn't even making an analogy. They were applying OP's rule (we shouldn't dictate business based on political beliefs) to a hypothetical in order to demonstrate its negative moral outcome.

Do we want hammers to be restricted to only those whose political ideologies align with ours?

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.

Social media is slightly different in that content is catered to the individual, so I'd guess that it does a slightly better job at siloing people. It also allows others on the platform to provide the catered content as opposed to the media corporation providing you with their political vision (although I'm not sure which is better or worse).

I don't think that private censorship is necessarily a problem, but I do think that corporations having the authority to exercise what is a pretty effective form of muting is a problem. This is of course due to the size and prevalence of Facebook as a platform. I don't think the solution (or best solution, at least) is to break up the tech giants as Elizabeth Warren would suggest. I would instead prefer to see some form of socialized media platforms that take the market question out of the equation (does white supremacy content hurt Facebook more than removing it would?). This is of course, because, the market is not always right (even though in this case I would make a strong argument that it is).

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 work might bring relief to the larger cities, but it also opens up smaller, often blue-collar industry towns up for gentrification, out-pricing the existing residents in a place where there wouldn't normally be "office jobs".

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.

I think equating ugly with hard-to-read is a common mistake

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 disagree :) It's easier for me to look at an object and its contents and see where it is referenced. I think switch statements are ugly. I think if/else blocks are ugly. I prefer boolean statements when possible, although definitely not nested ternaries.

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

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

It shouldn't be, AFAIK they should be used together. Use CSS grid for general layout of multiple elements on a page or area. Use flexbox to style something that suits a row or column.

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

hopefully never have to commute ever again

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 hope that by talking about what it means to build well when trying to serve everybody, we can show businesses how short they’re falling of the mark — and why those common root-causes in JS-centric development are so toxic.

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.

I think anyone who gives an article the now cliche "Why [popular thing] sucks" doesn't care about receiving charitable responses.

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

Love letter to Vue 8 years ago

I don't think you are really going to have to concede to the latest hotness for a very long time. There's still plenty of jobs for building and maintaining PHP + jQuery applications. Shoot, I spent a lot of time at my last job maintaining Classic ASP serving up HTML. React isn't going anywhere.

I've been using BoostNote pretty regularly for about 6 months, and I like it fine, but I wish it weren't an Electron App. There's not really any sharing/collaborating as far as I know, and the note structuring/search leaves a little bit to be desired (compared to say, OneNote). The good news is that it's open-source!

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.

It's government surveillance. The mall can collect and record whatever data they want on their property, who cares. We can compel our government to not accept and blindly process this data en masse. It's the same as taking bulk data from Facebook, or Google, and looking for the .0001% that points to a criminal. Many, myself included, believe that this is wrong.