bmandale

While a bit annoying, that seems like the optimal solution within the constraints of apple's design culture.

There is an optimization for lists, and maybe that's what GP is remembering. l += is functionally different from l = l +. The former mutates l, whereas the latter creates a new l. The difference matters when the line above is m = l. The mutation version will mutate m as well (they're the same reference), the creates new version will not. This optimization can just as easily turn into a footgun if the programmer is unaware of it, and in that sense is unpythonic.

The fact is that there are no synergies for many companies, even companies operating in the same industry. The reason for promoting a merger between such companies is exactly that they will see reduced competition and hence greater profitability. The ideal merger is actually between companies making different products, where the one company can benefit from more vertical integration.

A reframing that would have the power to lower collisions between cars and bikes would be to blame the road design, or even the car design. These are things that can be easily changed for a large number of people if enough political will exists.

...which in turn was caused by bad design of github's CI pipeline. Funny how it all comes back around like that.

> The string may begin with an arbitrary amount of whitespace (as determined by isspace(3))

Second is that it only applies to signed long long, not unsigned.

market power

>What is stopping everyone else from doing the same?

see above

Python banned this in python3. Problem solved.

After python, it seems like every language decided that making parsing depend on indents was a bad idea. A shame, because humans pretty much only go by indents. An example I've frequently run into is where I forget a closing curly brace. The error is reported at the end of the file, and gives me no advice on where to go looking for the typo. The location should be obvious, as it's at exactly the point where the indentation stops matching the braces. But the parser doesn't look at indents at all, so it can't tell me that.

  $ base64 -d <<< SW50ZXJlc3RpbmchIFBsZWFzZSB0ZWxsIHVzIG1vcmUh
  Interesting! Please tell us more!

the title is referring to inside html attributes, where they will be removed hence not affect where the link points.