zurfyx

Lexical contributor here. I love what you've build here! A full-fledged collaborative rich text editor. I'm glad that Lexical worked well for you, we'd be happy to take your feedback throughout the development process, you can reach out to me over Discord by the same username or on our server.

No idea :D https://github.com/facebook/lexical/pull/1733

Mostly referring to high-traffic surfaces here, like Facebook Feed or Messenger. The % varies depending on the environment and the previous Draft.js implementation (and their plugins) but overall it's been very positive, especially with low-end devices that went way over 16ms response time per keypress.

Thanks for trying it out! Mind drafting a quick issue here so that we can have a look? https://github.com/facebook/lexical/issues

No docs yet - but this code pointer for physical files (plugin) may help https://github.com/facebook/lexical/blob/main/packages/lexic...

We listen to a few typing related events and do some computation from here: keydown, input, beforeinput. Android, contrary to any other device, mostly relies on composition so Lexical makes sure to handle and flush these events accordingly.

If you're curious, this is where it all starts - https://github.com/facebook/lexical/blob/main/packages/lexic...

Running your own editor with built-in plugins does not take more than a few lines of code - see the playground code https://github.com/facebook/lexical/blob/main/packages/lexic...

We already provide most common plugins out of the box (inc. lists and tables) but if you're planning to build a feature rich interface with many custom plugins it may take somewhat longer.

For 1. 2. see @trueadm's answer here - https://news.ycombinator.com/item?id=31022152

3. Lexical is not strictly tied to collaboration but its plugin system was built to be extensible enough to cater all developers needs. Collaboration is just another plugin (@lexical/yjs) and does listen and perform the conversion every time there's changes in the EditorState.

This model of independent plugins that can be plugged-and-played without further ado also simplifies devX as collaboration can be added later when the application is mature without the need to rethink any of the plugins that were originally created for non-collab plain/rich text.

4. Lexical Web is just the first of many. We want to port the API and fundamentals to various others platforms, including iOS for which we are already performing the initial set of testing. Cross-platform means the API, including Node's will look alike and EditorState and node's properties will be compatible even if behind the scenes the reconciler is constrained by the toolkit available on each platform (and doesn't render or behave 100% like Web's).

A setInterval/setTimeout can only be cleared (clearInterval/clearTimeout). Modifications have to pushed through clear -> set.

"Of all the ways of doing concurrency, callbacks are by far the worst," Why? Working with callbacks on a solo thread has proved to be more performant I/O wise than threads.

"for any other problem anything else will be much better than Node.js, even PHP."

Why?

While it might be true to certain extend (i.e. Node not being the right solution for many cases), this article is just filled with baseless arguments.

I did download it if that helps (the video when you started with "test 123"). Will be up in ~2h https://youtu.be/qFoKjhIFGsk

For those who want to see how it was built, he still has a few videos about the early stages of its development on his YouTube:

https://www.youtube.com/watch?v=fBZRGLzYnns

https://www.youtube.com/watch?v=rBUDudoxW18

https://www.youtube.com/watch?v=9XBOCY_LdGQ

https://www.youtube.com/watch?v=MAs5TOozedQ

Hey! I wrote this library[0] as a part of Google Summer of Code 2017 @ Physical Web organization. I found no easy way of integrating (reading & writing URLs) my browsed-based app[1] with Eddyson. While there are official libraries for both iOS and Android, I found none for Eddyson.

So I thought this could be an opportunity to dig into the Physical Web specifications[2], to build something easy to use for us (web developers <3) since Web Bluetooth is getting more and more popular.

Looking forward to your feedback! =D

PS: Special thanks to @beaufortfrancois for the super useful source code of the default Physical Web Eddystone config URL[3].

[0] https://www.npmjs.com/package/eddystone-web-bluetooth

[1] https://github.com/zurfyx/memories

[2] https://github.com/beaufortfrancois/sandbox/tree/gh-pages/we...

[3] https://github.com/beaufortfrancois/sandbox/blob/gh-pages/we...

It looks great atm, now it matches the colors of the site. They even recently added it a grey-er background color which makes it different from the content background.