Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's worth mentioning that I spoke to Guy Bedford (author of JSPM) after Sam put out this article. He thinks he can get JSPM's times down pretty easily and he's putting some effort into it this week.

I wouldn't let anyone interested in trying out JSPM be jaded by these numbers just yet. JSPM v0.17beta-6 hasn't reached fully stable yet and that's what's being used to generate these #s



JSPM is slow to build but I don't see much utility in building during development when on-the-fly transpilation can be used instead.

In terms of using JSPM to create builds for production, it seems significantly easier to setup than the equivalent using gulp, browserify, webpack.


Easier than Webpack? I dunno about that. I have major gripes about webpack, but being difficult to set up is not one of them.


The problem with Webpack IMO is that it kinda feels like Grunt sometimes where you find yourself editing a giant nested config. But it is by far the most flexible tool for the job and setting it up without all the fancy stuff is pretty straightforward.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: