Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: An Isomorphic JavaScript Framework Faster Than React

jsblocks.com

Post reply on HN
Print view View original

171–180 of 257 posts

Re: Show HN: An Isomorphic JavaScript Framework Faster Than React

#171

Post by gcb0 »

mambodog wrote: post #6

It's not hard to be faster than React, React's performance benefit comes from the fact it makes performance easy to understand and optimise rather than just being magically (but opaquely) fast. However, the real reason React is a good choice is not performance, but rather how it encourages developers to think about, isolate and better manage mutable state in their applications.

care to share how react is transparent?

it's completely opaque on how it decides to re render the dom. unless you only have react code there, it's completely dark magic for other code

Re: Show HN: An Isomorphic JavaScript Framework Faster Than React

#172

Post by wambotron »

lhorie wrote: post #70
yummybear wrote: post #12

I think it's great that there is such an amount of active development in the JS sphere, and I'm sure your framework is fantastic - so don't take this as directed at your framework specifically. That being said... I am however feeling so overexposed to new libraries and frameworks that I can hardly muster the energy to even look at it. I constantly feel that I'm behind on my homework having to evaluate new libraries a…

Take a look at Mithril. People are frequently surprised by its small learning curve (and for many, the majority of the learning is for knowledge that you can go and apply outside of Mithril)

I'm using Mithril because of how easy it is to look over the source. I didn't want to have another framework with a huge learning curve (even for senior devs) like Angular. It's well documented, and you can read the entire Mithril source and understand what it's doing within a few hours. That means I don't have to bother training people on it. I can give any new people the API and a link to the source and they should be able to contribute within days.

Re: Show HN: An Isomorphic JavaScript Framework Faster Than React

#173

Post by lhorie »

rattray wrote: post #53
beefsack wrote: post #46

I'd be more interested to see a performance comparison with Mithril[1] rather than React, their core functionality is similar but Mitril strives to be lean and fast. [1] https://lhorie.github.io/mithril/

Agreed. Mithril's performance is incredible, and it's also closer to React in philosophy. That's the alternative I'd be looking at (perhaps along with Vue, which also goes unmentioned). EDIT: though, one difference is this supports server-side rendering out of the box, while Mithril requires a (tiny) third-party module: https://www.npmjs.com/package/mithril-node-render

There's also another more ambitious Mithril isomorphism project called misojs https://github.com/jsguy/misojs

Definitely worth looking into if you're looking for a full stack solution.

Re: Show HN: An Isomorphic JavaScript Framework Faster Than React

#174

Post by insin »

keslag wrote: post #155
vvpan wrote: post #127

Earlier quoted context omitted.

You mean how the DOM is constructed via JS functions? There's this project to fix it: https://github.com/insin/msx

Thanks for this, I was looking for something that could keep me using Mithril.

FYI, you can use Babel to transpile JSX for Mithril by putting this in .babelrc:

    {
      "jsxPragma": "m"
    }

Re: Show HN: An Isomorphic JavaScript Framework Faster Than React

#175

Post by jonahx »

astoilkov wrote: post #166
swah wrote: post #165

To demonstrate speed, don't use a very slow CSS transition property...

You mean the animations demo? This is to showcase how to work with animations to speed. CSS3 Transitions/Animations have the same performance regardless of the framework.

I think he's just saying you should have used a lower transition time, like 100 or 200ms. It has to do with nothing more than the impression it makes on the user. It's "illogical" but if one of your examples uses a slow CSS transition then the framework "feels" slower, even though the two things have nothing to do with each other.

Re: Show HN: An Isomorphic JavaScript Framework Faster Than React

#176

Post by smanuel »

yummybear wrote: post #12

I think it's great that there is such an amount of active development in the JS sphere, and I'm sure your framework is fantastic - so don't take this as directed at your framework specifically. That being said... I am however feeling so overexposed to new libraries and frameworks that I can hardly muster the energy to even look at it. I constantly feel that I'm behind on my homework having to evaluate new libraries a…

That comment!

That's exactly how I feel about every new js framework popping out from nowhere.

But I accidentally clicked on the title. The site looks cool and guess what, a framework which is faster that React and doesn't make you put xml in js.

And it grabbed my attention. I don't know whether I'll ever use it but it will be on my radar for sure. Especially if they don't lie about how fast it is.

Re: Show HN: An Isomorphic JavaScript Framework Faster Than React

#177

Post by nashashmi »

snarfy wrote: post #3

> Well, one problem is declarative programming has never been as expressive as imperative programming. In React you'd use JavaScript for this iteration. This is why I like React over say Angular, with ng-each, ng-if, etc. Flow control does not belong in markup. I cringed the first time I saw an XML schema with an IF element.

You are right. Flow control does not belong in markup. But what if I redefined the logic and called them instead relationships.

Could relationships be declared in markup? Could behaviors be declared in markup? Then we would expect the browser and the script to play with the relationships according to the behaviors.

Re: Show HN: An Isomorphic JavaScript Framework Faster Than React

#178

Post by vdaniuk »

guelo wrote: post #170
vdaniuk wrote: post #39

Earlier quoted context omitted.

There is no "our" and there is no "we". Developers, web developers, JS developers or even HN users who are JS developers are not: * a tribe * a close-knit group * an industry union You do not assign blame to hundreds of thousands of professionals, who live in different parts of the world, speak different languages and work on different projects. The web evolves without intelligent design or regard of your personal in…

> not: > * a tribe > * a close-knit group > * an industry union unfourtunately

I would love to see some sustainable structured cooperation with at least thousands of developers participating.

https://snowdrift.coop <-- this is a great example, btw

Re: Show HN: An Isomorphic JavaScript Framework Faster Than React

#179

Post by anilgulecha »

striking wrote: post #14
anshin wrote: post #9

This is interesting, but it doesn't excite me. My initial reaction is to be curious as to why it's able to thrash underscore and lodash (and React too, but separately) on speed. There could be many reasons for this. Maybe I'm personally not interested in adopting a new framework, maybe your target audience (which includes me) has some sort of fatigue or lack of interest, maybe speed isn't enough of a reason to sell m…

I think it's because people are tired of the thrashing between/around the "next big thing." Angular was supposed to fix everything, React is still trying to fix everything... But even Atom stopped using React because it was so slow. As for this framework, I'd be happier if it came in discrete chunks that you could wire together, because if you're not happy with one part of it, you don't have to accept it. You can ins…

> But even Atom stopped using React because it was so slow

That's a mischaracterization -- it was only slow for a very specific usecase -- rendering a source code text-view. (It's like using an optimized C plugin in your python project for that core part that needs the benefit of performance.)

React makes a LOT of sense for a JS framework, and it's not a surprise that it's among the most popular ones now. To simply call it unusable because ONE particular usecase did not suit it is doing it an injustice.

Re: Show HN: An Isomorphic JavaScript Framework Faster Than React

#180

Post by daenz »

yummybear wrote: post #12

I think it's great that there is such an amount of active development in the JS sphere, and I'm sure your framework is fantastic - so don't take this as directed at your framework specifically. That being said... I am however feeling so overexposed to new libraries and frameworks that I can hardly muster the energy to even look at it. I constantly feel that I'm behind on my homework having to evaluate new libraries a…

I feel what you're saying. With regards to this and similar projects, I think the important thing is to be familiar with reactive programming. To me, it was an eye-opening new paradigm to develop in.
Post reply on HN