Frontend developer in Web3 π¨π»βπ» | Sharing content about building the frontend for decentralized applications π | Digital nomad π | @developer_dao member π§±
I have always been very interested in @LensProtocol but I have never really worked with it.
Time to change that πͺπ»
Planning to build a Lens-powered project and create a tutorial out of it to share my learnings βπ»
I am really happy about the shift towards unstyled components in the frontend dev space. Component libs like Bootstrap or MUI provide good accessibility but customizing them can be a pain in the ***. With unstyled components you get both, great accessibility & customizability πͺπ»
@shikkhar_ I heard recently that the shower is the only place where we tend to not be distracted and come up with great ideas because we can't bring our phones into the shower. Every else (e.g. on the toilet) we bring our phones and start scrolling π
@panditdhamdhere@reactjs@nextjs Depends on the problem. Yes, you can use "use client" for components with state etc. but then the component will still be pre-rendered on the server and hydrated on the client which might lead to hydration errors. Pretty confusing IMO that a client component is still pre-rendered
It used to be easy to write @reactjs code. Now with the differentiation between server/client components and the fact that even a client component can be pre-rendered on the server (@nextjs π), I feel like things have gotten way more complex...