[deleted]
I just see them as "This is the way I organize my JS", so they're all useful to me.
Tuxedo.js – A Framework Built on React and Flux
21–30 of 90 posts
Re: Tuxedo.js – A Framework Built on React and Flux
#22Seriously? Your solution to showing syntax highlighted code snippets is images???
Re: Tuxedo.js – A Framework Built on React and Flux
#23[deleted]
I hate them! Do you remember the good old times, where people just wrote their code, and didn't share it with anyone? Everyone just reimplemented everything, all the time. And if someone did try to share some code, you wouldn't find out about it in "news"!!! You'd have to search through mailing lists and be lucky! to spot it before it got replaced by thousands of angry emails about the new license people's favorite *nix tool just adopted.
I do remembered reading an email one day, from some guy who was getting tired of all these licensing discussions. He remember the great ol' times, when code was written on paper, everyone had their own language, and no one gave a damn about a license...
Re: Tuxedo.js – A Framework Built on React and Flux
#24I 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.
Better than some of the stagnant languages out there. If people don't want to try any of these new frameworks, they should just keep using what they were using before. Strange to complain about there being too much enthusiasm and innovation in a community.
Re: Tuxedo.js – A Framework Built on React and Flux
#25I 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.
Re: Tuxedo.js – A Framework Built on React and Flux
#26The index is missing some content on Safari thanks to an error (OS X, 8.0.2, private browsing enabled):
> InvalidCharacterError: DOM Exception 5: An invalid or illegal character was specified, such as in an XML name.
Seems like an useful combination, but doesn't make me feel great when it's got an error on a mainstream browser.
Re: Tuxedo.js – A Framework Built on React and Flux
#27[deleted]
I hate them! Do you remember the good old times, where people just wrote their code, and didn't share it with anyone? Everyone just reimplemented everything, all the time. And if someone did try to share some code, you wouldn't find out about it in "news"!!! You'd have to search through mailing lists and be lucky! to spot it before it got replaced by thousands of angry emails about the new license people's favorite *…
You sir, win.
Edit: I'm getting prepared for this to be my most down voted comment yet so guess I should add something of substance like saying that; I don't feel like the over sharing of JS libraries is inherently the problem. But it's what you do with that that can bring you into dangerous water, for example. If my project depends on 10 deprecated projects I'm going to have a hard time. But if I grab one as my base and build on top of it to suit my needs than a healthy architecture can be born. So I guess oversharing isn't the issue, but if you don't plan on maintaining your project forever more make it easy to extend, overwrite, and build on. A lot of JS frameworks don't have this in mind.
Re: Tuxedo.js – A Framework Built on React and Flux
#28It would take something truly novel to make me consider anything on top of the simple and powerful setup which is react + a custom flux. I don't see much here except some glue that reduces flux boilerplate for actions. It also seems to be a replacement for a simple mixin that subscribes components to stores. The animations feature doesn't seem to be too different than the standard CSSTransitionGroup. The docs say that the Tuxx abstracts away the "complexity" of flux but I don't buy it.
Re: Tuxedo.js – A Framework Built on React and Flux
#29I 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 over-engineer things these days.
Re: Tuxedo.js – A Framework Built on React and Flux
#30It would take something truly novel to make me consider anything on top of the simple and powerful setup which is react + a custom flux. I don't see much here except some glue that reduces flux boilerplate for actions. It also seems to be a replacement for a simple mixin that subscribes components to stores. The animations feature doesn't seem to be too different than the standard CSSTransitionGroup. The docs say tha…
Same. Flux is really simple and most of the implementations just remove some boilerplate and add some conventions. Given more time there might be a framework that has everything that I want, informed by comprehensive, mature, real-world use cases, but I haven't yet seen anything compelling enough in the dozen or so libraries I've looked at. I've found a lot of value in having granular control so I can explore different conventions and optimizations.