kattfisk

A stronger argument IMO is that those types of crimes are premeditated, calculated and committed by those who have many other options. So deterrents are likely to actually work against them.

Not that I agree with you. But there's an argument to be made for using deterrents where they are likely to work. Rather than against the desperate or impulsive.

If it's pornography of an unwilling subject, surely the distribution and consumption is harmful to the subject, as it's a violation of their privacy and integrity.

If someone had put secret cameras in your bedroom, would you be completely cool with them selling the pictures online?

What if you were abused, let's say threatened with a weapon and forced to undress in front of a camera, a traumatic experience for sure. Afterwards you learn that the film is being traded between people who get off on this stuff. Would that really not feel like a further violation?

Would you really be unaffected by the knowledge that for the rest of your life, at any time, there could be creeps getting off on your abuse?

I found Inkscape when I needed to make some diagrams, and even though that's not really what it's for, it blows dedicated diagram tools out of the water.

Inkscape is actually fun to use because it strikes a nice balance between easy and powerful.

My only problem with GIMP lately has been that by default it's used monochrome tool icons which are really hard to tell apart. Which seems like a real form-over-function decision (likely made by the distribution though).

My experience with Jetbrains was that they did not rely on vendor lock-in, but on actually making a product worth paying for. I could move my projects away from their suite easily, the build tools and scripts where all third-party open-source. I just didn't want to.

But perhaps things are different in other spaces. I can imagine using Kotlin might lock you in more.

It's not necessarily true. There are other interpretations that are equally valid as far as we currently know. They are just less famous.

They really are letting the milk go slightly rancid as a method of preservation. Which is why their chocolate tastes like rancid milk (or vomit).

Now I understand that those who grew up eating it are just used to the flavor. The real mystery is how it became so popular in the first place. How was vomit-flavored chocolate preferable to not having chocolate?

I've yet to see any that are of any use.

A pet peeve of mine is documentation that describes how the code works. If I want to know that, I can just read it (perhaps assisted by an IDE or debugger).*

What I need documented is why the code works like that. How is it intended to be used? What quirks and gotchas are there?

*If the code is not readable it needs to be refactored, not documented.

Just shifting the tax burden from salaries toward capital should make it less of a problem. When capital income is taxed less than salaries wealth concentration gets worse as workers are replaced.

But hey, GDP line goes up, so it must be good right?

Completely depends on how you live.

Someone who lives in a house with plenty of storage and a 30 minute drive to the nearest store will have a lot of food at home. Whereas someone who lives in a tiny apartment with a five minute walk to the store will not.

In general, places like American suburbs, with huge single-family homes, no stores and complete reliance on cars, are rare in Europe.

Good thing the US doesn't recognize the authority of the International Criminal Court, so there's no risk of them having to face consequences for their war crimes.

They even have a law that makes it illegal to cooperate with the ICC in bringing US personnel to justice, and that allows the president to use any force necessary to prevent it from happening.

Moving fast doesn't have to mean poor workmanship.

To make an analogy, if you want to be able to make a cup of coffee fast, you need to make sure that the coffee beans, the water, and the brewer are all near each other, that there is electricity and that the water is running. These are all things that enable you to move fast, but they don't decrease quality, if anything they increase quality because you aren't wasting time and effort tackling obstacles unrelated to brewing.

Which is in fact the point of the article. That you should make sure you have a good development environment, with support systems and processes, so that you can work effectively even if your developers are not savants. Rather than trying to hire people who are good enough to do a decent job even in the worst environments.

🆗