4 ms·
My biggest problem is "the complete stack." Which one? How many months will it be the blessed way of doing things? As soon as I get some work outsourced, here
by dullgiulio 9y ago
My biggest problem is "the complete stack." Which one? How many months will it be the blessed way of doing things?
As soon as I get some work outsourced, here it comes yet another build system and yet another complete stack I have to get expert at.
Javascript lacks a standard library (a mistake from the beginning) as well as standard tools (can't blame Netscape for this, but today we could totally come up with something more definitive.
- tonyedgecombe 9y agoIf JavaScript had a standard library from the beginning we would be replacing it now because it wouldn't support Unicode or promises or async or whatever is coming next.
- sametmax 9y agoThe stdlib can evolve with the W3C the same way the language evolves.
- tonyedgecombe 9y agoYou mean we're stuck with the legacy stuff forever.
- hajile 9y agoThe w3c cannot break the web. Once something is in the language a certain way, it stays (technically, there have been a couple small breaking changes, but the fact that you don't hear about them speaks to their size and impact)
- veeti 9y agoThere is no single blessed "complete stack" for React and there never will be. That is a feature, since it is a view library only. It sounds like you're looking for a full framework, e.g. Angular or Ember.
- lhnz 9y agoReact was released in 2013. Redux was released in 2015. If you'd picked them then you've had a very long amount of time using the same tools.
- yellowapple 9y agoI'd hardly call 4 and 2 years (respectively) a "very long time".
- type0 9y agoIt is a very long time in js world of things
- saint_fiasco 9y agoWe don't have precognition. It is not safe to pick a brand new framework for an important project right away, we have to wait a bit first to make sure it is being maintained well.