Fork me on GitHub
#uncomplicate
<
2016-05-06
>
blueberry09:05:30

wouldn't that be a heavyweight solution? Neanderthal is a library - it should work in any environment you put it.

blueberry18:05:17

@aaelony atlas builds in that container wouldn't be optimized for the hardware architecture the container is running on.

aaelony18:05:19

yeah, it's definitely a tension between ease of install and use versus performance (which is the main point). I'm in agreement now.

aaelony18:05:11

was just a crazy thought to think that, well, if it's only tested and seamless on one platform right now, just make a docker container for that platform. But from a performance context, it defeats the purpose.

aaelony18:05:41

From a user adoption library perspective though, it might make sense, but not if benchmarking is the goal

blueberry18:05:46

It is also tested and even more seamless (as in works out of the box) on OSX 😉

blueberry18:05:52

And even from the user adoption point: how is fiddling with a docker container easier than installing a pre-built atlas with your system's package manager? On linux, for example, almost all distributions support installing atlas with something like pacman -Suy atlas.

blueberry18:05:12

If someone sends you a windows atlas.dll, that solves the biggest current hurdle for using Neanderthal on Windows.