Jeremiah Senkpiel
Jeremiah Senkpiel
I just want to note that native promises are still _super_ slow.
@dougwilson should we target this for 4.x deprecation? Tbh I can't even find app.render in the codebase..
~~Github search keeps becoming worse and worse. -_-~~ Actually I tried to search this via in-browser find. weird.
Makes people aware of things that will be removed, and I wouldn't say this is the recommended method to use. (just render it from your template engine imo)
make app.render a proxy to app._render, call app._render from res.render? > while still letting res.render work with people overriding app.render (backwards-compatibility). oops, nevermind.
I thought it would only use deflate as a last resort and when the client accepted it?
@gfemec can you provide details on the browser setup that causes this?
Isn't the use case here to avoid doing shader source compiles at runtime and to instead just turn it all into SPIR-V at build time?
It's always nice to have more options, but wouldn't SMAA (Subpixel Morphological AA) be preferred to TAA or FXAA in most situations? Usually when I play games I just turn...
I think a PrintTable function would be necessary. If we were to, Node.js would probably print an ASCII table I imagine, which would necessitate having tabling logic... somewhere. We *could*...