The curse of being a browser developer and knowing about rendering performance, memory usage, etc. is that you are guaranteed to be the one person nobody ever listens to about these topics.
-
-
I actually have the opposite feeling from #2: browser developers optimize too well, which has allowed web apps to grow their memory usage without bound.
-
I have similar feelings re. React.
- 1 more reply
New conversation -
-
-
We fixed the memory leak about ten separate times while I was at Moz.
-
Not just fixed The Leak but even better: negative leaks!https://mobile.twitter.com/amccreight/status/1100530694566998016 …
End of conversation
New conversation -
-
-
Another fun one I see sometimes when they have a positive feeling about their browser is that it is using a lot of memory in a deliberate fashion to maximize performance.
-
We preallocate lots of malloc memory to implement our fast arena allocators on top of it. Does that count?
- 1 more reply
New conversation -
-
-
2 happened this week. Someone filled a bug against the GC because slack uses too much memory.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
The funny thing here is that you basically expressed a less mean variant of 2 when you were starting to work on Servo. Some lessons can only be learned the hard way.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
3 doesn't seem too far off. One example is all the extra work we do in Gecko to get CSS animations and transitions to layer correctly--something none of the other engines do and which Emilio is always itching to drop.
-
Does that actually make it slow or just add a lot of code complexity?
- 1 more reply
New conversation -
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.