What is it isomorphic to? How do I compute the isomorphism between this framework and some other thing?
Show HN: An Isomorphic JavaScript Framework Faster Than React
61–70 of 257 posts
Re: Show HN: An Isomorphic JavaScript Framework Faster Than React
#62> 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.
Flow control does not belong in markup. My favourite templating system is enlive[1] (or enliven[2]). You use CSS-style selectors to select snippets of HTML to manipulate and then use code to duplicate, remove, move or replace these snippets, insert content, set attributes etc. The "template" is pure HTML without any additional markup and without any logic. The code then says "repeat this snippet for every item in thi…
What do you think about OneScript - https://github.com/astoilkov/OneScript?
Re: Show HN: An Isomorphic JavaScript Framework Faster Than React
#63I've been playing around with RiotJs (actually committed some fixes/features to the repo). I think what is attractive about both Riot and React is that everything is "defined" in JavaScript, there isn't really a separation of markup and behavior. Each little module can act an individual component. React has gone a step further and has shown that the DOM doesn't really matter...your React code could create native apps…
Cool question. Please take a look at OneScript - https://github.com/astoilkov/OneScript and share your opinion. I believe this is the next step in developing applications. Bringing HTML, CSS and JavaScript in one place where components are modular and small.
I like this syntax. How do you pass values to a component and how do you nest components with values and lets say, loop over an array and create a (sub)component? Also, when you embed a component, is there a way to interact with it?
This looks cool, keep it up
Re: Show HN: An Isomorphic JavaScript Framework Faster Than React
#64I've been playing around with RiotJs (actually committed some fixes/features to the repo). I think what is attractive about both Riot and React is that everything is "defined" in JavaScript, there isn't really a separation of markup and behavior. Each little module can act an individual component. React has gone a step further and has shown that the DOM doesn't really matter...your React code could create native apps…
How would you compare Riot to React?
Re: Show HN: An Isomorphic JavaScript Framework Faster Than React
#65Earlier quoted context omitted.
What is problem for you - for some might be job security :) And I think Angular is still very much in fashion. At least this is impression I am getting from occasional talks with random recruiters.
this is impression I am getting from occasional talks with random recruiters What's in fashion isn't what the recruiters are talking about, but what the developers are talking about. Recruiters will always lag a bit behind whats actually in fashion.
I guess it is also depends on who is judge - either business (my case) or developers (yours :))
Re: Show HN: An Isomorphic JavaScript Framework Faster Than React
#66Have you ever encountered a situation in the browser where 32k ops per second from underscorejs wasn't enough?
How many rows/columns were in the table being repopulated? 10 times in 2400ms doesn't seem that bad - it's 240ms per refresh. Is this too slow for your use case?
The 250ms gain on rendering 1500 rows - is this something you think needs to be optimized? I can't imagine a scenario where all of those rows would fit on the screen at once.
I ask as the main area of focus for the framework seems to be speed, and I'm curious to know what inspired you to make it.
Re: Show HN: An Isomorphic JavaScript Framework Faster Than React
#67Top article on the front page of Hacker News as I write this, and not a single positive comment below. Great job, guys... To the author: I think the homepage looks great, the examples are clear and informative, and I would definitely give this a try if I weren't wed to a couple of other frameworks right now.
I think a lot of the negativity has to do with the marketing. This isn't being sold as "a cool thing I made", but "Better MV-ish Framework" and "Faster than React". If you try to position it as better than existing alternatives, HN commenters will tear it down if they don't think it makes the cut. If you put it out as "exploring interesting new approaches", I think you're likely to see a lot less negativity here. Com…
Absolutely fair points.
Another one: the general weariness with which new JS frameworks are greeted has increased massively in the 433 days since Mithril was posted here.
Re: Show HN: An Isomorphic JavaScript Framework Faster Than React
#68Still relies on JavaScript server side rendering - which will be the biggest performance bottleneck, by far, for both this and React. If you really want a framework that is faster, check out Tungsten ( https://github.com/wayfair/tungstenjs ), which is as fast as this client side, and can render in vanilla Mustache using Go/C++.
I can't speak to this framework, but you do not need to use server-side rendering for React applications. Instead, you can essentially serve a blank page on every request, then have the React application bootstrap itself when the page loads. Alternatively, one could precompile the HTML, and serve it as static content with nginx, apache, etc.
Correct, not rendering on the server removes the bottleneck.
Re: Show HN: An Isomorphic JavaScript Framework Faster Than React
#69Earlier quoted context omitted.
Cool question. Please take a look at OneScript - https://github.com/astoilkov/OneScript and share your opinion. I believe this is the next step in developing applications. Bringing HTML, CSS and JavaScript in one place where components are modular and small.
I like this syntax. How do you pass values to a component and how do you nest components with values and lets say, loop over an array and create a (sub)component? Also, when you embed a component, is there a way to interact with it? This looks cool, keep it up
Great questions. I currently filling the documentation so you could watch the repo or star it and keep an eye on it. The idea is that components will be like objects and elements so you could easily access them. Take a look at this example:
{ this.each(profiles);
My profile.
}Re: Show HN: An Isomorphic JavaScript Framework Faster Than React
#70I 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)