Still 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 translating that into the actual UI pieces. If you've got {likes : 42}, React has no idea what a "like" is, what it means to have 42 of them, or what it should do with that information. Your code has to tell it what that means in terms of something to actually draw.
Inferno: A fast, React-like JavaScript library for building UIs
21–30 of 128 posts
Re: Inferno: A fast, React-like JavaScript library for building UIs
#22But does it have something similar to React Native?
This was a problem I was trying to solve as well and theres a pretty elegent solution that this project has implemented partly already. The "render to string" is also a proof of concept that the indicates "unknown" types can be fullfilled by a "renderer". So long as he allows generic "renderers". Within a more free form environment like nativescript[ 1], this library can be one of any that can be used. I was planning…
I didn't know about nativescript before, thanks for bringing it to my attention! That said, it looks like nativescript promotes single code for multiple platform, which means the app won't look awesome in any of them (examples from history: phonegap, java awt). I would be much more comfortable with it if I could just use JS to access native controls and style them using the established (platform specific) methods. I am guessing css will never support each and every widget property... Is this approach possible with nativescript?
Re: Inferno: A fast, React-like JavaScript library for building UIs
#23This is the second time trueadm posted this. Not sure what you're trying to prove? Mind answering this?
Trying to prove? I'm trying to get feedback and input on this project. Any feedback is good :)
Re: Inferno: A fast, React-like JavaScript library for building UIs
#24This is the second time trueadm posted this. Not sure what you're trying to prove? Mind answering this?
[deleted]
Re: Inferno: A fast, React-like JavaScript library for building UIs
#25It's still in progress but it gets better on each release. Even better that the new version is using TypeScript!
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
Re: Inferno: A fast, React-like JavaScript library for building UIs
#26This is the second time trueadm posted this. Not sure what you're trying to prove? Mind answering this?
Trying to prove? I'm trying to get feedback and input on this project. Any feedback is good :)
The vitriol on this thread is surprising and disappointing, but I can reassure you that it's also uninformed: re-posting things that have received little or no discussion, after some decent interval, is a norm on HN and is encouraged.
It would be a bad idea to post this story again in another month, but your last post got no comments at all, so this is presumably totally legit.
Re: Inferno: A fast, React-like JavaScript library for building UIs
#27This is the second time trueadm posted this. Not sure what you're trying to prove? Mind answering this?
Trying to prove? I'm trying to get feedback and input on this project. Any feedback is good :)
It's somewhat ironic that your comment was also posted twice. :)
FWIW, I don't disapprove of you submitting this twice. I, like most people, did not see the original submission, so why not.
Re: Inferno: A fast, React-like JavaScript library for building UIs
#28This is the second time trueadm posted this. Not sure what you're trying to prove? Mind answering this?
Trying to prove? I'm trying to get feedback and input on this project. Any feedback is good :)
tptacek is right: totally legit. From https://news.ycombinator.com/newsfaq.html:
Are reposts ok?
If a story has had significant attention in the last year or so, we kill reposts as duplicates. If not, a small number of reposts is ok.
The reason is that there's so much randomness in what gets seen on /newest and thus gets a chance at the front page. Allowing a few rolls of the dice is a way of mitigating that randomness and increasing the best posts' chance at getting attention, which is a top priority here. So we don't penalize reposts as dupes until that happens.
Edit: please don't take the pushback personally. JavaScript fatigue and framework fatigue have become trends over the last year or so. That's probably why the discussion is a bit more cranky than the median. Criticisms like 'ego' are totally out of line; neutral questions like "What problem does this solve" are of course fine.
Re: Inferno: A fast, React-like JavaScript library for building UIs
#29Someone's ego
Please don't comment like this here! HN comments need to be civil and substantive—especially in response to new work, which is so easy to dismiss. And personal attacks are right out.
We detached this from https://news.ycombinator.com/item?id=11837303 and marked it off-topic.
Re: Inferno: A fast, React-like JavaScript library for building UIs
#30"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?