Why build in list traversal functions? Some people prefer lodash, some prefer underscore, others prefer VanillaJS. It seems like just a little sugar, but adding a sugar a little at a time gets addictive.
Show HN: An Isomorphic JavaScript Framework Faster Than React
141–150 of 257 posts
Re: Show HN: An Isomorphic JavaScript Framework Faster Than React
#142Earlier quoted context omitted.
Only if you feel that Angular itself was a mistake. I do, primarily because it's yet another attempt in a long history of misguided attempts to bestow Turing completeness on XML.
Not at all! Honestly there are some WONDERFUL things about angular. There are some bad ones too. - Polling for changes vs. event driven - two way data bindings causing infinite redraw loops. - "feels like O(n^2)" performance on ng-repeats / large pages but things like the templating, directives, data-binding... they are all really good things. And dependency injection! They have really moved the needle forward on cli…
ng-if, ng-switch, ng-repeat? There's already a language in the browser that does these things, it's called JavaScript.
Why do you even need dependency injection and singleton services and factories in a dynamic language with closures and first-class functions? You don't. Client-side testing works fine without DI. Angular is just a way to do Java in JavaScript. It's a pile of unnecessary complexity designed to sell to enterprises that love over-designed Java projects and want to make client-side development feel more similar to what they know. In that regard I suppose Angular is a little better than Google Web Toolkit, but that isn't saying much.
Re: Show HN: An Isomorphic JavaScript Framework Faster Than React
#143Earlier quoted context omitted.
As someone who mostly codes in Python, I don't understand, why JS gets new framework so often. What is the reason behind? Is Javascript makes thing easy to develop a new framework? Why doesn't Python get new framework so often?
My personal theory is that it is because * JS is possibly the largest programming language community in the world * There are a lot of shortcomings in "the web platform" for app-style development * Most JS developers are primarily developers in another language with a stronger culture and set of ideas/idioms Combine these things and you get .NET developers creating C# flavored JS frameworks, Ruby developers creating…
Is there any Pythonish JS framework?
Re: Show HN: An Isomorphic JavaScript Framework Faster Than React
#144Why build in list traversal functions? Some people prefer lodash, some prefer underscore, others prefer VanillaJS. It seems like just a little sugar, but adding a sugar a little at a time gets addictive.
You are correct. I am thinking of removing the functional methods. It would be better to leave this battle to lodash and underscore.
Re: Show HN: An Isomorphic JavaScript Framework Faster Than React
#145Earlier quoted context omitted.
You are absolutely correct. It is hard to compete with Google and Facebook. Possibly impossible. I love what I do and it is great experience developing jsblocks. And one last thing you could check OneScript - https://github.com/astoilkov/OneScript . Do you think it is simple?
Why not joining Elm instead?
I believe that HTML, CSS, JavaScript should be combined the way they exist in the moment. Elm is too revolutionary for me. :)
Re: Show HN: An Isomorphic JavaScript Framework Faster Than React
#146I'm surprised that no one's pointed this out yet, but isn't this basically the same as Knockout (http://knockoutjs.com/)?
The difference being that Knockout's been around forever (first release was in 2010), does two things and does them well (data binding and observables), and is very mature and feature-complete at this point.
I don't have any comparison performance-wise, but I don't see anything new and exciting feature-wise in JSBlocks that Knockout doesn't already do.
Re: Show HN: An Isomorphic JavaScript Framework Faster Than React
#147I'm just generally not a big fan of "X is some percent slower than Y" stats, because I find them counterintuitive. However, in this case I think something is wrong. Rendering: jsblocks: 700ms React: 950ms (35% slower) Angular: 2200ms (310% slower) Doing some maths: 700ms + (700ms * 0.35) = 945ms 700ms + (700ms * 3.10) = 2870ms Looks like they got a little carried away when calculating Angular's rendering speed. Same…
You are absolutely correct. It actually is an error. Thanks I will fix it.
[deleted]
Re: Show HN: An Isomorphic JavaScript Framework Faster Than React
#148Being a current react user the thing that I like the most about react is having my markup and my logic in one self contained file. React is fast, but that isn't what has me use it on all of my projects. React has toString() which makes isomorphic apps very easy to create but that isn't why I use it either. I use it because it constantly encourages maintainable solutions for user interfaces.
If you don't mind me asking - how do you manage that? Do you use inline CSS a la https://speakerdeck.com/vjeux/react-css-in-js?
Re: Show HN: An Isomorphic JavaScript Framework Faster Than React
#149It'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.
Correct. But React is also a step behind ClojureScript based React wrappers :) like Om and Reagent.
Could you explain why are they step ahead? I am not familiar with ClojureScript, but my interest in it is really high.
Re: Show HN: An Isomorphic JavaScript Framework Faster Than React
#150I'm surprised that no one's pointed this out yet, but isn't this basically the same as Knockout ( http://knockoutjs.com/ )? The difference being that Knockout's been around forever (first release was in 2010), does two things and does them well (data binding and observables), and is very mature and feature-complete at this point. I don't have any comparison performance-wise, but I don't see anything new and exciting…
It is similar to Knockout. However, Knockout is hard to manage because you have to invent architecture on your own while jsblocks offers MVC out of the box. Additionally, Knockout don't have routing, server-side rendering, animations, filtering, sorting, paging, lazy loading of views, validation, working with remote data out of the box.
Also the debugging experience is a cool feature - http://jsblocks.com/learn/introduction-why-jsblocks#debuggin....