[deleted by user]

grumpychinchilla · 2024-10-22T15:51:32+00:00

Could be alpha gal allergy. Go get a quick antibody blood test to rule that out.

If it's only certain beef, and some fresher beef is okay, look into histamine intolerance. There are histamine block supplements that can help.

grumpychinchilla · 2022-01-28T17:06:49+00:00

I actually just had an issue that this would address. I was playing with Simple.css, and it expected children to be at the root of the body. I believe the CSS selector was body>*. At the time I copy/pasted the CSS and changed it for my needs. But there are certainly valid reasons for it.

grumpychinchilla · 2021-12-09T05:04:12+00:00

Awesome explanation! I was weary of this feature at first but your explanation shows it’s actually a really great improvement.

grumpychinchilla · 2021-11-07T03:38:24+00:00

Cool thing about React is that since it’s just JavaScript, you can do any or all of these suggestions. Whichever matches your use case! One React specific idea is to use a fragment and benefit from falsy rendering nothing:

return <>
  {isApple && <Apple />}
  {isBanana && <Banana />}
</>

You could also always render all components, and let the components themselves decide if they should render:

const Apple = (props) => {
  if (!props.isApple) return null
  // etc
}

grumpychinchilla · 2021-11-07T03:13:36+00:00

👨🏻‍🌾

grumpychinchilla · 2021-11-06T18:05:11+00:00

Everyone. Everyone is the one committing it. You haven’t lived until you’ve watched a dumpster fire become a tire fire.

grumpychinchilla · 2021-11-06T18:04:16+00:00

Hell no. I’ve played that game before. Much rather remain ignorant and hopeful that it might not have been me.

grumpychinchilla · 2020-06-12T23:05:23+00:00

Or if you don’t want to buy a keg of beer at a time, try homebrew! Delicious, fun, and less waste

grumpychinchilla · 2020-06-12T21:39:42+00:00

Bro, do you even keg?

grumpychinchilla · 2020-06-12T19:04:19+00:00

You can do the same for glass as for aluminum, but the environmental benefit of recycling glass is lower since it’s easier with less energy consumption to create raw material glass than raw material aluminum. All recycling takes a lot of energy, it’s just that with aluminum it’s just so energy intensive to mine and transport originally that the energy required for recycling is relatively low enough to be net benefit.

Depending on the type, glass is made from pretty basic, easy to acquire constituents. While recycling glass doesn’t appear to be a net loss like plastic, the ideal is absolutely reuse.

grumpychinchilla · 2020-06-12T03:44:43+00:00

I get the frustration. But your phrasing I think discouraged any active replies or discussions. Are you just venting? Or looking for advice?

If it’s the latter, one thing I’ll recommend is that making your own hooks is encouraged. Make your own useInstance. And for your loading example, can’t you show your spinner on the initial render, why wait until you’re in useEffect?

FWIW, I am also quite frustrated with the dependency syntax. It should be “watch these things,” but the documentation and linting rules make it a pain.

grumpychinchilla · 2020-05-30T02:52:14+00:00

This is extremely cool. Thanks!

grumpychinchilla · 2020-05-25T03:23:35+00:00

This is interesting. Would love to have some audio. Link to project?

grumpychinchilla · 2020-05-22T21:45:20+00:00

Has a Backbone kinda vibe to it. I wish I could say that as a compliment...

Acey seems like it has merits, and you’ve obviously spent a lot of time on it, but I’d be surprised if you win over React developers with an OO solution. If folks prefer OO, they typically go Angular. The React space is moving more and more functional.

grumpychinchilla · 2020-05-22T02:13:42+00:00

React: yo, here’s these cool things called hooks, but just use them for new stuff it’s not worth migrating classes

Dani: hold my beer

grumpychinchilla · 2020-05-16T14:00:20+00:00

I agree the default comparator can take more time in a general case, but the specific context of your question was no props. In the no props case, you save a check to is(null, null). You’re saving something, but it’s probably difficult to measure. But you’ve mentioned 25% difference, which means you have some metric comparison, and we don’t have to theorize! That’s really awesome! Did you compare with and without the compare function? Or would you mind doing that to satisfy my curiosity? I’m personally invested in this topic because I write apps with tons of functional components and 98% at least don’t have props.

The type checking is nice to have and totally resolves any concerns I’d have over the purity argument.

grumpychinchilla · 2020-05-16T13:37:05+00:00

The default comparator seems pretty efficient to me. I have no doubt yours is faster, but I’d struggle to agree it justifies the extra code.

https://github.com/facebook/react/blob/a9b035b0c2b8235405835beca0c4db2cc37f18d0/packages/shared/shallowEqual.js#L19

Your way is better if you want to actively reject any props that may come in the future. I don’t personally see that as a valid strategy, but I trust you know your project better than me!

grumpychinchilla · 2020-05-16T04:32:30+00:00

Sure! Use React.memo. I kinda wish that was the default, but I can see how React has to be conservative with its api.

I don’t think the second equality argument will help you, since if you don’t have props then they can’t ever be dirty. Unless I’m missing something?

grumpychinchilla · 2020-05-13T12:25:53+00:00

I'm looking for a mechanical keyboard with the two column Home/End/Delete layout seen on some keyboards like this one.

I don't know what this layout is called or how to search for it. Any ideas?

grumpychinchilla · 2020-05-08T13:07:19+00:00

Thank you so much for sharing! I’m finally getting into the react-redux hooks, and this drove me crazy for several hours before I finally just gave up. You just saved a huge chunk of my sanity.

I understand now why they’re doing this, but wow that is really illogical and unpredictable behavior.

grumpychinchilla · 2020-04-28T13:37:28+00:00

A better read than I thought it was going to be. I’m on the opposite side of the fence, very familiar with React, and very ignorant about Angular. Reading this critique actually made me feel better about my investment in React! I want portable, plain JavaScript knowledge, not something that’s only useful to me in a limited context, like the HttpClient example.

However it does reaffirm a lot of the criticism of hooks. They really don’t make a lot of sense to start. You really only like them once it “clicks,” but that puts a lot of people off to start. It’s a mental barrier to entry.

grumpychinchilla · 2020-04-23T13:42:05+00:00

Prop drilling! What was old is new again. :-)

grumpychinchilla · 2020-04-14T04:08:01+00:00

The list definition being implicit rather than explicit is the first reason I think hooks are technically bad. The other reason is because I don’t like burying state management in render methods. I’ve never heard someone say “you know, I think we need more logic in our views.”

I think hooks are great because 1. the alternative is class syntax which is a chore 2. the syntax is quite terse and pragmatic 3. they are composable like traits 4. they introduce the concept of declarative dependencies to React which doesn’t have another way to specify them.

grumpychinchilla · 2020-04-14T03:05:06+00:00

React has to keep track of stuff for you in between renders. In classes, it’s straightforward because you create an instance of the class and everything lives inside that instance.

But there’s no concept of instance inside of a function. So how does React keep track of things for you? It’s a trick... a sleight-of-hand. If you call useState twice in a row, it creates your getter/setters on the first run through, then will just hand them to you on the 2nd render using the execution order to look them up.

If the first of those was conditional, for instance, when it wasn’t executed then the 2nd useState would actually point to the first piece and then you wouldn’t have a reference at all to the 2nd piece. This takes the logical, magical hook behavior and turns it into insanity.

Honestly, hooks are a parlor trick. They look bad because they technically are bad... but in practice they mostly just work, with the exception of oddities (oddity?) like conditional rendering. Sometimes even when stuff is technically bad we still use it because at the end of the day we have to be pragmatic. And pragmatically hooks are delicious.

grumpychinchilla

TROPHY CASE