31–40 of 90 posts
Does Tuxedo have a plan for Isomorphic applications? I have been following the Yahoo fluxible project since it provides nice abstractions, but was designed for isomorphic apps out of the box.
[1] https://github.com/goatslacker/alt [2] https://github.com/goatslacker/iso
Earlier quoted context omitted.
I think it's probably a good thing for now. People are still trying to figure out how to do frontend programming well. Eventually one/a few good models will come out of the chaos, and some frameworks implementing them will start to stabilize. Of course, I have no idea how long that will take.
I feel like the Ruby webdev community had a similar ethos, but I dropped out of that scene before things really coalesced. Can anyone comment on how things are playing out there?
Earlier quoted context omitted.
I think it's probably a good thing for now. People are still trying to figure out how to do frontend programming well. Eventually one/a few good models will come out of the chaos, and some frameworks implementing them will start to stabilize. Of course, I have no idea how long that will take.
I feel like the Ruby webdev community had a similar ethos, but I dropped out of that scene before things really coalesced. Can anyone comment on how things are playing out there?
Mind to develop your point ?
I never miss downvoting, but all the "not another framework!" Posts make me do so. It's not the framework creators fault that JavaScript is flooded with libraries, so give the framework the chance to prove itself. For JavaScript frameworks, it's survival of the fittest.
+1. There is literally zero negative impact on anyone's life by a hundred new js frameworks coming out every day. Ignore them. Use the ones you know and enjoy. If a new one seems to be gaining mainstream traction, spend an hour to check it out. Don't waste a second of brain activity or get annoyed with new frameworks - there is no reason.
(I might have the details wrong but here's the flavour)
Backbone was a good start - Ember and later angular offered to fulfil a genuine need but after a long period of bedding in, many people have become dissatisfied with them.
React (and a few similar frameworks that appeared around thw same time) turned everyone's head and seemed to offer a much better way forward. However it was only part of the jigsaw. It can be described as the V in MVC with some suggestions on the right way to add the M and C ('Flux').
So - what we're seeing now is a lot of people who've had time to digest React+Flux and are releasing a complete MVC package that incorporates all the lessons learnt. Consider how long we had the "just use jQuery" phase of front-end development. It's just time for pendulum to swing back the other way.
The javascript community seems to live by the motto "A framework a day keeps the doctor away". Is anyone keeping count, we must be in the hundreds by now?
Note: I didn't say making a good framework was easy, just making one at all.
Sometimes people just decide to experiment, to try something and then as they grow with it they think it's big enough to share. When a whole bunch of people do that, you end up where we are with JS frameworks.
I'm in the "it's no big deal" group. Are there thousands of frameworks? Yes. Have I heard of more than 5 of them being used extensively? No. The good ones are embraced by developers and shared. The other ones are mocked into oblivion. It's the natural order of things.
To all the 'oh noes - another framework people' - there's a pattern here. We're going through a transition that isn't complete. (I might have the details wrong but here's the flavour) Backbone was a good start - Ember and later angular offered to fulfil a genuine need but after a long period of bedding in, many people have become dissatisfied with them. React (and a few similar frameworks that appeared around thw sam…