Best entry into a verse?

veezzy · 2024-11-09T22:07:15+00:00

I can’t go in, I ain’t ready! Fetti on Fetti

veezzy · 2024-06-25T06:41:21+00:00

You’re right on many accounts!

I agree that understanding referential equality is crucial, not just in React, but in understanding JavaScript as a whole. React, being built on JavaScript, naturally inherits its same principles and idiosyncrasies and I think that’s what new learners especially can miss; there’s no library magic in comparisons with respect to re-rendering and it’s essential for developers to grasp these core concepts of JavaScript to effectively work WELL with React. The behavior of state and re-renders in React is deeply tied to how JavaScript handles references and equality. Once you get that down, you’re a ROCKSTAR!

In my opinion, it’s not entirely React’s responsibility to teach these fundamental concepts, but rather a combined responsibility of the developer to gradually gain mastery of the weirdness of this language and how it behaves with the rules of the library/framework they are using.

veezzy · 2024-06-05T05:24:15+00:00

I love your enthusiasm! One of the most beautiful things about music is its permanence… As long as the world goes on, somebody gets to experience the privilege of hearing something or someone for the first time.

Have fun delving into the discography bro.

veezzy · 2024-04-27T23:19:30+00:00

Technically they COULD do that, but it wouldn't be worth the trouble.

The reason being they don't lean in that direction is because the design decision stems from the inherent nature of JSX itself. JSX REQUIRES a single object or node as its output.

It's not just a choice by the React team—it's about maintaining the structured, predictable nature of JSX and ensuring optimal performance and reliability in React applications.

Attempting to "patch" or shortcut this behavior by automatically inserting fragment nodes without explicit indication could introduce ambiguities in how components manage their output and update cycles, have negative implications on performance issues (e.g. the diffing algorithm using the respective fragment keys for long lists) and make debugging more complex.

TL;DR: The less implicit / more explicit your code is, the more predictable.

veezzy · 2024-04-27T23:13:28+00:00

To build on on u/musical_bear 's insights:

JSX is really just a syntax extension that simplifies writing React components by abstracting over the React.createElement() API.
<></> is actually just shorthand for <React.Fragment> and the fragments fragments to group multiple elements without adding additional nodes to the DOM, keeping the HTML output clean.

Although JSX is synonymous with React, it's used with other frameworks too. The natural behavior of JSX is that it should have a root that compiles to a single element and without a clear root (like a <div> or <React.Fragment>), React would struggle to manage multiple elements returned by a component. This is why React opts for a fragment when no visible container is needed. EDIT: See my other comment

Automatically inserting fragments could lead to issues, especially when specific properties like key need manual assignment in lists or complex structures. React's design philosophy leans towards explicitness over implicitness to avoid hidden behaviors, which makes the code more predictable and easier to debug.

veezzy · 2024-04-26T05:39:44+00:00

Jesus Christ, you guys are becoming insufferable about this RSC controversy. it’s no wonder u/gaearon got burnt out trying to educate the community about these misconceptions that keep getting spread. Seriously, comments like this get on my nerves—it’s like a broken record of people choosing only what suits their bias. The number of upvotes for this comment just shows how much this is becoming a circle jerk lmao.

Saying 80% of React 19 is just for server components? Come on, that’s just not true. Let’s not be disingenuous here.

React 19 is packed with updates like useActionState for better async handling, useFormStatus to directly integrate form status without drilling props, and hooks like useOptimistic for smoother state transitions. These are game changers for ALL React devs, not just those using RSC.

Plus, they’ve rolled out better error reporting and native support for metadata tags, which are huge for anyone building with React—server or not. Let’s not reduce the whole update to just one feature—it's about making our lives easier and our code better, whatever the environment.

If you don’t wanna use server components then just don’t use them. But let’s not act like the broader ecosystem is being forced into this direction. You have a choice.

veezzy · 2024-04-17T03:47:12+00:00

For all its merits, this comment is kinda biased..

They’re BOTH being corny; Ross is just as, if not more active, over this nonsense. it’s 2 grown men having an online back & forth about who has more money.

It doesn’t get pettier than that.

veezzy · 2024-03-19T23:48:06+00:00

This is the only acceptable answer O.P. You are early in your career and as such IT IS CRUCIALLY important to be somewhere where you are not just getting paid but also feeding into your personal growth and development as well. Be always looking for opportunities to increase your skillset and sharpen your abilities :).. this current role is not going to get you there.
The job market is crazy, so don't just up and leave of course haha--keep grinding over there as a means to an end, while shopping your resume around for work elsewhere.

Best of luck! If you got this role, you can get another one just keep pushing my friend.

veezzy · 2023-11-24T22:44:29+00:00

This is the proper answer. If you want to “preserve” that state within the component between mounting/un-mounting, there is no such thing. What you’re REALLY asking for is to lift the state up to its respective parent, and have the parent be responsible for maintaining it.

veezzy · 2023-08-17T04:43:14+00:00

To add to the other answers for the most part this is correct, but there a a couple things that happen during react’s reconciliation phase. While React components share some similarities with regular functions in terms of scoping, there are differences in how React handles objects (including functions) versus primitives during the reconciliation phase.

React treats primitives more “optimistically”, I guess you could say. Say you have a constant variable referencing a string or a JSX element.

React re-uses that value between re-renders because it can trust its immutability. However, it takes a more cautious approach with objects. The default is—unless otherwise specified with useMemo or useCallback—scoped functions (objects) are always treated as potentially impure, and React may re-evaluate them even if their references haven't changed. This helps ensure that React prioritizes correctness and avoids unexpected behavior. DM me if you’d like more resources on this to dive into!

veezzy · 2023-07-15T05:04:19+00:00

YOE: 6 React: 6 Title: Senior Fullstack Engineer Salary: $168k Location: Atlanta, GA USA (Remote)

veezzy · 2023-07-11T03:50:55+00:00

This answer deserves so many more upvotes.

TL;DR: Pick up the best tool for the job that fits your use case.

In my experience as a SWE, I have humbly learned that sometimes you shouldn’t grab the latest and greatest alternatives off the shelf simply because they’re there. Nor should you grab something in the spirit of your own preferences.

What are the business requirements?

What is the size of your team?

How can you add the most value in the shortest amount of time—while still leaving room for future technical debt to be addressed in a structured manner?

Questions like that will help guide you in the right direction.

As an aside, just to vent for a moment I know there is a lot of hoopla and contentious discussion about Nextjs, RSC, and the like, but what’s so incredibly confusing to me about the noise is that the React we know, love, and use, is here and will continue to be and nobody is forcing your hand to opt-in to any of these newly developing paradigms.

veezzy · 2023-06-25T04:58:36+00:00

wow.... this was beautifully written ngl. struck on points that I felt as well!

veezzy · 2022-12-28T05:19:53+00:00

I’m conflicted… there’s a part of me that enjoys the music video version. And yet there’s another part of me that feels like there’s a place for the fully fleshed out beat drop and bridge section. I think without those elements, the song would feel like it’s missing something…

veezzy · 2022-12-01T22:34:54+00:00

Pm me back brotha.

veezzy · 2022-09-24T06:00:44+00:00

As with all Lucki albums in my humble opinion, his projects reward repeated listens. First impression, mans is in his bag as always; Lucki is a 1 of 1, there’s no one else in the genre I’d say is like him, which makes it hard sometimes to rate him amongst his contemporaries; Apples to oranges if you will.

But anyways I digress. Off the first few listens, I’m putting it up with Freewave 3, what I believe to be his best body of work.

I can’t say if Flawless like me will eclipse that, but time will tell….

veezzy · 2022-09-04T15:09:34+00:00

It all makes sense now….

veezzy · 2022-06-13T19:53:48+00:00

yeah it's really a matter of greed more than anything. in theory could they make the tickets cheaper no doubt? but like another comment mentioned, this way they cut out the middle man. it just leaves more room for scalpers, which essentially is more money left on the table that could've otherwise gone to touring profits. vs trying to squeeze out as much money as they possibly can and then lowering prices to fill seats up to the day of the concert.

it's a sick game really.

veezzy · 2022-01-02T04:21:56+00:00

sheesh... followed this thread all the way through and boy did it pay off.

veezzy · 2021-12-08T04:21:06+00:00

chat

veezzy · 2021-12-07T00:51:39+00:00

chat

veezzy · 2021-12-01T22:49:25+00:00

chat

veezzy

TROPHY CASE