However my recent years have been in Python, which perhaps is high level enough to require a large amount of code writing. Maybe in C++ it's a bigger gain?
13,916 karma · joined May 12, 2014
However my recent years have been in Python, which perhaps is high level enough to require a large amount of code writing. Maybe in C++ it's a bigger gain?
> In another comment, I asked why people chose to use the symbol τ over just writing turn or "rev(olution)" (defined to be the constant ≈ 6.28318530718) given how unambiguous the latter is as a name for 2π. And why not just write sinrev() or sinturn(), and leave the symbols sin() and rev (defined to be ≈ 6.28318530718) alone?
You were asking why they used the symbol τ rather than the words "rev" or "turn". You didn't give a clue that you knew any of the rest, including what the symbol meant.
I suppose many people would wonder what the difference is between a legitimate caller you don't want and a fake one.
Your prior claim was that they only solve one problem, not about a definition. They solve several problems:
- less data can move over the wire compared to sending a full page every time (this is in your definition, and is definitely not always true, as sometimes REST APIs can return far more data than what's needed to render the screen)
- the same REST/data API can serve your website and other consumers, e.g. any native mobile apps or third party API consumers
- you can write tests for your frontend, e.g. you can unit test components' behaviour and style in isolation
- the frontend can also work, or at least respond usefully to the user, when the network or the backend are not working
Would a better example be Python's inline if else construction?
x = 3 if thing else 4This is astonishing. Is anyone else surprised at this dead code figure? Is it a feature of large projects I've just never noticed?
Yes - the kerfuffle is broadly I think the fact that it negates the main advantage of passkeys: people can't be tricked into pasting them into a fake login screen.
> It's an impossible design. It's all just obfuscation, most of which is confusing to users.
I agree - they're explained in a really odd way, and I think that's because they're a technology with multiple interaction patterns, rather than a single thing like a password. E.g. your fingerprint on your Mac is implemented as a passkey, or clicking on a browser passkey is also a passkey, or using a password manager via a different UI is also a passkey, or touching a Yubikey is also a passkey. The underlying mechanism (passkey) probably has been surfaced more than it should've been.
The main feature of passkeys is that they can't be pasted into a website they shouldn't be pasted in to. That means you can't copy them, by design.
1. They are testing what the market will bear. Ubisoft's silly "quadruple-A game" rhetoric and executives saying "people will have to get used to $100 games" is them testing the water. This should pull back, as most people don't want games that cost that much, unless they're really amazing. They aren't (currently). I imagine this same thinking is going on in hardware-land.
2. Current RAM/GFx card prices are driving up prices all round. It should still be true that for the same spec, console components should get cheaper over time, but I can imagine it's less of an effect at the moment with all the AI data centres hoovering up manufacturing capacity.
I don't understand why you don't like them, because you haven't said!
3D-Secure long predates apps, including in the UK. I had to work on a Government Gateway integration for local council payments in the mid 2000s that included 3D-Secure. I still see it today, although it normally now results in a ping to an app approval.