it seems like a lot of your problem here is being caught off guard that pre-sliced bread, which has been modified so that it does not go stale as it otherwise would, is a processed food. try buying bread from a bakery that goes stale. after recalibrating that expectation maybe this will make more sense overall?
Right. It's like the argument that the 2 party system is an intentional brake on democracy, so we have to legislate reforms into being... with the permission of the 2 party system that determines whether legislation gets passed? The clear logical extension of the argument is that reform on the terms in which we have these problems is ultimately not very workable.
Coding is pretty straightforwardly a craft - something that is done for use value but allows for artistic expression and a convergence of form and function. It isn't art.
However, I disagree that aiming to get enjoyment out of a coding job is necessarily a mistake. But it does often have to be weighed against competing factors like ease of getting a job and pay.
This comment is perfectly alienated from nature. Yes, significant seasonal and regional variation in diet is a worthwhile tradeoff for eating much more nutritious, tastier, cheaper, and more environmentally sustainable food than we have now. No, it does not mean we would have to eat like feudal peasants.
I don't think it makes any sense to try to hold people responsible for keeping the economy running hot as individuals on top of being rational self-interested actors.
why are we operating national, natural monopoly services on a for-profit basis that fundamentally incentivizes this in the first place (rhetorical). Amazon deserves to be taken into democratic public ownership for nominal compensation.
You will be surprised. Do a "Inspect Element" and have fun filtering on "XHR requests". Notice that JSON that a lot of those requests return. but sshhhh, you didn't hear this from me.
With the move to client-side rendering, too many. The backend becomes dumber and dumber and all logic such as filtering data moves to the frontend. You'd be surprised what you can find poking around at APIs that client-side apps use.
The analogy is going up to a house and checking all the doors and windows to see if they are locked. That's rather like port scanning, a form of 'poking'. If you go to a state government web site and do that, even if you don't exfiltrate data or load it up with ransomware, it's definitely very shady behavior, although it seems there are no laws against it in the USA (some ISPs will ban users caught doing this however).
Obviously if you broke into someone's house and then asked them to pay you for your 'vuln discovery', err...
However, I think looking at HTML code on a public facing web page is not that. If you hang naked pictures of yourself on your front door, you don't get to complain when people take pictures of them.
The data was send to my browser. The more fitting analogy to me is that I get a letter and a huge pile of documents in a giant binder. Some of the documents are referenced in the letter. Now the sender gets upset because I started looking at the documents in the binder that weren't referenced in their cover letter.
Last year, when a Nintendo Switch was difficult to come by, I found that a large retailer’s API returned exact stock counts (and even restock dates in some cases) for any physical store you wanted. Got a Switch for myself and a couple friends in an afternoon.
of course, similar things happen pretty much everywhere else, but usually not so egregiously.