1. 9
  1.  

  2. 12

    I’ll wait for it to be open source before I even consider trying anything. I don’t want to rely on your service being up for mine to be.

    1. 2

      Seems like this is targeted specifically at the use case of running inside a browser.

      I’m just transitioning from npm to yarn for my own projects. Current versions of either seem pretty good to me, and much improved over old versions of npm in terms of speed.

      Faster is always better, but I don’t feel seriously inconvenienced by existing tooling anymore (at least on my own projects, which are not that large.) Are there still major performance concerns for typical projects with existing tools?

      1. 1

        I’m just transitioning from npm to yarn for my own projects.

        I wonder when do you JavaScript people actually program for users :-)

        1. 1

          What users? ;-)

          I probably should have specified “for new projects”, but in any case, your point stands!

      2. 2

        Retrieves only the files you need, on-demand

        Well that’s cheating :) Sure it’s a good strategy for in-browser, but I’m not sure why I’d need to download packages from a package registry in the browser… oh, they’re building an in-browser IDE.

        1. 1

          I just started writing JS for our internal CRM and other applications, and although it doesn’t really bother me, I do find it strange how npm install (some package) takes so long, like I can build packages from source in FreeBSD quicker than I can install one module in npm. If the code behind this ever makes it to a local application, it would certainly be a big improvement. It probably only works in development though, as when bundling your applications, you may need a file that turbo hasn’t fetched, and depending on your builder picking this up, it could cause a few headaches/problems debugging production runtime errors.

          Regardless of the above, the software engineering behind this sounds very impressive and it’s nice to see a startup actually solve a real world problem.

          1. 2

            If npm speed is bothering your, I highly recommend trying https://yarnpkg.com/ – it can pretty much be used as a drop-in replacement for npm that just makes everything faster (and takes up less of your drive space)

            1. 1

              Up until I read the post in this thread, I have never heard of yarn, I have only been writing JS for a few months now. I have just given it a quick whirl and it seems fairly decent,I will see how it fairs over the next few months and how it compares etc, thanks :-).

              1. 2

                I moved from yarn back to the official npm client when they released v5. npm currently also caches packages :)

          2. 1

            This post almost makes zero sense… apart from “buy my product” it’s pretty much a series of unconnected dots and buzzwords masquerading as cohesive argument for… something?!

            tens of millions of requests every month ~ 4 requests per second…