What laptops have that without having a number pad as well? I know my macbook doesn’t have a better hone/end/pgup/pgdn. I personally hate laptops with number pads because the keyboard is then off center, so I just accept this sacrifice on laptops.
I do really wish they had macbook-like arrow keys, which are very effective for touch typing since the half-size makes them easy to feel.
The last dell (xps 13 2-in-1 from about 2 years ago) I bought has page up and down above left and right (half-size keys, like the macbook, but the gaps filled in), and home/end above in the f-key row. It's not my ideal but it's good enough.
My old Acer C710 and my X1 Carbon also have dedicated pgup/pgdn/home/end keys in those locations. As soon as framework comes out with such a layout I'll buy a new panel.
All ThinkPads up to T420/X220 (2011) have a proper delete/home/end/pgup/pgdown block at the top right. And then the 2017 ThinkPad 25 anniversary edition, which is what I'm using right now and hoping it lasts until there is a proper replacement on the market.
My ThinkPad X1 has no number pad, and puts pgup/pgdn on either side of the up-arrow key, which works quite nicely for me. I picked that laptop specifically for the keyboard.
"USB 3" is also ambiguous as hell. It's unfortunately talking about one of perhaps 10 different protocols, some of which are different depending on what year you are speaking of, because there's name collisions between incompatible versions.
"-o" is mostly "--remove-assertions" already, so that wouldn't help.
While today's use case for assert is unit testing, the actual killer feature of the keyword is that it's removed only from prod.
The idea is that you can write things like function contracts, that are expensive, but only exist in dev.
Now, if one of you dependencies use assert for something they expect to still be in prod, which is the problem we are talking about in the first place, "-o" or "--remove-assertions" will strip their assert too, breaking their code, and hence, yours since it depends on it.
Before this thread i had no idea assert was debug only in python.
Another solution would be to accept the current role of assert as quick error checking and add in debug_assert to indicate a conditional error check. The biggest issue with that approach is that a majority will suddenly ask "Wait, python has a debug mode?"
I still do not understand what the problem is and what users need to know. So assert throws and exception in debug mode and is 'commented out' in production, right?
So the problem is some vendors ship libs that have failing asserts so cannot run in debug mode?
What legal repercussion could Facebook possibly have in such a case? Since when could one party sue another party for using browser automation on their website?
Not anecdotal: By nature of the structural relations of our society, the richest people are exploiting the labor of the poorest people, which leaves little reason for the poor people to coopperate.
What is the fix if employers ('the rich') are to employ and not exploit? For cases in the news like Amazon drivers etc it is clear but many people just want jobs and do not feel exploited even though their boss is making a killing?
Objectively not wrong, but self-evidently relative. Of course, if you somehow believe an entire society of exploiters is coherent, then maybe it seems rational to think hard work can infinitely “pay off.” But if you account for the need of exploiters to have somebody to exploit, then the idea doesn’t seem so sound.
