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

Tuxedo.js – A Framework Built on React and Flux

tuxedojs.org

Post reply on HN
Print view View original

41–50 of 90 posts

Re: Tuxedo.js – A Framework Built on React and Flux

#41

Post by bringking »

goatslacker wrote: post #31
bringking wrote: post #6

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.

You should check out alt[1] and iso[2] which is isomorphic out of the box and it's pure flux. There are examples in both repos. [1] https://github.com/goatslacker/alt [2] https://github.com/goatslacker/iso

Thanks, those look great. Good work. Looks a little leaner than fluxible as well, which is always a plus

Re: Tuxedo.js – A Framework Built on React and Flux

#42

Post by RussianCow »

weego wrote: post #40
andybak wrote: post #38

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…

Those lessons appear to have left us needing a loading screen to show a web page. I'll stick with not bolting everything I can find together into a Frankensteins monster of a stack.

To be fair, a loading screen in a web app is a symptom of a bad design, not the use of a framework. For instance, you can use React from Node.js to pre-render the app's initial state.

Re: Tuxedo.js – A Framework Built on React and Flux

#43

Post by RussianCow »

fro wrote: post #25
emsy wrote: post #19

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.

Of course there is! It fragments the community, which means instead of pouring our efforts into making one really awesome framework (e.g. Ruby on Rails), every other developer is making their own.

Not that I think that's inherently bad, especially since web technology is constantly in flux, but you can't say that having tons of small frameworks has zero impact on anyone's life.

Re: Tuxedo.js – A Framework Built on React and Flux

#44

Post by goatslacker »

weego wrote: post #40
andybak wrote: post #38

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…

Those lessons appear to have left us needing a loading screen to show a web page. I'll stick with not bolting everything I can find together into a Frankensteins monster of a stack.

It doesn't have to be that way. These lessons are no substitute for server side rendering although with more frameworks supporting isomorphism out of the box this will hopefully be a thing of the past.

Re: Tuxedo.js – A Framework Built on React and Flux

#47

Post by norswap »

andybak wrote: post #38

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…

Frameworks are most often a bad idea. Use libraries instead.

Sometimes they are useful though. For instance, they make sense when routing. But in those cases, they should more like libraries as well: more lightweight. Something like Express or Koa.js but more lightweight.

Re: Tuxedo.js – A Framework Built on React and Flux

#48

Post by sebastianconcpt »

norswap wrote: post #47
andybak wrote: post #38

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…

Frameworks are most often a bad idea. Use libraries instead. Sometimes they are useful though. For instance, they make sense when routing. But in those cases, they should more like libraries as well: more lightweight. Something like Express or Koa.js but more lightweight.

People learn using frameworks and discover using libraries.

Some are pioneering-friendly others just-doing-the-job-friendly.

Nothing static, all oscillating in a big Cambrian Explosion of JavaScript creativity

Re: Tuxedo.js – A Framework Built on React and Flux

#49

Post by UberMouse »

jstoiko wrote: post #29

I just spent the past 5 days (re-)evaluating javascript frameworks for a project. It does feel like there are (too) many choices. However, I wonder: why are so many of these frameworks so opinionated? e.g. in Tuxxedo, why would 'actions' be named 'add', 'remove', 'edit' or 'get'. Why not following CRUD or POST/DELETE/PUT/GET convention? That's just one example. It feels like the front-end developer community tends to…

Those actions can be named whatever you want. The person who wrote the code that appears in the documentation just went with those names, they're completely up to you, the developer.

Re: Tuxedo.js – A Framework Built on React and Flux

#50

Post by sjfstebbins »

UberMouse wrote: post #49
jstoiko wrote: post #29

I just spent the past 5 days (re-)evaluating javascript frameworks for a project. It does feel like there are (too) many choices. However, I wonder: why are so many of these frameworks so opinionated? e.g. in Tuxxedo, why would 'actions' be named 'add', 'remove', 'edit' or 'get'. Why not following CRUD or POST/DELETE/PUT/GET convention? That's just one example. It feels like the front-end developer community tends to…

Those actions can be named whatever you want. The person who wrote the code that appears in the documentation just went with those names, they're completely up to you, the developer.

We provided opinionated components, but almost all of them are customizable. Actions, animations etc.. can all be changed. We allow you to use our default component names or adjust them to your liking. This ability to adjust defaults follows throughout Tuxx. Check out the documentation for more.
Post reply on HN