Live data from Hacker News

Viewing profile — acywatson

acywatson

HN member
Joined
Wed, Apr 13, 2022, 8:29 PM UTC
HN karma
18
Public activity
13 items

About acywatson

No profile information was provided.

Recent public activity

  1. comment
    Comment #31829887

    We definitely have plans to improve Tables drastically over time, but I'm not sure when we'll get to those particular issues. If you care to make an Issue for this on GitHub, that …

  2. comment
    Comment #31825536

    Sure - DraftJS, for instance, delegates DOM reconciliation to React. Lexical does not. The core library is framework-agnostic, with it's own diffing and reconciliation processes.

  3. comment
    Comment #31825450

    It's under consideration, but as of now we need native support for iOS and Android first. React Native doesn't currently support contentEditable.

  4. comment
    Comment #31825391

    Yes, we have something like this in @lexical/selection: https://github.com/facebook/lexical/blob/af099ffd9f464b523d6...

  5. comment
    Comment #31817370

    You mean typing latency, right? The most important thing we do there is handling reconciliation ourselves rather than delegating to a framework (e.g., React). If you have full cont…

  6. comment
    Comment #31815250

    I work at Meta on the Lexical team - yes, Lexical supports markdown and rendering from markdown syntax. Lexical isn't a drop-in replacement for Draft, but we're migrating all of ou…

  7. comment
    Comment #31024241

    >Sure, but indicate that it's an alpha product Do you mean something like the banner on the README? https://github.com/facebook/lexical >They don't even have the decency to label i…

  8. comment
    Comment #31023751

    FWIW, we updated the README to reflect the status of DraftJS today. https://github.com/facebook/draft-js Point taken about updating the site, though.

  9. comment
    Comment #31023678

    It would be awesome if you'd be willing to report them on GitHub :) https://github.com/facebook/lexical/issues/new?assignees=&la...

  10. comment
    Comment #31023427

    > So Lexical doesn't care about how the DOM is rendered? Or is speech-to-text derived independent of the DOM? I do now see your general point about the conflation there - the reali…

  11. comment
    Comment #31023308

    > I'm building my own text editor and I thought VSCode was impressive enough. See this well written article about their text buffer reimplementation: https://code.visualstudio.com/…

  12. comment
    Comment #31023286

    Thank for the feedback - we're definitely still working on the docs. > These are weird and conflated set of buzzwords. Why should something that isn't concerned with UI components …

  13. comment
    Comment #31023243

    The core Lexical library is really a framework for building such editors. However, we also provide many common rich-text features out-of-the-box via separate packages, such as @lex…