benkb8

Isn't there a chicken-and-egg problem especially in US cities? The typical low-density suburban sprawl in american urban areas was "fueled" by the car/oil and housing industry in a much larger scale then in other similar developed countries. This lifestyle was nothing less then the american dream - no? In the same time the economy and the urban centers are expanding and everything is built around the autombile lifestyle. So yes, today it wouldn't be possible to simply scratch the car out of the equation, simply because it's heart and center of the urban america. But without the onesided accent on individual motor car traffic, america would probably have a different landscape that made public transport much more cheaper and convenient.

thanks for your explanations.

> - with opam every time you create switch you need to compile everything from scratch, with esy we try to reuse as much as possible from the build cache

Yes, that's definitely useful.

> [...] for now you can use package.json for npm/yarn for bucklescript dependencies and esy.json (esy looks for esy.json before package.json) for native dependencies.

So by acting like we use esy on Bucklescript, when we actually use npm, we get a very similar result?

hi Andrey,

thanks for yor work on esy, everytime it comes up I have a look at the documentation and the latest developments. It looks like a nice project, but I'm still a little confused about its purpose. You mention your JS background, so is it all about familiarity to npm? Or are there other things you gain when you run esy on top of dune?

And my other question? It doesn't run with bucklescript - right? Are there specific reasons?

Ben