Відео

2024: not true, Appium can be integrated in CI

man, ryan used to be so awkward

He came back and will sweep BJP completely like he did same to congress. He is more powerful after jail.

Thanks so much for making this people. You rock.

42:45 It would be nice to have an opening for a plugin ecosystem on top of Excalidraw.

37:30 It's funny those have taken that long. They were some of the first features I thought of when thinking about an app similar to Excalidraw.

Amazing talk.

Put the Excalidraw link in the description, as well as his Github profile link, please.

It's truly the most difficult tool I've ever used.

Lots to learn. Thankyou Dave!

I love this demo, I learned so much about though process and limitations of different React features. thanks

That tank simile was terrible. Seriously, let's not forget that there were a total of about two tigers on the entire western front, the US soldiers just kept calling every German tank they came across a tiger. 4:33 - this bit right here is what I really need a lot more elaboration on. It needed so much more than two seconds and a brief comment, because I just cannot get this shit to even start doing anything, it's all just errors when I try to "yarn run android" and blank screens when I execute Flipper. After spending four hours yesterday trying and failing to get React-devtools to work... Christ I hate this shit.

thank you

Folks, please provide links to the libs you recommend using.

Joy Of React brought me here.

19:00 Ah man. That's a great visual. Thank you. Not sure I completely understand what you mean by 'functional level' vs 'declarative DSL', but that's okay. Curious to know if Nix, which to my understanding uses a declarative configuration, would address some of issues of Grunt without being Gulp like. (Total novice btw)

Amazing how much time and money the whole industry spent on this hype. Redux is one of the worst pieces of technology ever introduced, yet people accepted it as dogma of state management in the early days...

So hard to hear with that mouth making that clicking sound.

So what's the point of having hierarchy at all? Why not just have nodes all over the place and just manage them using recoil atoms? This reminds me of AWS S3 buckets, where directories don't actually exist, it is just a container with flat files. The illusion of directories are then "created" based on naming conventions. This seems to be heading the same direction except with state, that's why you had to bring "3D" into it. Overhyped imo and excepting a few use cases, likely not needed.

wow simply amazing how easily he explains it !!

Is it possible to use Flipper as profiling tool? I noticed the "Device plugin 'CPU' is not supported by the selected device". I'm wondering why?

The white background is burning my eyes.

I PLAYED YOUR 2048

Nice one - but not sure if HOCs are dead - there might be some use case

What is the status of this project?

Amazing, how can reach the community there's discord for it?

Does any one have the source code of this ?

Could you share the repository of this project?

God I thought it was just me thinking that the current state management tools in react ecosystem are annoying as hell in some scenarios. This looks very elegant and natural, great presentation too. Kudos.

"I've seen an app that has over a 1000 context providers". On React Native EACH TEXT has a context provider

Amazing talk!! Thank you Josh!

This is soo much I want: make website funnn

Terrific presentation, thank you

did he really just say that 13:00 🤣

import { create } from 'zustand' import { map, filter, equals, over, lensProp } from 'ramda' import { ErrorBoundary } from 'react-error-boundary' const useComponentStore = create((set) => ({ roles: {}, registerComponent: (Component, { role }) => set((state) => ({ roles: over( lensProp(role), (components = []) => [...components, Component], state.roles ) })), unregisterComponent: (Component) => set((state) => ({ roles: map(filter(equals(Component), state.roles)) })) })) const { registerComponent, unregisterComponent } = useComponentStore.getState() const PluginHandler = ({ role, passedProps }) => { const components = useComponentStore((state) => state.roles[role]) return ( <> {components.map((Component, key) => ( <ErrorBoundary key={key} fallback={<></>} onError={(e) => console.warn('plugin error', e)}> <Component {...passedProps} /> </ErrorBoundary> ))} </> ) } export default PluginHandler export { registerComponent, unregisterComponent }

driving me nuts that the debugger isn't showing width or height -.-

This is the first explanation I've seen, that properly highlights the strengths of GraphQL. Any other blog or video I've seen (even recent ones), seem like they are just fanboys, repeating what somewhat else said and actually have no idea what is going on. Thank you for this video!

понапидумывали всякой херни. заебешься учить

Simply brilliant

this man is a god

He works for Pied Piper, right? 😁 Great explanation. Thank you

The presenter is very good at presenting and explaining the subject matter.

thanks a lot

This is love! Thank you Wojciech

The 3D idea to represent state is genius. Kudos!

3:35 this screenshot of an extremely bad GUI made by a programmer who hates and doesn't understand GUIs illustrates my point that GUIs are complicated. ...sure buddy, sure. same as Linux illustrates the point that (all) operating systems are obnoxious and borderline useless.

17:17 sexy af

05:50 😂😂that's funny yo

man! ,there is no great feeling than letting someone else use your app and they are impressed with it 😊

Code for this demo app available somewhere?