React.js Conf live stream [video]
youtube.com
youtube.com
I'm glad there have been no major announcements. This isn't an Apple keynote. We should want our tools to be predictable, stable, and paid attention to. Introducing more React stuff would be cool, don't get me wrong. But some of us are actually trying to build products and having stability and feature depth is more important than throwing React at another problem. The React team is fairly small and so they should stick to solving specific problems. There's still lots to be done in React Native.
Looking forward to seeing what the second half of the day brings. A lot of this stuff isn't particularly new to me but that's ok too. It's good to see they're still doing talks which introduce new users.
There's little constructive purpose for these bad faith remarks in threads like that in general (I've probably been guilty of some in the past myself). No need to slam one thing to raise up another - let tools stand on their own merit, and criticize based on that alone.
FWIW, I'm pretty heavily involved in the Angular community, and I respect what Facebook has done in creating & fostering React - I keep an eye on it because I love just about all things frontend on the web, even if I don't use React much (although I might use React Native for an app for a community I am a part of).
To look cool to other developers by shitting all over something.
So it's mostly "to vent my frustration for other aspects of my life in needless negativity and aggression in an unrelated topic".
Flex, although still alive thanks to the efforts of a group of unsung heroes, is not a platform on which I would build anything new.
Obviously I agree with you, I would never build anything new with Flex, or target the Flash runtime; but that's not to say there aren't good lessons to be learned and concepts to be snatched. Hence, the "not sure if good or bad" comment – it depends on what you steal I guess.
Besides that, there's the incalculable benefit of being able to use the same mental model (to say nothing of programming language) when developing, especially when designing UI components and animations. Even if you had equal skill with building layouts in both systems, there's great advantage in not having to context switch.
The ability to reuse code is very real, even sharing a lot with a web react app since most state/business logic is in some flux implementation.
The pain points (documentation, build process, etc.) are real, too, but things I can forgive for now due to its newness and its very strong foundation.
We put the most up to date version on this page
You could also use the underlying Draft model and manage the view entirely yourself, but React helps a lot here and removes a lot of complexity from Draft.
Also, I'm disheartened by the simple, anonymous down votes my comments are receiving rather than actual rebuttals. At least you had the decency to respond.
First, you added a snarky, negative comment as the first response to someone open-sourcing a new library. There's no need for this, especially when spicyj is (as far as I've seen) an extremely gracious open-sourcer. Your comment's core complaint, about library lock-in, was actually a valid complaint, and something that should be discussed. But sadly, the way you brought up the idea means that no one else will want to engage.
Then, you replied to @spicyj's helpful response, which had I been him I probably wouldn't have even bothered with, with another snarky negative comment.
Finally, someone else jumped into the conversation with another solution, and you replied to their comment with a sarcastic non-question. Not only that, but you used a strawman of "to make a simple rich text editor work", when clearly that's not all Draft.js is trying to do.
And then after all of that, you complained about being anonymously downvoted. (And even in lodging that complaint you somehow managed to further subtly insult @tlrobinson.)
---
I actually think your original issue, about library lock-in for text editor's a valid point. I see a lot of work going into separate rich text editors that are all reinventing the same sorts of things, with no clear best solution being developed for real-time use cases like Google Docs or Dropbox Paper. I really wish the perfect, easy solution for those existed.
That said, I'm excited about Draft.js because I think anything that Facebook wants to throw their open-source weight behind will get more love, even if it encourages others to make more competing editor libraries.
* https://news.ycombinator.com/item?id=11153935
* https://news.ycombinator.com/item?id=11153945
That said you’re absolutely not “required” to use it. It will be handy to React users because it fits into its component model and thus doesn’t have to implement the reconciliation from scratch. If you don’t use React you might not find it as handy. In this case you might like to use [ProseMirror](https://prosemirror.net/) instead.
Your post to HN is not well thought out. Most of us on HN come to read insightful comments with cinstructive critisicm. I came here to see if anyone is discussing it's architecture, performance, potential extensibility, comparison with other editors like CodeMirror and Quill etc. Your comment, in all honesty, sucked.
The goal is that with Draft.js you can easily build any UI you want and Draft.js helps you manage the underlying model and DOM manipulations.
I am sure that several people will build and publish drop-in components using Draft.js within days.
Well, something closer to CKEditor or, if you prefer minimal, something like the editor in Medium.com.
was: https://www.youtube.com/watch?v=0fCEeAgeRC0
should be: https://www.youtube.com/watch?v=pi62S_MvheE