When I was on-call for a big project, I jumped every time my phone rang. It wasn't a good experience at all.
"We are at the fair, I have 18 customers lined up but I can't take orders. Can you fix this now or should I start taking them on paper?"
You know the joke that atheists don't believe in god until the plane nosedives? That was the moment for me :)
"Oh, I... I need to see the error message before I can say anything. We don't have any errors logged. Hmm... Would you allow me to remote into your device?"
"Can't do that. We lost the internet connection here, sorry."
This is my favorite mobile game of all time. The AI is also very weird (in a good way) and sometimes genius! It feels like the custom maps I used to create with "Age of Empires II" in which I let random units fight against each other.
But the GDPR itself is written in legalese. There are many interpretations like yours, but then, without a lawyer, it's a dangerous game to play. The cost of the lawyer may be prohibitive to some small businesses, let alone side-projects.
I'm actually pro-GDPR but this needs to be kept in mind.
I guess that depends on how many you want to buy. I can't come up with a reason why one would buy many domains with an obscure TLD, especially for private use but that doesn't mean that there isn't one.
I'm very happy it's not written in {insert technology unpopular among hackers to gather points}.
Nowhere is Electron mentioned and still comes the hate. A close friend of mine (not a web-developer, unlike me) has a very popular app (>10K users) which uses Electron and he got only around 30 performance complaints last year and all of them could be solved without rewriting the damn thing. The app has a giant "Feedback" button in the main view and there are at least 10 bug reports / suggestions per day (I manage the support desk).
This is getting to the levels of this silly Java hate because everyone thought the performance of Eclipse from years ago still is the state-of-the-art for Java development. There are many bad electron-based apps, that is for sure and completely normal because the barrier to entry is so low. Yeah and there is Slack, but don't complain if you gave up IRC for that incompatible piece of... Whatever.
IMHO it's bad, as long as a lifestyle is pushed heavily from people who aren't immediate family. Doesn't matter if it's "hookup culture" or waiting for the prince charming to marry.
Why do they even market those new chips? It's the average performance that matters and you can wait 10 seconds to open an app, as, in the end it didn't change the average performance from the case that you would open it in a second and stare at it 9 seconds being stunned by its speed.
I try to write a first prototype without any regards to best practices. When I'm doing a rewrite (of a prototype, not a full product), by then I already have the structure in my mind and perfectionism then can't get in the way. For example I don't design unnecessarily complex sub systems just to get the flexibility I don't need.
it's the same brand, I think if they have the tendency to do this for their keyboard and mouse, who knows what they'll end up doing with their laptops.
My only exposure to anime is his films (friend suggested them, first I ignored the recommendation because they were "for kids" and some time later I watched "Spirited away" by luck and you know the rest of the story) and want to explore more, I thought maybe you could have some suggestions from your other favorites?
AFAIK it doesn't, but I'm just learning. My understanding is the standard way of doing things work if you are creating the most boring CRUD apps but you need to "bend the rules" a bit to make it work for your use case very often - as long as you keep it newcomer-friendly.
Correct me if I'm wrong but I think what you have is described as an "action dispatcher" these days.
For what it's worth, I think, we can define the whole Flux architecture in somewhat-skewed MVC terms. Not trying to downplay the usefulness of Flux here but if I'm not all wrong, it would've helped many people if we kept at least some of the terms from MVC or MVVM.
"We are at the fair, I have 18 customers lined up but I can't take orders. Can you fix this now or should I start taking them on paper?"
You know the joke that atheists don't believe in god until the plane nosedives? That was the moment for me :)
"Oh, I... I need to see the error message before I can say anything. We don't have any errors logged. Hmm... Would you allow me to remote into your device?"
"Can't do that. We lost the internet connection here, sorry."
Ugh.