trueadm

12 ms·

61.
by trueadm 4y ago
Lexical is a different take compared to ProseMirror and CodeMirror. We took a lot of inspiration from them, but we felt that having a source-of-truth that wasn't the DOM was a better approach. We also looked to improve on code-size, pe
62.
by trueadm 4y ago
We do have a link to a live demo. It's the Lexical Playground: https://lexical-playground.vercel.app/
63.
by trueadm 4y ago
Happy to answer any questions that folks might have about Lexical.
64.
by trueadm 9y ago
This wasn't the case. I left the project to focus my attention on React.
65.
by trueadm 9y ago
I think this may be referring to "preact-compat" issues rather than Preact issues. I know the Inferno team recently had to change a lot of the state scheduling to be 1:1 with React 15/16 (i.e. batch sync schedule setState aft
66.
by trueadm 9y ago
A very large software company that use Inferno in production already had their legal team look into Inferno. It didn't infringe on any patents.
67.
by trueadm 10y ago
It would be awesome if you could give the Inferno team your feedback so we can help improve Inferno. :)
68.
by trueadm 10y ago
What issue did you have with Inferno, would mind reporting it please so we can fix it? :)
69.
by trueadm 10y ago
This isn't true anymore. Blueprints were removed from Inferno quite some time ago. Inferno uses createVNode calls, which are very much like createElement calls.
70.
by trueadm 10y ago
We have a Slack if you're interested: https://inferno-slack.herokuapp.com/
71.
by trueadm 10y ago
Inferno also has its own event system like React does.
72.
by trueadm 10y ago
The interview actually talks quite a bit about how I went about making these changes. Worth fully reading!
73.
by trueadm 10y ago
I'm sorry, this topic has nothing to do with the operating system. Inferno in this context is a popular JavaScript library for building UIs, not an operating system.
74.
by trueadm 10y ago
Note: I'm the author of Inferno I commonly hear the same thing – you've benchmarked React and it performs fine. Did you benchmark this on a modern MacBook/laptop by any chance? The realism is that the desktop market is only 1
75.
by trueadm 10y ago
Unlike Angular 1 -> Angular 2, React Fiber will be fully backwards compatible with the current React.
76.
by trueadm 10y ago
There's no reason why React can't learn from Inferno. In fact, I'm aware that they're using a lot of the internals of Inferno to improve React Fiber. I'm sure we'll see more on this in the future :)
77.
by trueadm 10y ago
Inferno is 8kb, it's smaller than the Mithril re-write and is on par with Preact in terms of parse performance. I think you may have looked at the older Inferno codebase, as the current one is very slim and readable.
78.
by trueadm 10y ago
Note: I'm the author of Inferno and know the authors of Preact and Ivi well. That's a great question and one I frequently get asked. The "current" React codebase is legacy in many ways, the React team are hard at work on
79.
by trueadm 10y ago
This has nothing to do with React. This is a JavaScript library called Inferno – the title makes sense to people in the JavaScript scene.
80.
by trueadm 10y ago
Great work! Styletron looks awesome and the performance definitely fits well with some of the apps I work with. I'll give it a try :)
81.
by trueadm 10y ago
I never posted the Inferno website URL to Hacker News, someone else did. We should be going live with the new website in the coming week, I was hoping to post it once that had been done!
82.
by trueadm 10y ago
You can use ES2015 classes too and `inferno-compat` will try to support everything that React 15.4 currently supports. Recompose should work fine too, as should most common libraries. If you run into issues, please let the Inferno team know
83.
by trueadm 10y ago
If anyone has any further questions/queries/ideas/rants you can jump on the Inferno Slack - https://inferno-slack.herokuapp.com/ . The team and I would love to hear from you. We want to make Inferno better and
84.
by trueadm 10y ago
You totally can use Inferno. You can use a package on NPM called "inferno-compat" to alias out React to Inferno via Webpack/Babel/Browserify if you want to. Alternatively, you can use Inferno as is and it has JSX Babel p
85.
by trueadm 10y ago
I completely agree and I wrote Inferno. I really do think people jump on Hacker News stories in the wrong way at times. Inferno isn't meant to make you abandon months of work because it's shiny and new – or whatever reason someone
86.
by trueadm 10y ago
Will definitely do that. README writing is like an entirely different skill in itself to be honest. I'm not great at it :/
87.
by trueadm 10y ago
I think it looks great. We've been designing this site for a while now and there comes a point where you need to stop designing it and start building it – which is why we still don't have a site :D
88.
by trueadm 10y ago
note: I'm the author of Inferno. If you're comfortable with what you have right now. I don't expect you to switch to Inferno. If you're happy with your app, it works great, it's performance is where you want it and
89.
by trueadm 10y ago
That is so far from the truth that it's unbelievable. Inferno has the same surface API as React – the public endpoints. Everything under the hood is different though and it's different for many good reasons which I'll cover i
90.
by trueadm 10y ago
You don't need to necessarily use Inferno in production all at all. If you're happy with React, stick with it. Inferno can serve to help other authors and the React team to further improve their tools. This is open source after al

More ›