This still doesn't fix the biggest issue with running non-javascript code in the browser: browsers still offer no way to know when a valu...
This still doesn't fix the biggest issue with running non-javascript code in the browser: browsers still offer no way to know when a value is collected. e.g. if I allocate a callback function, and hand it to setTimeout, I have no way to know when to collect it. Sure, you can encode rules about some of the common functions; but as soon as you get to e.g. attaching an 'onreadystatechange' to an XHR: you can't follow all the different code paths. Every time a proposal comes up to fix this: - GC callbacks - Weak valued maps - Proxy with collection trap The proposal gets squashed. Unless this is attended to Javascript remains the required language on the web.
Posted by daurnimator on Jun 17, 2015, 11:46 PM
Tags
Related issues
- The biggest problem with having an LLM do this, from what I've observed of at least frontier models, is that the way they are trained...
- The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
- (My comment is about detached houses).
- The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
- > steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
- Why is there no comparison with FLUX 3 Image?
Raise real-world problems, find people facing the same issue, and discuss solutions.6,000 issues0 comments
hackernews (Other)
The biggest problem with having an LLM do this, from what I've observed of at least frontier models, is that the way they are trained...
The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
(My comment is about detached houses).
The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
> steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
Why is there no comparison with FLUX 3 Image?
> our Git monorepo was developing an annoying problem Sentences like this are so common from people using monorepos that I am convinced ...
Why is there no contact form?
This still doesn't fix the biggest issue with running non-javascript code in the browser: browsers still offer no way to know when a valu...
This still doesn't fix the biggest issue with running non-javascript code in the browser: browsers still offer no way to know when a value is collected. e.g. if I allocate a callback function, and hand it to setTimeout, I have no way to know when to collect it. Sure, you can encode rules about some of the common functions; but as soon as you get to e.g. attaching an 'onreadystatechange' to an XHR: you can't follow all the different code paths. Every time a proposal comes up to fix this: - GC callbacks - Weak valued maps - Proxy with collection trap The proposal gets squashed. Unless this is attended to Javascript remains the required language on the web.
Comments (0)
No comments yet. Start the discussion.