Chung Wei
@chungweileong.bsky.social
I think probably the safest way (might degrade the UX tho), is to show the release link instead of copy the actual content?
August 21, 2025 at 2:47 PM
I think probably the safest way (might degrade the UX tho), is to show the release link instead of copy the actual content?
No worries, just trying to get things resolved before it reaches to more people.
This is the first time I heard of renovatebot actually.
This is the first time I heard of renovatebot actually.
August 21, 2025 at 2:27 PM
No worries, just trying to get things resolved before it reaches to more people.
This is the first time I heard of renovatebot actually.
This is the first time I heard of renovatebot actually.
My current issue with Safari is that it’s using more memory than I expected, like at least x2,x3 times more than Chromium browsers, it happens on almost every sites.
February 22, 2025 at 4:52 AM
My current issue with Safari is that it’s using more memory than I expected, like at least x2,x3 times more than Chromium browsers, it happens on almost every sites.
Right now I really wish that Safari focus on reducing memory usage tho, like I can hit 1GB memory on nearly every sites.
February 16, 2025 at 10:42 AM
Right now I really wish that Safari focus on reducing memory usage tho, like I can hit 1GB memory on nearly every sites.
Yeah I know, but based my observation so far, it happens in quite a lot of sites like Jira & AWS, where leaving the site sitting without doing anything almost aways cause it to build up the memory to 1GB+
February 14, 2025 at 11:09 AM
Yeah I know, but based my observation so far, it happens in quite a lot of sites like Jira & AWS, where leaving the site sitting without doing anything almost aways cause it to build up the memory to 1GB+
Yes. I literally have to switch to chromium browser today. Safari seems to have memory leaking issue lately where watching a couple of YouTube videos in a row can build up the memory usage like crazy.
February 14, 2025 at 9:48 AM
Yes. I literally have to switch to chromium browser today. Safari seems to have memory leaking issue lately where watching a couple of YouTube videos in a row can build up the memory usage like crazy.
Yeah, I found it annoying, especially when I have to explain to a beginner why it's being logged to the client.
December 8, 2024 at 5:24 AM
Yeah, I found it annoying, especially when I have to explain to a beginner why it's being logged to the client.
Can probably try @socket.dev, at least it’s better IMO.
December 4, 2024 at 1:33 PM
Can probably try @socket.dev, at least it’s better IMO.
It kinda depends on the React setup, with framework like Next.js, we usually initialize the i18n on server-side globally, then pull parts of the i18n and serve it to React components.
November 23, 2024 at 9:54 AM
It kinda depends on the React setup, with framework like Next.js, we usually initialize the i18n on server-side globally, then pull parts of the i18n and serve it to React components.
I mean you usually want to do it on request basis. In fact what the i18n initialization does is retrieve corresponding i18n JSONs and hand it off to client side, after that the memory should be released by GC.
November 23, 2024 at 9:41 AM
I mean you usually want to do it on request basis. In fact what the i18n initialization does is retrieve corresponding i18n JSONs and hand it off to client side, after that the memory should be released by GC.
Most cases like initializing something, you can actually do it outside of React component.
November 23, 2024 at 9:01 AM
Most cases like initializing something, you can actually do it outside of React component.
Yeah, it basically allows you to sync between react state or external state, aka non-react state.
November 23, 2024 at 6:18 AM
Yeah, it basically allows you to sync between react state or external state, aka non-react state.
useEffect() is indeed triggered onMounted, but we shouldn’t use it to do things onMounted. Basically it’s not a place for you to write onMounted code.
tkdodo.eu/blog/avoidin...
tkdodo.eu/blog/avoidin...
Avoiding useEffect with callback refs
Interacting with DOM nodes doesn't necessarily need useEffect
tkdodo.eu
November 23, 2024 at 4:39 AM
useEffect() is indeed triggered onMounted, but we shouldn’t use it to do things onMounted. Basically it’s not a place for you to write onMounted code.
tkdodo.eu/blog/avoidin...
tkdodo.eu/blog/avoidin...
Nice, I’m actually like it a lot this way
November 21, 2024 at 12:13 PM
Nice, I’m actually like it a lot this way
Been using it for months, it’s actually not that bad for dev, unless you really need those DevTools that chrome(or chrome extension) provides. It’s getting way better compared to years ago.
November 15, 2024 at 11:15 AM
Been using it for months, it’s actually not that bad for dev, unless you really need those DevTools that chrome(or chrome extension) provides. It’s getting way better compared to years ago.
Now that you mentioned, I can no longer unsee that🙃
November 8, 2024 at 12:56 AM
Now that you mentioned, I can no longer unsee that🙃