4 ms·

This does not remotely belong in a HTTP header. DevTools, CI is more like it. In any case, it is impossible to prove that your JS code will not somehow exceed

This does not remotely belong in a HTTP header. DevTools, CI is more like it. In any case, it is impossible to prove that your JS code will not somehow exceed these limits on a rarely exercised execution path. So I recommend turning this on in production as soon as the halting problem is solved.

duskwuff 7y ago
Yeah, I have a hard time seeing what value this feature directly provides to the end user. The changes that a web site would have to make to make it work are all well and good -- but those changes are just as valuable if never-slow mode isn't enabled. The only effect that turning this flag on has is to make the web site malfunction if it tries to do something "slow"!
- tantalor 7y ago
  Performance is a feature; would you rather your site break or just look bad?
  - duskwuff 7y ago
    Both as a user and as a site operator, I would much rather have a site perform poorly than have it fail to work at all.
hermanradtke 7y ago
Isn’t it also impossible to prove that your code won’t violate CSP on a rarely exercised execution org?
- tedunangst 7y ago
  The consequences of CSP violations vs accidentally loading a 1.01 MB image differ.
- paulddraper 7y ago
  CSP had the report-uri that helps mitigate....and it's pretty clear how something violates CSP.
  - hermanradtke 7y ago
    I am pretty sure I saw the same reporting behavior with this idea.
deleted 7y ago
[deleted]
deleted 7y ago
[deleted]
adrianN 7y ago
People write hard and soft real time systems all the time without solving the halting problem in general.
- stefan_ 7y ago
  Of course, by careful engineering and restrictions (e.g. straight up no dynamic memory allocation). On systems where you can understand and measure the entire execution path from electrical trigger to response. And in any case, they don't wire in blow-up switches when the timing fails. On the other hand, we have the modern frontend project with its 300 nodes in the dependency tree, of which a handful are written by whoever will be turning this on. Are you sure your i18n library isn't lazy-loading translations and you blow the budget once someone selects not-English?
sagebird 7y ago
Perhaps the halting problem being solved would imply that a time machine, if possible, would be solved as well? EG.. Imagine a program that halts if a program that iterates over every possible combination of a machines includes a time machine. Then devise a program that halts if the first step of building a time machine is to get a thimble, etc. Do some sort of binary search over the steps of building a time machine by constructing halting problems. What I'm getting at is that if the halting problem was solvable perhaps someone would travel back in time and tell us the solution to the halting problem. Or perhaps they wouldn't, but I wonder if they could.

duskwuff 7y ago

Yeah, I have a hard time seeing what value this feature directly provides to the end user. The changes that a web site would have to make to make it work are all well and good -- but those changes are just as valuable if never-slow mode isn't enabled. The only effect that turning this flag on has is to make the web site malfunction if it tries to do something "slow"!

tantalor 7y ago
Performance is a feature; would you rather your site break or just look bad?
- duskwuff 7y ago
  Both as a user and as a site operator, I would much rather have a site perform poorly than have it fail to work at all.

hermanradtke 7y ago

Isn’t it also impossible to prove that your code won’t violate CSP on a rarely exercised execution org?

tedunangst 7y ago
The consequences of CSP violations vs accidentally loading a 1.01 MB image differ.
paulddraper 7y ago
CSP had the report-uri that helps mitigate....and it's pretty clear how something violates CSP.
- hermanradtke 7y ago
  I am pretty sure I saw the same reporting behavior with this idea.

deleted 7y ago

[deleted]

deleted 7y ago

[deleted]

adrianN 7y ago

People write hard and soft real time systems all the time without solving the halting problem in general.

stefan_ 7y ago
Of course, by careful engineering and restrictions (e.g. straight up no dynamic memory allocation). On systems where you can understand and measure the entire execution path from electrical trigger to response. And in any case, they don't wire in blow-up switches when the timing fails. On the other hand, we have the modern frontend project with its 300 nodes in the dependency tree, of which a handful are written by whoever will be turning this on. Are you sure your i18n library isn't lazy-loading translations and you blow the budget once someone selects not-English?

sagebird 7y ago

Perhaps the halting problem being solved would imply that a time machine, if possible, would be solved as well? EG.. Imagine a program that halts if a program that iterates over every possible combination of a machines includes a time machine. Then devise a program that halts if the first step of building a time machine is to get a thimble, etc. Do some sort of binary search over the steps of building a time machine by constructing halting problems. What I'm getting at is that if the halting problem was solvable perhaps someone would travel back in time and tell us the solution to the halting problem. Or perhaps they wouldn't, but I wonder if they could.