As a kid, I had no idea they would someday print books, so each day I cut out the strip from the newspaper and paste it into a book. I’m sure my mom threw it away decades ago, but I wish I still had it.
Maybe if your camera is broken? Or you are using one of those phones built without a camera (like the ones issued to people who work at secure government sites)?
I have the same issue with board gamers. Now, admittedly it isn't as intrusive as audio/video uploads. But so many want to record the game along with the names of the players. When I request they don't use my actual name and just put Player A (or whatever) they look at me like I'm a weirdo. When did it become weird to want as little information about yourself to be online?
I just searched "Firefox" in the app store. The top result is Google Chrome with an Ad indicator (Google paid for higher placement). Second is Firefox.
Is it? CSS Grid and flexbox exist. What I do is design at the smallest screen size first (mobile first), then increase the screen size until it looks bad/breaks, then I set a breakpoint and use CSS to adjust things as needed. Rinse and repeat as many times as needed until it looks good at all screen sizes. It really is not difficult if you know what you are doing.
There is no sign that we will ever send out Von Neumann probes, so why should I believe that any other intelligent civilization will do the same thing.
Or, how do we know they haven’t reached us? Maybe they stayed in the outer solar system. Maybe they came, looked, and left. Maybe they have some sort of cloaking device technology. Maybe they are really small. Maybe they came during the age of dinosaurs and probe is still out there in space, shut down and waiting to be discovered.
No, anything you can do with arrow functions can be done without them. Arrow functions are just a simpler way of writing code. For example, you can control "this" in non-arrow functions using tools like call, apply, and bind. It is just more verbose.
My previous job was a full stack developer, but I had built the entire product from front to back on my own and knew how it all worked. I found it quite easy and even enjoyable. Now I'm working a job that is not full stack and I'm finding it extremely stressful because I didn't build the thing and still haven't figured out how the different parts work, much less work together.
> To successfully use an abstraction, you need to understand the problem the abstraction is trying to solve and also understand how the abstraction has solved the problem.
Not just abstractions, but just about everything we use. For example, why were arrow functions added to JavaScript? After all, everything you can do with arrow functions you could do previously without arrow functions. What was the problem that arrow functions were trying to solve and how do arrow functions solve that problem? I wish MDN was updated so that at the top of every page it first gave an overview of what problem this particular feature solves and how it solves it. Including how the problem used to be solved with "old" syntax and why this new syntax is preferable. And when it is not preferable.