61–70 of 107 posts
Earlier quoted context omitted.
Pose [0] was posted on HN a few days ago. I haven't tried it, but its API looks super clean. HN Discussion [1] [0] https://popmotion.io/pose/ [1] https://news.ycombinator.com/item?id=16701756
I got excited about Pose but when I tried it out I saw a lot of unexpected and undocumented behavior. Seems promising but docs needs more work and examples!
This is awesome course. I'm watching the videos and coding last 2 hours. Very happy with what I was able to do in such a short period.
Earlier quoted context omitted.
Eh, React is 5 years old. I've been writing it professionally for 3. I'm not worried. And honestly -- React doesn't have the same pain points jQuery/Backbone/Angular1 did where I couldn't wait to move on after 6 months. We'd have to see an absolutely massive paradigm shift before I'd regret writing my apps in React.
I feel this way about React but Redux seems awkward and worthy of replacement. Am I in the minority on this?
Earlier quoted context omitted.
That's why I am going to wait till next year to start learning JQuery. Should be stable and mature by then.
Too late, http://youmightnotneedjquery.com/
I fear that by the time I'm good enough at react, another library will come out
I fear that by the time I'm good enough at react, another library will come out
Probably next big thing will be straight web components or UI libraries like react or angular converting to web components. So everything should be nicely interoperable in the future, it'd just be a matter of how your modeling your data.
Imagine for every 10 components you pull you'd load 10 separate frameworks - unless they all come from the same source. These "components" wouldn't be able to know one another or work together at all. The only thing web components are good for are encapsulated styles, but that hasn't been a problem for many years now.
Since they've come up with the idea the web has moved on. React has progressed to such an extent that javascript has effectively left the browser, drives full-native applications, renders on the server, makes interop possible that no piece of technology has been able to pull off before, where you can share code and semantics on pretty much every platform while being able to re-use eco system components: https://news.ycombinator.com/item?id=16198843 and https://github.com/gaearon/react-blessed-hot-motion
Throwing all this away, we'd be back in a browser-tied web driven by dumb-components, and for no reason at all.
Earlier quoted context omitted.
I feel this way about React but Redux seems awkward and worthy of replacement. Am I in the minority on this?
There are tons of options for State Management before you even need Redux. Check out: Context API: https://reactjs.org/docs/context.html Unstated: https://github.com/jamiebuilds/unstated MobX: https://github.com/mobxjs/mobx
One thing completely missing from courses is how to handle animations. Most React apps have no animations whatsoever (including mine, because I have no idea how to implement them), but they're important for usability IMHO.
Pose [0] was posted on HN a few days ago. I haven't tried it, but its API looks super clean. HN Discussion [1] [0] https://popmotion.io/pose/ [1] https://news.ycombinator.com/item?id=16701756
Earlier quoted context omitted.
I recently found https://svelte.technology and looking forward to trying it out. It has no run-time like React or any other virtual DOM engine, but instead does compile-time static analysis. It is a Rich Harris project (authored Rollup, Ractive, Bublé) so might be worth paying attention to.
Ractive was a neat little library which was under appreciated. React took over the world with all the immutable - one way binding and virtual Dom thing.. otherwise ractive was far lighter and better than Angular