I modified Firefox's memory allocator to improve responsiveness on macOS
1–7 of 7 posts
Re: I modified Firefox's memory allocator to improve responsiveness on macOS
#2Short: Using an undocumented API on OSX >10.14 resulted in higher performance and lower battery usage.
Maybe Apple should consider making that API official?
Re: I modified Firefox's memory allocator to improve responsiveness on macOS
#3As informative as this is, what is with the tendency to use Twitter where a blog posting would be more appropriate? Reading this with the character limit break cadence and understanding.
Re: I modified Firefox's memory allocator to improve responsiveness on macOS
#4[deleted]
Re: I modified Firefox's memory allocator to improve responsiveness on macOS
#5As informative as this is, what is with the tendency to use Twitter where a blog posting would be more appropriate? Reading this with the character limit break cadence and understanding.
No post body was provided.
Re: I modified Firefox's memory allocator to improve responsiveness on macOS
#6As informative as this is, what is with the tendency to use Twitter where a blog posting would be more appropriate? Reading this with the character limit break cadence and understanding.
Guessing the idea is to expand viewership of the content. Easier for people to share content and stumble upon it when it’s hosted on Twitter versus a blog.
Re: I modified Firefox's memory allocator to improve responsiveness on macOS
#7As informative as this is, what is with the tendency to use Twitter where a blog posting would be more appropriate? Reading this with the character limit break cadence and understanding.
1. Because the Author doesn't have blog
2. Setting up a blog is hard, so much hassle along with maintenance.
3. Writing it on Twitter, especially when you are already on Twitter, has the lowest friction.