Any specific reason it is called Inferno? Somehow I can't stop thinking that after Inferno comes Purgatorio and Paradiso.
And the name is already taken:
https://en.wikipedia.org/wiki/Inferno_(operating_system)
Inferno: A fast, React-like JavaScript library for building UIs
31–40 of 128 posts
Re: Inferno: A fast, React-like JavaScript library for building UIs
#32We were previously using RiotJs in our company. We are building huge single page application and recently moved to InfernoJS. Results have been amazing. RiotJs used to BE lagging a lot (It simply could not handle 3000 components in same way) It had really long (50ms) delays everywhere.
After moving to Inferno following things have improved:
-We are unit testing components -Performance!!! (No delays/lagging anymore) -es2015 syntax with JSX and inheritance -Intellisense support in IDEs (webstorm) no custom riot syntax - Future proof syntax without worrying low level API changes
Negative things: -It took for a while to recode all our components in JSX
--Havunen
Re: Inferno: A fast, React-like JavaScript library for building UIs
#33Any specific reason it is called Inferno? Somehow I can't stop thinking that after Inferno comes Purgatorio and Paradiso.
And the name is already taken: https://en.wikipedia.org/wiki/Inferno_(operating_system)
React was also taken before Facebook used it. It's not an issue in my eyes. Inferno was used to emphasise performance and power.
Re: Inferno: A fast, React-like JavaScript library for building UIs
#34We were previously using RiotJs in our company. We are building huge single page application and recently moved to InfernoJS. Results have been amazing. RiotJs used to BE lagging a lot (It simply could not handle 3000 components in same way) It had really long (50ms) delays everywhere. After moving to Inferno following things have improved: -We are unit testing components -Performance!!! (No delays/lagging anymore) -…
> It simply could not handle 3000 components in same way
Can you elaborate?
Do you mean 3000 simultaneously in the DOM? Is this a grid/table where each cell is a component or something else?
Re: Inferno: A fast, React-like JavaScript library for building UIs
#35"Non-performant features have been removed or replaced where an alternative solution is easy to adopt without too many changes." Sound for me like preact ( https://github.com/developit/preact )
Same API as react? sounds nice. What did they left out?
"but only the modern (ES6 Classes and stateless functional components) interfaces"
Re: Inferno: A fast, React-like JavaScript library for building UIs
#36Earlier quoted context omitted.
TypeScript not only helped improve Inferno's with quality and read-ability of code. It can potentially help produce highly optimal output (bundles) with Google's Closure Compiler. In the future it may even help created optimised WebAssembly output. It's an exciting time :)
I've just opened the GitHub repo and I see no trace of TypeScript, no .ts files anywhere
[deleted]
Re: Inferno: A fast, React-like JavaScript library for building UIs
#37Earlier quoted context omitted.
TypeScript not only helped improve Inferno's with quality and read-ability of code. It can potentially help produce highly optimal output (bundles) with Google's Closure Compiler. In the future it may even help created optimised WebAssembly output. It's an exciting time :)
I've just opened the GitHub repo and I see no trace of TypeScript, no .ts files anywhere
Wrong branch. Check 0.8-dev: https://github.com/trueadm/inferno/tree/0.8-dev/src
Re: Inferno: A fast, React-like JavaScript library for building UIs
#38Still feel like we're talking past each other a bit here. Some portion of your UI logic is going to have to translate that data into the corresponding UI output, whether it be HTML elements or Android Views or iOS NSWhateverThingsTheyUse. With a virtual DOM, that's a two step process: your component is responsible for doing the "data -> desired UI structure" translation, and then the VDOM layer is responsible for tra…
Erm. That... is a comment that _I_ made, a couple days ago, in a Reddit thread where someone was asking about trying to diff data instead of the VDOM. Why are you pasting it here?
https://www.reddit.com/r/javascript/comments/4m1w6a/an_extre...
Re: Inferno: A fast, React-like JavaScript library for building UIs
#39We were previously using RiotJs in our company. We are building huge single page application and recently moved to InfernoJS. Results have been amazing. RiotJs used to BE lagging a lot (It simply could not handle 3000 components in same way) It had really long (50ms) delays everywhere. After moving to Inferno following things have improved: -We are unit testing components -Performance!!! (No delays/lagging anymore) -…
What do you consider huge?
Maybe we're just slow, but we recently estimated that rewriting and launching our whole frontend in another js Framework would take a dedicated 3 Person Team atleast a year, how do you explain this cost to someone with financial responsibility, I mean the benefits are probably great, but THAT great?
Re: Inferno: A fast, React-like JavaScript library for building UIs
#40Still feel like we're talking past each other a bit here. Some portion of your UI logic is going to have to translate that data into the corresponding UI output, whether it be HTML elements or Android Views or iOS NSWhateverThingsTheyUse. With a virtual DOM, that's a two step process: your component is responsible for doing the "data -> desired UI structure" translation, and then the VDOM layer is responsible for tra…
Erm. That... is a comment that _I_ made, a couple days ago, in a Reddit thread where someone was asking about trying to diff data instead of the VDOM. Why are you pasting it here? https://www.reddit.com/r/javascript/comments/4m1w6a/an_extre...
...sincerest form of flattery?