14 ms·
Some of these grievances might be better titled "things that thew me off when learning React". I'm not quite sure how using "className" vs "class" materially a
by FLGMwt 10y ago
Some of these grievances might be better titled "things that thew me off when learning React".
I'm not quite sure how using "className" vs "class" materially affects a complex project.
propTypes are pretty shallow in terms of checking, but I've seen them more as something third party components should provide as metadata/documentation rather than replacing a type system. Large project should rely on Flow or TypeScript if they're worried about typings.
I'm not sure I follow the complaints against asychronicity? Maybe when dealing with improperly complex components it becomes tricky and that I think takes experience to get a feel for.
Additionally, if we're comparing what appears to me to be a synchronous two way binding pattern to React, I think it's really just a matter of choosing the wrong technology for a given preference. React and the omnidirectional data flow pattern are directly opposed to that.
- aphextron 10y ago>I'm not sure I follow the complaints against asychronicity? Maybe when dealing with improperly complex components it becomes tricky and that I think takes experience to get a feel for I found this argument pretty confusing at first too. I think since the author is familiar with Scala he may be used to the Actor style of async programming used heavily in the Akka framework that abstracts most of the hard to understand control flow away from the programmer (http://doc.akka.io/docs/akka/2.4/scala/actors.html http://doc.akka.io/docs/akka/2.4/scala/actors.html). It's a valid complaint, but as long as Javascript is the only choice for developing on the web we don't really have an alternative.
- FLGMwt 10y agoWhoops, missed the edit window. s/omni/uni