Troy Rhinehart

[Troy Rhinehart @_gingur]

@benadam11 You have no idea 😉

[Troy Rhinehart @_gingur]

@Aaron_Silvas I love the energy you're putting into this, and the fact that your hard work can give others great energy back. 🍻

[Troy Rhinehart @_gingur]

@benadam11 I remember this! Ball is life 😅

[Troy Rhinehart @_gingur]

Leaving GD after 13 years, such an emotional experience...I can't comprehend how it would feel doing this every 2 years like a lot in this industry do.

[Troy Rhinehart @_gingur]

@benadam11 Yes. However, I would also let them know about the issues and see how they respond; difference between a bad experience vs a bad restaurant.

[Troy Rhinehart @_gingur]

@awesomekling Not in the EU, but do you know if this is specific to only offline or P2P/LAN gameplay? Would require significant revenue otherwise, and would most likely lead to significant changes in prices or cause publishers to double down on subscription based models

[Troy Rhinehart @_gingur]

@nz_webguy @adamwathan Underrated comment 🤣

[Troy Rhinehart @_gingur]

@adamwathan It matters, but not nearly as much as bundling multiple versions of the same dependency. Docker and package management optimizations are great when properly using devDeps and peerDeps, but deduping and semver management is where the real fun begins.

[Troy Rhinehart @_gingur]

Seems like an oxymoron, am I ignorant or wouldn't undocumented imply coming into the country illegally, which by definition is a crime?

It's not to say illegal immigrants are ill natured and want to commit crimes, but we shouldn't ignore the crime(s) they committed to get here.

[Kamala Harris @KamalaHarris]

An undocumented immigrant is not a criminal.

[Troy Rhinehart @_gingur]

@kentcdodds I love using TSOA, would you be interested to see what that would look like?

[Troy Rhinehart @_gingur]

Build time optimizations, finally! React is far from perfect but this is a great move in the right direction.

The less my source code is dependent on direct React imports, the better. This would allow the compiler to own the complexity and iterate much faster, or even be swapped

[Andrew Clark @acdlite]

By the end of 2024, you’ll likely never need these APIs again:

• useMemo, useCallback, memo → React Compiler
• forwardRef → ref is a prop
• React.lazy → RSC, promise-as-child
• useContext → use(Context)
• throw promise → use(promise)
• <Context.Provider> → <Context>

[Troy Rhinehart @_gingur]

@Aaron_Silvas @Steve8708 😂 I like to keep everyone on their toes

[Troy Rhinehart @_gingur]

@benadam11 Yes! Maybe in next next 😉

[Troy Rhinehart @_gingur]

Yesss, this is the way. Takes me back working with @benadam11 and others to define a design language, this was a critical decision that has aged very well IMO

[Devon Govett @devongovett]

I'm convinced that color variables should always be semantic, e.g. var(--border-light) not var(--gray-200), var(--highlight-background) not var(--blue-600). Knowing where a value will be used makes stuff like high contrast mode way easier to handle in a single place.

[Troy Rhinehart @_gingur]

@benadam11 @sama @gdb always has been, ben

[Troy Rhinehart @_gingur]

Amen

[Passle @passle_]

This is very much not a dream, I do this for all my libraries.

Ship standard JS, dont bundle, dont minify, dont polyfill, those are all app-level concerns.

[Troy Rhinehart @_gingur]

@benadam11 Yeah but think of the applications. I'd love a virtual nurse, educator, personal trainer, and life coach but at a fraction of the cost, always available and always learning.