, and we burned it at the stake.
Gotta love that about FOSS communities. Every time someone tries to do something interesting, we burn them at the stake. It's a classic of the Mozilla fandom, for example.
I feel that would be incredibly wasteful (and a browsing session can be several windows, too) for marginal zero or even negative net gain. Browsing would also need to set isolation profiles, because for some tabs, sites or windows you'd certainly want to have access to your localtime (plus it be precise enough). Ditto for each and every potential variable.
The truth is, not everything needs to be containerized.
local machine time
local machine ram
I'd venture the only way to block those is to either recompile the browser or somehow use a separate Javascript engine that doesn't provide that info, as it's pretty foundational (as some people mention, localtime is accessible simply by constructing a Date object).
That
if constexpr
in the case you mention does make the constructor clean as heck. Thanks for the clarification and the commits, by the way!