61–70 of 121 posts
I vote for React + MobX as the goto stack of 2017.
> Learn [Vue.js] after you have learned React or Angular. Hugely disagree with this. I really like Vue - but in my (very limited) experience, its appeal is that even though it's not as powerful or flexible as React or Angular it's way easier to learn and get moving with. Fewer new concepts, less new tooling, no ecosystem of related stuff to consider, etc. I'd have suggested learning Vue first, and sticking with it un…
I vote for React + MobX as the goto stack of 2017.
I want a javascript framework that allows me to update a page incrementally, but also always works correctly and contains full content from the first server-side page load. Are there any options for this? Are there even keywords I can search for that discuss this? Sure, this files under "anything is possible", but honestly, I'd like a javascript framework that doesn't actively fight me also having static content. Any…
It also manages to do this without introducing needless abstractions into your code. Even more magical: it works with any server side language or framework you desire!
The trick is that all rendering gets done server side and the SPA framework is just a dumb little script that replaces old DOM nodes with the newly rendered bits as they get sent down the pipe. You only bring the logic client side as needed, but defer work to the server 99% of the time. So no need to reproduce your rendering logic in 2 places.
Someone on HN has been hyping up his own variation on the technique and calls his framework IntercoolerJS but I haven't felt the need to move away from jQuery-Pjax.
I want a javascript framework that allows me to update a page incrementally, but also always works correctly and contains full content from the first server-side page load. Are there any options for this? Are there even keywords I can search for that discuss this? Sure, this files under "anything is possible", but honestly, I'd like a javascript framework that doesn't actively fight me also having static content. Any…
These javascript frameworks ultimately produce, at the end of the first page load, a DOM structure with event hooks attached. The DOM structure could be 100% created using html markup from the server, so if the framework provided a way to just hook up the events and then manage the DOM from that point on, you'd get the best of both worlds. It's possible to do this with native javascript jQuery by putting either classes or data attributes in the markup to indicate where the hooks go and then running an init method to find them. Bootstrap components work this way, for example. One of the earlier SPA frameworks, Knockout, worked this way too.
I must be honest, my experience with node was very short but this article suggests me that working with js may be really more complicated than working with java. Too many frameworks (which often lives too shortly), too many things to learn, it's overwhelming...sometimes it seems to me that working with js has become so difficult that working with java and jquery is still easier and better (i know lot of people will t…
I have no problem with difficulty (if interesting), but I get completely blocked by, what seems to me, needless complexity. The will to learn vanishes completely.
I want a javascript framework that allows me to update a page incrementally, but also always works correctly and contains full content from the first server-side page load. Are there any options for this? Are there even keywords I can search for that discuss this? Sure, this files under "anything is possible", but honestly, I'd like a javascript framework that doesn't actively fight me also having static content. Any…
I'd really like to see this too. Most of what I've seen is something like "use node.js on the server and make use of the framework's server-side rendering capabilities". For me that's a problem, because I don't want and can't use node.js on the server. These javascript frameworks ultimately produce, at the end of the first page load, a DOM structure with event hooks attached. The DOM structure could be 100% created u…
I don't understand, you want a javascript framework to do server-side rendering, but don't want to use node?
> Learn [Vue.js] after you have learned React or Angular. Hugely disagree with this. I really like Vue - but in my (very limited) experience, its appeal is that even though it's not as powerful or flexible as React or Angular it's way easier to learn and get moving with. Fewer new concepts, less new tooling, no ecosystem of related stuff to consider, etc. I'd have suggested learning Vue first, and sticking with it un…