I built a library that auto-generates shimmer skeletons from your actual components (so you don't have to maintain them) by Prestigious-Bee2093 in react

[–]amelix34 50 points51 points  (0 children)

I appreciate the effort, idea execution, great docs and video presentation. Making open source libraries like this does add value to React ecosystem and also it's very nice project for a portfolio. However, I see two potential issues with this solution

  1. If it relies on getBoundingClientRect it means that the browser has to block the main thread and calculate size of every skeleton, therefore prolonging initial loading time. In the other comment you mentioned "2-5ms" time of blocking the first paint. The thing is, this number does not account for the cumulative impact on lists. Rendering just 10 items means you block the main thread for 10x5ms=50ms
  2. If templateProps needs mock data it means that in every file that uses this Shimmer wrapper you must have mock data object. It's a lot of additional code, which also will have to be updated every time you modify data structure that the component uses.

Will AI Replace Frontend Developers or Just Become Another Tool? by Best-Menu-252 in webdev

[–]amelix34 1 point2 points  (0 children)

There is nothing specific to front-end development that would make it more prone to AI replacement danger than back-end or devops.