Echo JS 0.11.0

<~>
amitport 3251 days ago. link 2 points ▲ ▼
assuming you don't have development time to waste - do not make a research topic out of selecting build tools - choose one - start working - don't use features you don't need - if you encounter issues - try something else
-just build your product!-

(ps, I like jspm, but really, just pick one and move on to real coding)

Replies

ashleynolan 3251 days ago. link 1 point ▲ ▼
If I was working in a smaller team, I’d definitely do that.  Problem is, the choice I make impacts on 30-40 developers and this means it takes time to change workflow tools and process (as well as re-educating people on the tools we’ve chosen).  It also doesn’t inspire confidence in your choices if you try and switch workflow tools every couple of weeks/months!

I’m playing around with a JSPM setup atm, but wanted to get opinions off devs who have more experience using it than me.  

I find it’s always useful to ask the question and see what comes out of it!
amitport 3251 days ago. link 2 points ▲ ▼
The thing is jspm, browserify and webpack are not exactly comparable. They do some different things and do them differently. 

What I was trying to say is basically this:
If you ask a general question people will answer based on their perspective, which isn't necessarily aligned with your requirements and thus not really helping your decision making.

You should focus on your specific requirements and work from there.

For me, gulp takes care of pre-build/deployment issues, so I don't need those features from webpack. On the other end, jspm, beside including a module loader (systemJs) is also a 'package manager' that is comparable to bower but more generic. I find this to be very useful when you start mixing packages from different sources that use different module systems.