>I honestly think i was pretty respectful to everyone
Cursing at people, taking hidden photos, posting them publicly laughing at the situation, mocking employees and the police, is the opposite of being respectful.
Reading this wasn't easy, but let's appreciate the authenticity.
This post doesn't reflect well on you, you were disrespectful to every person in the story. You really need to grow up, and you could've handled this way better.
You could have, for example, asked exactly what their concerns were, and proposed ways to address them.
Your site looks very amateur, but from your description, it doesn't sound like you are doing anything clearly forbidden by law.
>someone had written a comment about S which he did not like.
Couldn't this also be done in the reddit? Then is the lack of moderation and language filters the problem?
>In a sense, it is the difference between the way an entrepreneur might approach doing a startup versus how we build modern skyscrapers. Evolution versus Engineering.
There are core differences in software engineering that, unlike in construction work:
- making changes is often cheaper
- we might not know beforehand everything that is needed to be built, especially unknown unknowns
I would still agree that the truth is somewhere in between, but I would argue that, for software, it's closer to the evolutionary approach.
Exactly this. OP fails to understand that there are reasons why it was done this way, and that someone who spent thousand of hours working on this might know something that they don't.
That's an incorrect answer. A light-day means "the distance covered by the speed of light in a day (24h)". The day length is related to Earth's turn speed, it's not related to its distance to the sun.
>How many millions codebases use it is irrelevant.
It is relevant, because it speaks to the reliability of the dependency. `pydantic` has 24.7k Github stars and was last updated 52 minutes ago.
Adding a random dependency `dacite`, which has 1.9k Github stars, no one has ever heard of, and was last updated 4 months ago, introduces way more complexity and sources of instabilities than propagating `pydantic`.
>The less your core logic depends on specific tools or libraries, the easier it becomes to maintain, test, or even replace parts of your system without causing everything to break.
It seems like the author doesn't like depending on `pydantic`, simply because it's a third party dependency. To solve this they introduce another, but more obscure, third party dependency called `dacite`, that converts `pydantic` to `dataclasses`.
It's more likely that `dacite` is going to break your application, than `pydantic`, a library used by millions of users in huge projects, ever will. Not to mention the complexity overhead introduced by this non sense mapping.