43 karma · joined January 8, 2016
I assume Google is reporting on my Chromecast usage, but Vizio doing unaccepted updates to essentially brick my tv unless I agree to be monitored? That’s a step or two too far.
Worse, I couldn’t tell it to stop connecting to my WiFi after all this happened. I had to ban the TV from my LAN and change the WiFi credentials.
I spent a lot of money on that TV, only to have it go rogue on me.
In either case, the subject of a decent article might be: setting up automated exports from service features like Takeout, to mitigate the risk of personal service account closures and disruptions.
In the article it describes reverting the state of the component if the action fails, asynchronously. IMO that’s much worse than briefly representing a progress state for a few ms.
Did I misunderstand?
Now they shouldn't, but people jumping on JS often spin their wheels until they get pointed to a boilerplate project. It doesn't make for a fair comparison, but it doesn't matter.
Now they're trying to wrap their heads around six major libs with loosely overlapping concepts, four build and orchestration tools, and ten-plus scattered files... for "hello world." Then comes the generally miserable process of figuring out how to put it online.
Throughout this process the reference material is all at least three weeks old, making it hopelessly out-of-date.
I mean, this stuff is often referred to (even here) as a kind of dumpster fire. I can't imagine what a truly new person would think. So while I'm not starting any new PHP projects these days, it isn't hard to see the general appeal.
But on the other hand, I was warned that gum disease will be my nemesis.
For loops I'll create a collection of items in a function (usually done with map against a prop collection) and drop that variable in my JSX.
Basically the same for conditionals. If I want a thing, a var gets a component assigned. Otherwise it's null.
Are these bad patterns, as is?