borromakot

Haven't looked at the actual product, but my personal advice to this team is not to use terms like `Next-Gen` and `Modern` as their taglines. It turns of real significant buyers from consideration IMHO.

When I hear "next-gen" and "modern" I hear "we don't have a real value proposition except 'its not the incumbent thing'".

It is sad that such a song and dance is required when anyone with half a brain can read the racism in DHH's post.

Imagine a scenario that a black family moved into your neighborhood and started causing a bunch of problems. There are no other black people in the neighborhood.

It should take you a picosecond to figure out which one of these is obviously racist and which isn't:

"We need to remove the black people from our neighborhood"

"We need to remove the new family from our neighborhood"

People like "well he has a good point they are causing problems" so technically the set of "black people" and "people who are currently causing problems in our neighborhood" are the same set. This is irrelevant.

...thats his point. He doesn't want to shout and shame. So he wrote a blog post.

"Hence" means, "therefore", as in "I didn't want to shout and shame, therefore I wrote this blog post"

it is not just you

holy shit this is awesome.

pretty cool, any plans on making it OSS some day or sharing more about your process? The Ash community would love that I'm sure.

Make sure to tell the team about it, and ask questions about it. Sometimes it's hard to tell the difference between magic and a misunderstanding

If I sounded snarky that wasn't my intention. At the end of the day though it doesn't feel like you read the article which was clearly in a different context than the one in which you responded. FWIW I didn't expect this small article speaking to a small audience (Elixir devs) to make the rounds on hacker news.

I agree on the importance of defining terms, and I think the important thing here is that "process" in Joe's parlance is not an OS level process, it is one of a fleet of processes running inside the BEAM VM. And the "system" in this case is the supervisory system around it, which itself consists of individual processes.

I'm critiquing a common misunderstanding of the phrase "Let it crash", whereby effectively no local error handling is performed. This leads to worse user experiences and worse outcomes in general. I understand that you're offering critique, but it again sounds like you're critiquing a reductive element (the headline itself).