HackerTrans
TopNewTrendsCommentsPastAskShowJobs

mattkrick

no profile record

comments

mattkrick
·3 mesi fa·discuss
The post fails to mention that spaceX is not just a rocket company. Bundled with it is xAI, which is presumably losing money hand over fist. Package enough risk together and sell for a higher price to retail consumers. We’ve seen this play…
mattkrick
·5 mesi fa·discuss
Biome has been out of alpha for a few years now and is fantastic :-)
mattkrick
·7 mesi fa·discuss
I just finished the red rising series this year. Do you have any other recommendations in the same genre?
mattkrick
·9 mesi fa·discuss
The ads made this unreadable. Is this a thing? Get to hackernews front page & then inject your post with as many ads as possible to “cash in”?
mattkrick
·10 mesi fa·discuss
I’m in the exact same boat. Also toying with the idea of going back to android for the pixel 10 pro. I do miss android notifications and keyboard. Are there any features keeping you from going back?
mattkrick
·7 anni fa·discuss
Hooks are absolutely fantastic. However, there are still a few pain points:

- useState with an array is bad news if more than 1 component is consuming or setting the state.The clunky alternative is to keep it in a ref & call a forceUpdate whenever you would normally call your setter

- useCallback doesn't scratch the itch for things like document event listeners since everything inside the callback will be stale. The clunky alternative is a custom useEventCallback that keeps your callback function in a ref. (and that might not work in the upcoming sync mode)

- linter rules can be too strict & the --fix flag can actually cause a break in your app by adding things to the dependency list. Sometimes a useEffect depends on the current value of a ref, but linter says that's a no-no. 2 useCallbacks can be co-dependent, but there's no way to write that co-dependence in the dependency list. Sometimes I want to return null before a hook. The clunky alternative for all these is a bunch of eslint-ignore comments.