I’m a believer in “if your infrastructure isn’t working, plan A should be to improve your infrastructure; elaborate workarounds should only be a plan B”.
-
-
It’s also how I think about the Web graphics stack. I’m not a fan of the status quo of using a “compositor” to work around a subset of 2D graphics performance problems. The WebRender approach is to fix the entire stack instead.
Show this thread -
And I think of GC the same way. I’m skeptical of attempts to carve out GC-free subsets of languages, heavy reliance on escape analysis, etc. Improve your GC first before working around it.
Show this thread
End of conversation
New conversation -
-
-
Unfortunately, some of us can't vendor our dependencies like that, and have to support years-old versions of them, so there's not much incentive to invest in upstream fixes when you're going to have to do workarounds anyway.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.