I’ve always been of the opinion that language choice is supremely unimportant - but in this case you’d probably want to check for good libraries that may be available (so probably python).
However, I’d also point you towards the creator code bullet since they’re always doing wacky AI shit and demonstrate the approachability of building such a system.
If a function is declared but not implemented it’ll usually cause a linking error… And sometimes (with older compilers) a runtime error.
The standard here is that the declaration (1) would be in a .h file that other .c files might reference while the implementation (2) would be in a .c so it is only built once into a .o file during compilation & linking.
Just my opinion here but using a signed JWT instead of a server local variable seems needlessly risky for communicating a price. Considering the potential liability to the company if your signing token is compromised I’d much rather send the prices to the user and keep a server local copy tied to the account/session/auth token. When the user tries to confirm the price we’d just pull the information from local storage.
In terms of your primary question though… I can see the UX advantage of honoring the expired token if prices were stable but I’d probably roll out an MVP without that feature fully developed but with some logging to flag how often it’d activate - throw the statistics at business people and let them ponder how often it’d activate.
That all said, this is an API not a GUI so I really don’t care as much about the UX since the consumer can just automate resubmitting for a new token - especially if we’re putting together an SDK or code samples for clients to run the requests and double especially if we’re controlling both ends with a distributed binary (but that doesn’t sound like the case here).
Same reason why the game I worked on censored users talking about our Assassin boss… especially on a Saturday.
Not necessarily, Leninists and OG Marxists usually don’t get lumped in with Tankies - while Trotskists definitely should be. Tankies accept blatant authoritarianism as an acceptable cost to achieve socialism, non-Tankies reject authoritarian regimes.
… and super-Tankies are Pol Pot apologists.
And this is why PHP is actually an awesome language.