Prajwal BM @xshadowdev

@stornity Camera could not capture the real beauty which the eyes saw. It looks more beautiful in real bro. One must definitely visit Himalays in their life.

3 0 2 30 0

View Details

Prajwal BM @xshadowdev

13 hours ago

@Ammindless21 Hampta pass trek, Himachal Pardesh

1 0 1 71 0

View Details

Prajwal BM @xshadowdev

a month ago

@iam_enginner @threejs @bruno_simon @threejsJourney yen guru, becoming a game developer developer day by day?

1 0 1 85 0

View Details

Prajwal BM @xshadowdev

2 months ago

@iam_enginner @threejs @bruno_simon Insane

1 0 1 35 0

View Details

Prajwal BM @xshadowdev

3 months ago

@iam_enginner @threejs @threejsJourney it reminds me of a game in android, i dont remember the name.

1 0 1 82 0

View Details

Small update: Updated the UI and added a feature to change the display name, and also learnt a concept called Stale Closure, read till the end to learn about it. - Today I coded with no internet, which made me give more time to think what logic am I writing and what the bug is happening, and how do I solve it. - Added a feature where the peer can change their name which will instantly update on every connected peer by updating it through websocket. Concept: Stale closure - occurs when a function captures an outdated variable from an old scope, failing to see updated values function Counter() { const [count, setCount] = React.useState(0); useEffect(() => { setInterval(() => { console.log("Count:", count); }, 2000); }, []); return ( ); } now you expect the count to go as 0,1,2,3,4,5 as you click. but it wont instead it will be 0,0,0,0 for ever, but why? when the component first renders, react runs the effect and the setinterval is created, but the funtion captures count as 0, even when react updatesthe state the internal callback still sees the initial value. replay with the solution. - I was using a zustand state variable inside a useeffect which ran on first component mount, now every time i used the variable inside the effect it was null, but zustand has a better way to solve it by using store.getState() as zustand store is not tied to react and can be accessed anywhere.

Prajwal BM @xshadowdev

3 months ago

DAY 2: worked on the client side ws connection. - I used to write inline code where I put the logic of ws connection in the useeffct and make a connection, but this had some downsides like ws instance being created on each rerender. - So I learnt and used a different code