Wonder why. We’ve got thousands of conditionally rendered components on a pretty interactive scheduling screen. One click can affect all of them but everything feels instantaneous.
Our bottleneck was that we have so much data, making it all observable up front led to slow initial load times and high memory usage. We now make things observable on demand which has eliminated a lot of that.
I don't find these kinds of what-ifs very useful. I haven't used Rails, but does it somehow prevent you from accepting user input and programming it to go where you say you want it to go? Isn't there an element of "holding it wrong" with any language or framework?
I've had several of our users call up over the years, angrily asking why we made certain fields in our app "dropdowns" with rubbish in them.
Chrome decided to add autocomplete to some of our fields with contextually irrelevant options. As far as I know there isn't anything I can reliably do about it.
I too can't shake the feeling that hooks are off. I like JSX and the component model.
In React and like-minded projects, I look at a stack trace and see that it starts at some kind of batch renderer. I can't tell "why", "how" or sometimes even "what" broke. The input part of it is completely lost.
I work on a Backbone application where stack traces are much more obvious. They usually tell you the whole story. I find that juniors who were mostly exposed to React have a tendency to completely ignore stack traces, and am now wondering if they are just conditioned to them being unhelpful.
I do appreciate those rules because they lead to a higher quality listing.
I had a bugfix update rejected a little while ago for a business app.
Apple wanted a video walkthrough of every screen in the app, explaining what each screen is for and with a breakdown of device permissions needed on each of those screens. That day was a complete write-off. If the app required excessive permissions I could understand there might be some concern, but it doesn't. Any permissions we do need are justified in the info.plist as required, and are very descriptive.
They then rejected it again the next day, as I had apparently failed to mention what we use ARKit for in the video. We don't use ARKit and it is not in the codebase.
Another day goes by and they finally approve, with a friendly disclaimer that they will now require an updated video with every future update.
I listen to a few infosec podcasts when I'm out and about, and Spotify frequently forgets how far into an episode I am, or it just randomly jumps back half an hour. Only when I realise things sounds oddly familiar do I notice it happened yet again.
I cross a particularly busy intersection here in Melbourne as a pedestrian every day.
At least once a week I see people who are too busy playing with their phones to realise all the cars in front of them had already driven off, the traffic light was now red again, and pedestrians were about to start crossing. The sudden realisation then makes them slam the accelerator without checking their surroundings first.
At the same intersection I witnessed an accident where the first driver in line was playing with their phone, got spooked by someone honking, and ran the red light straight into traffic.
It's like they're tricking themselves into thinking they're paying enough attention.
I’ve noticed that many light themes use relatively bright colours for text, and I’m finding them increasingly difficult to read.
The orange used in the explorer view is just bright enough to become slightly blurry to me, causing me to squint.
I may not have that issue if you use the same orange found in the syntax highlighting, which seems slightly darker to me.